Your bookkeeper should send invoices but not delete projects. Your crew leads should log time but not see what everyone earns. Roles are how you set that up once, for every person in the same job, instead of person by person.
Permissions, roles and people
- A permission is one thing someone may do in one module: read time entries, approve a work order, delete an invoice.
- A role is a set of permissions for one kind of job: Office, Crew lead, Estimator.
- A person gets one or more roles. They can do everything their roles allow, added together.
You never give a permission to a person directly. When someone's job changes, you change their roles, and everything follows.
Your workspace starts with one role
A new workspace has a single role, Admin, for its Workspace Administrators. It's the system role: it can't be renamed or deleted, and every module you add gives it that module's permissions.
Everything else is yours to design. Make a role for each kind of job in your company, such as Office, Crew lead, Estimator or Field tech, and give it what that job needs. A role named after a job is easier to hand out and easier to check than a vague "user" or "viewer" role.
The Admin role is not the same as being a Workspace Administrator. A Workspace Admin (the Admin account type) can do everything, including managing people and settings, whatever roles they hold. See What a Workspace Administrator can do.
How modules add their own permissions
Each module brings its own list of permissions. When your workspace subscribes to a module, the Admin role gets them, the way the module recommends.
Your own roles get nothing automatically. After you add a module, open each of your roles and add what that job needs from it: usually reading for everyone who uses it, and creating and editing for the people who do that work.
Every module also has two permissions worth knowing:
- Manage settings lets someone change that module's settings without being a Workspace Admin. Give it to the person who looks after one module, such as your fleet manager for Equipment.
- Reports lets someone open the module's Reports tab.
Reading the permission list
When you open a role's Permissions tab, the available permissions are on the left, grouped by module, and the role's permissions are on the right. Each one says what it allows in plain words. Some carry a label:
- Take care, High risk or Critical: it changes or deletes a lot, or reaches sensitive information. Give it only to people who need it.
- Their own records only, Their team only or Their site only: it reaches only some records.
- Also gives: it includes another permission, for example edit includes read.
Nothing changes until you press Save changes, and Undo changes puts everything back.
Good to know
- Give each role the least its job needs. It's easy to add more later. It's harder to notice someone has too much.
- Check your work with Simulate. After setting up a role, open someone who holds it and press Simulate to see the workspace exactly as they do.
- A person with no role can sign in but sees nothing. Give everyone at least one role.
- Dashboards and reports never widen access. Sharing a dashboard shows each person only the data their own roles allow.
- A role still held by someone can't be deleted. Move its members first: the platform offers Open Members tab to do it.
Step by step: Create and manage roles · Add and manage people · Simulate a user