Understand access levels
When to use this
Use this when you need to choose the right access level for a user or explain why a person still cannot use a feature that the account has enabled.
What you need first
- The user already belongs to the account or is about to be invited.
- You know what kind of work that person actually needs to do.
Steps
1. Start by choosing the user’s access level seat:
2. Match the seat to the person’s real job:
3. After choosing the seat, confirm whether the account itself has the relevant module enabled. 4. If the user is a Client seat user, confirm that company scope is also set correctly.
- Owner
- Admin
- Office
- Creator
- Field
- Viewer
- Client
- office operations staff usually need Office
- field crews usually need Field
- external clients usually need Client
What happens next
- The seat determines the base capability bundle the user receives in that account.
- Account entitlements still matter. A user can have the right seat and still not see a module if that module is not enabled for the account.
- Feature flags can also change what appears inside an enabled area.
If it goes wrong
- If the user has the right seat but still cannot see the area, check whether that account has the module enabled first.
- If the account has the module but the user is still blocked, review [Understand roles vs seats](./understand-roles-vs-seats.md).
- If the user is a client and sees no useful records, confirm their company scope before changing them to another seat.