Using the Default role

Your users might need different levels of access or permissions based on their roles. Since a user can have more than one role, and each role comes with its own permissions, all these permissions add up. To keep things simple, it's a good idea to have a basic role that every user gets by default. This way, no matter what, every user starts with a fundamental set of permissions, even if they don't have any specific roles assigned to them yet.

The default role in the platform should always have the fewest permissions to serve as a foundation. You can only have one default role on your platform. Therefore, it's important to determine the lowest level of permissions needed for any user account and assign those permissions to the default role.

Set a role as default

You can set a role as default when creating or editing a role. Learn more in Managing roles.

We recommend using the default role for your basic user role, unless you need another lower role. View our recommendations for a user role in Best practice: User role.

Alternatively, you can create a restrictive Terminal PC role as default. This type of role is typically used for shared devices and is designed for pure consumption, without the ability to interact on the platform (such as commenting, liking, or sharing). Learn more about the Terminal PC role in Best practice: Unique roles.

Was this article helpful?

0 out of 0 found this helpful