Manage User Roles:
1. Navigate to Settings > Team (Admin access required)
2. Locate the team member in the list
3. Click the Role dropdown next to their name
4. Select role:
- Admin: Full workspace management, can invite/remove users, access all settings
- Collaborator: Standard user, cannot manage team or workspace settings
5. Confirm role change
6. User's permissions update immediately
Assign Module Permissions:
1. In Settings > Team, find the user
2. Click "Manage Permissions" or the sliders icon next to their name
3. FeaturesPermissions modal opens
4. Check/uncheck modules to enable or disable access
5. Click "Save"
6. User immediately gains or loses access to selected modules
7. Disabled modules disappear from user's navigation sidebar
Promote/Demote Users:
1. To promote Collaborator to Admin: Change role dropdown to "Admin"
2. To demote Admin to Collaborator: Change role dropdown to "Collaborator"
3. Confirm the change
4. Admin gains/loses Settings access, team management, billing access
5. Not*: Cannot change your own role (prevents lockout)
Practical example
Senior partner Marie Lefevre manages permissions for her growing notarial office. She promotes her trusted deputy Thomas to Admin role so he can help manage the team. For their new junior notary Emma (hired last month), she assigns Collaborator role with access to Library, Anonymisation, and Translation only - restricting Smart Drafting, CRM, and E-Invoicing which require more experience. For their two administrative assistants, she enables Agenda and Library but disables all other modules since they only need calendar management and document filing. This ensures junior staff learn the platform gradually while protecting sensitive client data and complex tools from accidental misuse.
Notes and limitations
Admin only: Only Admins can modify roles and permissions
Self-modification blocked: Cannot change your own role to prevent admin lockout
Workspace-level modules: Modules must be enabled at workspace level before assigning to users
Immediate effect: Permission changes apply instantly - user sees modules appear/disappear in navigation
No granular sub-permissions: Module access is all-or-nothing (e.g., cannot give "read-only Library" access)
Admin sees all: Admin role automatically has access to all modules regardless of individual toggles
No audit trail: System doesn't track who changed permissions when (no history log)
Removal requires separate action: Revoking all permissions doesn't remove user - must explicitly remove from workspace
FAQ
Q: What's the difference between Admin and Collaborator roles?
A: Admin has full workspace management capabilities including inviting/removing users, changing roles and permissions, configuring workspace settings (logo, name, defaults), managing billing, and accessing all modules. Collaborator is a standard user who can only access modules explicitly assigned to them and cannot manage team members or workspace settings. Admins can see Settings page; Collaborators cannot.
Q: Can I customize permissions per module, like giving someone read-only access?
A: No, module access is currently all-or-nothing. If you enable Library for a user, they have full Library access (upload, delete, organize, share). There are no read-only or limited permissions within a module. To restrict capabilities, either enable/disable entire modules or use administrative oversight and training to guide proper usage.
Q: Can I change my own role from Admin to Collaborator?
A: No, users cannot modify their own role to prevent accidental admin lockout scenarios. If you need to change your role (e.g., stepping down as admin), ask another Admin in your workspace to change your role. If you're the only Admin, contact support@nora.legal to safely transfer admin responsibilities before demoting yourself.