Where: web portal, Settings, then Role permissions. Needs: the Org Admin role.
When you finish: one of your roles can do something it could not do before, and you know how to take it back.
What you can give a role
Each role comes with a set of things it can do (see Roles, and what each one can do). On Role permissions, an Org Admin can add to that set for your organization. It only adds: you cannot take away something a role can already do.
Permission | What it lets people do | Who can already do it |
Archive jobs | Archive a job from its panel on the Dashboard. | Org Admin |
Edit org-wide configuration | Create, edit and import configurations, and the custom types and object templates they use. | Org Admin |
See every data object | See every job, map and data object in your organization, not only the ones they created. | Org Admin, Analyst / Fielder, Workforce Manager, Analyst (Read-only) |
Restore archived jobs | Bring an archived job back. | Every role except Analyst (Read-only), so there is nothing to give. |
See every data object is the widest permission on the page. Give it to Basic User, for example, and every Basic User sees every job, map and object in your organization, including other people's work.
Give a role a permission
In the web portal, open Settings, then Role permissions. Roles run across the top and permissions down the side.
Tick the box where the role's column meets the permission's row. A box that is already ticked and greyed out, marked DEFAULT, is something the role can already do.
Click Save changes. You see Role permissions saved, the box is marked GRANTED, and Recent changes shows who made the change and when.
Settings, Role permissions: Archive jobs ticked for Basic User, not saved yet. Boxes marked DEFAULT are what a role can already do; boxes marked READ-ONLY cannot be ticked.
Changed your mind before saving? Click Discard.
Org Admin has no column. It can already do everything on this page.
The Every member column gives the permission to everyone in your organization, whatever their role.
A person can do everything any of their roles can do. If you give Basic User a permission, everyone who holds Basic User gets it, even if they hold other roles too.
Analyst (Read-only) cannot be given anything that changes data. Those boxes are locked and marked READ-ONLY. Anyone who holds Analyst (Read-only) stays read-only whatever their other roles allow, unless they are also an Org Admin.
Changes apply to your organization only.
What changes for people in that role
The change applies straight away. Ask them to refresh the page so their screen catches up.
Archive jobs: Archive job is available when they open a job on the Dashboard. Archived jobs are under Historical on the Dashboard.
Edit org-wide configuration: Configurations appears in their Settings and on the Dashboard, and they can save changes there.
See every data object: each job's map shows all of its objects, not only theirs.
On a phone: ask them to sign out of Utility Scout and sign back in.
Take a permission back
Open Settings, then Role permissions.
Untick the box marked GRANTED and click Save changes.
Recent changes keeps every change, newest first, so you can see who gave each permission and who took it back.
People in that role then see, for example:
On a job, Archive job is greyed out, with Your role cannot archive jobs. An organization admin can grant it.
The bottom of a job's panel on the Dashboard, for someone whose role cannot archive jobs.
Configurations is gone from their Settings. If they open it from a saved link, they see You don't have permission to manage configurations.
Settings for someone whose role cannot edit configurations: there is no Configurations item, and a saved link shows this message.
After you take away See every data object, objects already downloaded to someone's phone stay visible in Utility Scout until they sign out and sign back in. Ask them to do that straight away.
If something does not look right
Role permissions is not in my Settings. Only an Org Admin sees it. Ask an Org Admin, or ask us.
Couldn't check your access to role permissions or Couldn't load role permissions. Cloneable could not be reached for a moment. Click Try again. Nothing was changed.
I gave a permission, but the person still cannot use it. Ask them to refresh the page, or sign out and back in. Then check all of their roles: if one of them is Analyst (Read-only), they stay read-only.
I want a role to do less. This page cannot take away what a role does by default. Give the person a different role instead.
I would like Cloneable to set this up. Ask us. Changes we make show in Recent changes too, with our email address.