Understand role permissions and record access
Control what users can do and which records they can see.
Menus and actions depend on your company's settings and your access. If something is missing, ask your company administrator.
Before you begin #
Only an authorized administrator should change role access. Review the intended scope before applying bulk changes.
Step by step #
- Open Roles and edit the intended role or use its record-access action.
- Review permissions for the modules the role needs.
- Review Show Assigned Users for user-selector visibility.
- Set Module Record Access separately for each applicable module.
- Use the bulk action when the same selected module settings must be applied to multiple roles.
- Save, then test with a representative restricted account.
Understand the fields #
- Show Assigned Users: governs the assigned-user visibility policy, including applicable child-role users.
- Module Record Access: controls records for the selected module.
- Assigned to me: narrows records to the applicable personal assignment rule.
- Assigned to me & my team: includes the applicable team scope.
- All company records: remains within company/permission boundaries.
- Use previous access rules: retains the module’s existing visibility behavior.
Check the result #
Verify both listing and direct record access with a restricted user. Changing a dropdown is not proof that every team workflow is correct.
If something goes wrong #
If access is broader or narrower than expected, inspect the module scope, assignments and all levels of the role hierarchy. Avoid making everyone an administrator as a workaround.
On mobile #
Open the same module from the app menu. Use the record card or its actions menu. Scroll through the form before saving so that required fields and validation messages are not missed. Your permissions still apply.