These docs are for AuthRocket 1. Looking for AuthRocket 2 docs?

Storing accounts within AuthRocket

AuthRocket provides a number of ways to store users and accounts. Whether you have a basic app with just a few users, a complex suite of apps requiring separate users and accounts with arbitrary associations and permissions between them, or something in between, AuthRocket is flexible enough to meet your needs.

In general, we find there are 3 major approaches to accounts:

  • Simple accounts where 1 User = 1 Account.
  • Single-owner accounts where 1 User = 1 Account, but additional users/team members have secondary access.
  • Complex accounts where an arbitrary number of Users belong to an arbitrary number of Accounts.

All 3 approaches can optionally support permissions, although they’re typically only used for the second and third options.

See the following for in-depth discussions, including how and when to use Orgs:

Additionally, there’s one major variation on the above, and that’s multi-tenant apps where each tenant has it’s own independent store of users (and accounts). This will combine use of one Realm for each tenant along with any of the above 3 approaches inside each realm, as appropriate for your app. See the multi-tenant section of Using Realms within AuthRocket for more.

The above is not an exhaustive list of how AuthRocket can be made to work. The building blocks provided by AuthRocket are very flexible and a wide variety of use cases are possible. If you have something in mind and can’t quite figure out how to make it fit, give us a shout and we’ll help you get it sorted out.

Questions? Find a Typo? Get in touch.