User permissions
User permissions determine how much of a team's activity, settings, and administration a user can access.
They are one of the main ways Legalesign separates operational users from team-wide administrators.
Why permissions matter
Permissions affect more than visibility. They determine whether a user can:
- see only their own documents or wider team activity
- manage other users
- access organisation-level settings
- control sensitive features such as billing or compliance settings
Practical permission model
In most teams, permissions should follow responsibilities rather than seniority alone.
Useful patterns include:
- broad team visibility only for users who need it
- restricted organisation controls for a smaller admin group
- permission reviews whenever responsibilities change
Common mistakes
Teams usually run into trouble when:
- too many users are given broad access by default
- permissions are set once and never revisited
- the difference between team activity and organisation controls is not clear
Permissions and user lifecycle
Permissions interact closely with user administration. When you add, remove, or replace a user, you should treat permission choice as part of the workflow rather than an afterthought.