I'm using a graph for a collaboration platform where the back end benefits from the idea of dynamic relationships between objects where someone "owns," "shares,

I'm using a graph for a collaboration platform where the back end benefits from the idea of dynamic relationships between objects where someone "owns," "shares," and things "comprise," etc. Instead of tacking an RBAC system onto a flat document management system, I just designed my data model as a set of objects and different types of relationships. Saves me the trouble of metadata, normalization, and access control just becomes a traversal instead of having to manage a separate policy store. Anything that requires collaboration, sharing, user profiles, consent, etc.