# Custom roles

> Admins can now create roles of their own and change what Manager and Member allow, down to who deletes submittals or marks an RFI's official response.

Source: https://docs.specset.com/changelog/2026-11-15-custom-roles · Published: 2026-11-15

Open **Members → Roles** in the organization sidebar. Click **New**, name the role, choose the built-in role it starts from (or start from nothing), and turn each permission on or off, area by area: projects, documents, submittals, RFIs, checklists, closeout, agents, members and integrations. Then give it to people in the **Org role** field on the Members page, or as their project role on one project.

![The Roles page under Members, listing the built-in Admin, Manager and Member roles and two of the organization's own, Field engineer and Owner's representative, with their descriptions and member counts](https://docs.specset.com/images/changelog/2026-11-15-custom-roles/roles.png)

Submittals and RFIs follow the role in detail. For submittals a role can view, create and edit, manage reviews, manage stamps and delete; for RFIs it can view, create and edit, respond, mark the official response and delete. Without View, the area leaves the person's project navigation and its records stay out of their search results and activity feed. An agent works with the role of the person using it, so what the role can't do, the agent can't do for them.

Manager and Member can be changed too, and **Reset to default** puts back the access they shipped with. Admin can't be changed, and organization settings, security, identity providers and the roles themselves stay with the Admin role. To review who holds a privileged role, run `specset org members list --privileged` with the command-line tool, version 2.2.0 or later. See [Members & roles](https://docs.specset.com/docs/team-roles) and [Secure configuration](https://docs.specset.com/docs/secure-configuration).
