Roles access begins at the account level, and permissions are ‘granted’ down from there. Every admin user (including the first admin to join the platform) has access to their own Roles. This set of permissions has already been configured for them by whoever gave them access to the platform. And this set of rights, their own Role, is what they, in turn, will use to grant other users access to the platform as well.
Roles follow a hierarchy similar to that of a typical family structure, where a ‘parent’ Roles sits at the top of the permissions hierarchy. This parent doc can be used to create ‘child’ and ‘sibling’ docs that grant permissions and system access to any users they’re assigned to.
‘Sibling’ docs are exactly what they sound like. You can think of them as any Roles that exist at the same level within the user hierarchy. Let’s say the owner of a parent doc creates three child docs. These three child docs are all siblings to each other, since they’ve been created by the same parent. The system also allows the owner of the parent doc to choose which sibling docs can ‘see’ other sibling docs.
Once the docs are created and configured, they can be assigned to one or more admin users, who can then access the platform according to the permissions granted to them within the docs they’ve been assigned. Please note that one Role can be assigned to one, multiple, or even groups of admin users.