Skip to content
English - United States
Client Support Portal Sign in
  • There are no suggestions because the search field is empty.

User Permissions Management FAQ

Find quick answers to common questions about managing user permissions, roles, and access exceptions in Aclarian.

This FAQ explains common approaches to managing user permissions in Aclarian. It covers best practices for using custom roles, when to clone or copy roles, how role conflicts work, and how to handle exceptions or lower-access needs.

Frequently asked questions

Should permissions be managed through roles or user profiles?

  • Permissions should usually be managed through Custom Roles. This is the most efficient and consistent method for assigning and maintaining access.

Can a user have more than one role?

  • Yes. A user can be assigned multiple roles.

What happens if roles conflict?

  • If roles conflict, the user receives the highest level of permission available for each item.

Can permissions be changed directly on a user profile?

  • Yes. User-level changes are allowed, but they should usually be used only for exceptions rather than standard access management.

Why are updated permissions not showing right away?

  • The user may need to log out and log back in before updated permissions take effect.

What is the best way to manage permissions at scale?

  • Use Custom Roles as the primary structure for managing permissions at scale. This makes access easier to assign, review, and maintain across multiple users.

When should Clone Role be used?

  • Use Clone Role when you need to create a variation of an existing role without starting from scratch. This is helpful when most permissions remain the same and only a few changes are needed.

When should Copy Roles from User be used?

  • Use Copy Roles from User as a short-term setup shortcut when onboarding someone who needs access similar to another user. For long-term maintenance, use roles instead of relying on copied user setups.

When should a user profile be edited directly?

  • Edit a user profile directly only when a true exception is needed. In most cases, role-based permission management is the better long-term approach.

What should I do if a user needs lower access than their current role provides?

  • Create a separate role with the correct lower access level instead of relying on repeated manual overrides. This keeps permission management more consistent and easier to maintain.

Summary

Managing permissions through roles creates a more scalable and maintainable access model. Using custom roles, limiting direct edits, and creating separate roles for true access differences helps keep user management clear and consistent.