> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/administration/settings/roles-and-permissions.md). # Roles and permissions Roles bundle permissions so access can be reviewed in one place. The Roles & Permissions page lists each role with its description, how many permissions it grants, and how many users hold it; built-in default roles are marked with a Default badge. Open a role to see exactly which permissions it includes. A user's abilities come from the roles they hold, which you assign per user on the Users page (self-serve if you hold the Manage Users permission). If you hold the Manage Roles & Permissions permission, role management is self-serve from this page: * **Create a role.** Click New role, name it, choose its permissions, and save. You can generally include only permissions you hold yourself. Office admins can also delegate **Access Mobile** and **Create Own Visits** without holding them. * **Edit or delete a custom role.** Open the role, change its name, description, or permissions, and save — every user holding the role gets the change immediately. Deleting a role removes it from the users who hold it. * **Default roles are read-only.** Use **Duplicate to edit** on a default role to create an editable copy, then adjust the copy's permissions. ![Roles and permissions settings](https://3838208579-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Flu1pgNH0CrkCPslG8suQ%2Fuploads%2Fgit-blob-794a0cb93ac854390367bbfdad33d4c3a7dbdd3f%2Fsettings-roles.png?alt=media) > **Where to find it:** Settings -> Roles & Permissions ## Let technicians complete only office-prepared reports Create and Edit are separate inspection-report permissions. To let technicians fill out and submit reports without starting new ones: 1. Open the technician's custom role, or duplicate a default role to make an editable copy. 2. Keep **View Inspection Report**, **Edit Inspection Report**, and **Submit Inspection Report** enabled. 3. Turn off **Create Inspection Report**. This also turns off **Duplicate Inspection Report**, because duplication creates a new report. 4. Save, then assign the custom role on the Users page and remove any other role that still grants report creation. These permissions apply on both web and mobile. The mobile app keeps existing reports available under **Inspection Reports** on the visit. Changes reach the app when it refreshes its permissions online; an offline device cannot receive a role change until it reconnects. ## Let technicians schedule their own visits **Create Own Visits** (under Scheduling) lets a technician add a job and visit for themselves from the teal **+** button on the technician app’s Visits tab, in Day, Week, Month, or Open. Only the **Default Super Technician** role includes it by default; **Default Technician** and **Back Office Admin** do not. Office admins with **Manage Roles & Permissions** can add it to custom roles, and those with **Manage Users** can assign roles that include it, without receiving the permission themselves. To give it to other technicians, add it to their custom role; to withhold it from Super Technicians, duplicate that default role, turn the permission off, and assign the copy instead. This permission works independently of [backlog self-scheduling](/customers-and-work/scheduling/let-technicians-schedule-backlog-visits.md): the **+** button appears on Day, Week, and Month even when the Open tab is disabled, and also appears on Open when that tab is enabled. ## Seat charges when granting mobile access Granting **mobile access** to a role that users already hold makes those users technicians. If your business is billed per technician seat, Essential shows the seat charge before the role saves. See [Manage Essential billing](/administration/settings/essential-billing.md). ## Related guides * [What the permissions control: a tour of the catalog](/administration/settings/what-the-permissions-control-a-tour-of-the-catalog.md) * [Add and manage users and their roles](/administration/settings/review-users-and-their-roles.md) * [Contact Essential for setup changes](/getting-started/getting-started/contact-essential-for-setup-changes.md) * [Add or edit a pricebook item](/administration/settings/add-or-edit-a-pricebook-item.md) * [Add the intake form to your website](/administration/settings/add-the-intake-form-to-your-website.md) * [Automate task statuses with Task Automations](/administration/settings/automate-task-statuses-with-task-automations.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://learn.withessential.com/administration/settings/roles-and-permissions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.