Overview

The Users settings page is where an administrator controls who at your organization can sign into Turris, which agency each person belongs to, and what they are allowed to see and change. From one screen you invite new teammates, adjust roles after a promotion, move people between branches, and open a role-by-role reference table when you are not sure how much access a role actually grants.

What is the Users Settings Page?

Users is the membership roster for your downstream organization in Turris. When you bring on a new licensing coordinator, move someone from one branch to another, or check who still holds Admin rights after a reorganization, this is the page you open.

Who uses it. Org administrators (the Admin role) own day-to-day membership: inviting new hires, changing roles, and reassigning people between agencies. Every other signed-in user can still open the page to update their own name, position, and title from the Edit My Profile button.

See every user in your organization on one screen, with their role, email, and the agency they belong to.
Invite a new user by email and place them in the right branch on day one.
Adjust a teammate's roles after a promotion or department change without leaving the Settings modal.
Move a user from one branch to another by changing their Associate with Agency field.
Pull up the full Role Permissions matrix when you need to answer "what can a Compliance user actually do?"
Let every team member self-serve updates to their first name, last name, and position.

Accessing the Users Settings Page

Users is a section inside the global Settings modal, which opens on top of whatever page you are currently viewing.

From anywhere in the app, open Left sidebar (bottom) → Settings. The Settings modal opens.
In the left-hand category list, under the Organization group, click Users.
The Users panel loads inside the modal. The page you were on stays open behind the modal and is restored when you close it.

What's visible on the page:

Element	Description
Users banner	Information header reminding you that you can add users to your organization and assign them roles with different access rights to control who can access and modify your data.
Filter label and help icon	A small question-mark icon next to the Filter label. Hovering it shows the note "You can filter members by agency."
Filter dropdown	Single-select agency dropdown used to scope the table by agency.
View Role Permissions button	Outline button with a help-circle icon. Opens a full-screen reference table that maps every feature to read / write access per role.
Create User button	Primary button that opens the Add User slide-over. Available only when you have permission to create users (in practice, Admins); other users see a feature-locked state in its place.
Edit My Profile button	Primary button that opens the Update User slide-over pre-filled with your own record. Visible to every signed-in user.
Users table	Lists each user's avatar, name, email, role badges, and associated agency.

To open an individual user, click their row in the table. The Update User slide-over opens with that user's current details. A non-Admin who clicks any row other than their own sees an inline alert reading You do not have permission to update users., and the slide-over does not open.

The Users Table

The table renders the filtered member list. Each row is one user.

Column	Description
Name	Circular avatar showing the user's initials, followed by their first and last name in bold.
Email	The user's sign-in email address.
Role	One primary-colored squared badge per role. A user with two roles (for example Admin and Compliance) shows two badges side by side. Underscored values are spaced out, so `pending_admin` renders as Pending Admin.
Agency	The legal name of the agency the user is associated with, in bold, with the branch name underneath in smaller muted text when one is set. Shows `N/A` when no agency is associated or the agency record has no legal name.

The table paginates automatically once the filtered list passes 10 rows. If no users match (for example because your filter excluded everyone), an inline banner reads No Users Available. There are currently no users available. Use the "Create User" button to add one.

Tip: The search box above the table matches against the Name, Email, and Role columns. Typing the first few letters of a role (for example compl) narrows the list to users holding that role. The Agency column is not searched.

Filtering by Agency

When you'd do this. Your organization has more than one branch and you want to focus on a single team, for example when reviewing who at the Atlanta branch can sign producer agreements.

Click the Filter dropdown to the right of the Filter label.
Choose one of:
- Select an agency (the placeholder): shows every user in your organization. This is the default, equivalent to no filter.
- All Agencies: shows every user across every branch.
- A specific agency name: shows only users whose Associate with Agency is set to that agency.
The table updates immediately. There is no separate Apply button.

Note: Filtering is a straight match on each user's associated agency. When you pick a specific agency, every user assigned to a different agency drops out of view, so the count you see is the headcount for that one branch.

Creating a User

When you'd do this. A new compliance hire starts Monday and needs to log in, view your agencies, and work in their branch.

Click Create User in the top-right of the Users panel. (This button is active only for users with permission to create users, in practice Admins.)
The Add User slide-over opens. Its subtitle reads to <Your Organization Name>, so you can confirm which org you are adding the user to.
Fill in the form:

Field	Required	Description
First Name	Yes	The user's given name. Example: `Jordan`.
Last Name	Yes	The user's family name. Example: `Reyes`.
Position (optional)	No	The user's job title at your organization. Example: `Compliance Manager`.
Email	Yes	The user's work email, used as their sign-in identity. Must be a valid email format. Cannot be changed after the user is created.
Role	Yes	Multi-select dropdown of the assignable roles: Admin, Legal, Compliance, and Viewer. At least one is required. Pending Admin and Pending Legal are not selectable when creating a user.
Associate with Agency	Yes	Single-select dropdown of every agency in your organization. Determines which branch the user belongs to and which compliance data they see by default.

Click Add at the bottom of the slide-over. The button stays disabled until every required field is valid.
The slide-over closes and the new user appears in the Users table. Turris invites them to your organization so they can sign in.

Tip: The Add User form includes its own View Role Permissions button directly below the Role field. Open it to confirm exactly what each role grants before you assign, so you can pick the smallest role that gives the new hire what they need.

Warning: The Email field locks the moment the user is created. If you mistype the email, there is no rename: you have to recreate the user. Double-check the spelling before you click Add.

Updating a User

When you'd do this. A Compliance user has been promoted to Admin, a teammate has moved branches, or you need to correct a position title before an audit.

In the Users table, click the row of the user you want to update.
The Update User slide-over opens. Its subtitle shows the user's first and last name.
Edit the available fields:
- First Name, Last Name, and Position (optional) are editable.
- Email is locked and shown in disabled grey.
- Role and Associate with Agency appear only when you are signed in as an Admin. Role is multi-select: remove a role by clicking its x, add one by picking from the dropdown.
- Associate with Agency is locked when the user you are editing holds the Admin role, because Admins span every branch.
Click Update at the bottom of the slide-over. The button stays disabled until you change at least one field.

Note: If a role you assign is not part of your subscription, the update is rejected and the alert names the role. Open View Role Permissions to confirm what your plan supports.

Permission rules for updates

Admins can update any user's name, position, roles, and agency assignment. The Role and Associate with Agency fields appear only for Admins.
Non-Admins can update only their own record (name and position). Clicking any other user's row triggers the alert You do not have permission to update users. and the slide-over does not open.
The Email field is always locked when editing an existing user. It can only be set at creation.
The Associate with Agency field is read-only when the user being edited is an Admin. To pin an Admin to a specific branch, change their role first.

Editing Your Own Profile

When you'd do this. Your last name changed, you took a new title, or you want to fix a typo in your own record without involving an Admin.

Click Edit My Profile in the top-right of the Users panel. Every signed-in user sees this button.
The Update User slide-over opens, pre-filled with your own record. The subtitle shows your name.
Update your First Name, Last Name, or Position (optional).
Click Update.

If you are not an Admin, your Email, Role, and Associate with Agency are not editable here: ask an Admin to change those for you. If you are an Admin, the Role field is available on your own record too, so take care not to remove your own Admin access (see Best Practices).

Roles

Roles decide what each user can read and write across the downstream app. Roles are assigned by Admins from the Role field in the slide-over, and at least one role is required per user. A user can hold more than one role at once and receives the combined access of every assigned role.

Role	What it does
Admin	Full access to all features and settings, including managing users and organization settings. Admins span every branch, so the Associate with Agency field does not apply to them.
Legal	Can view users and update their own profile, with full read/write access on Org Structure and Documents.
Compliance	Can view users and update their own profile, view Org Structure, and has full read/write access on Documents settings.
Viewer	Can view settings and every sub-menu, but the create, update, and delete buttons are hidden.

You may also see Pending Admin or Pending Legal badges on existing users. These are transitional roles applied during onboarding: a user who holds only a pending role cannot even see the Settings button in their nav bar. When you edit a user who has a pending role, the Role dropdown shows every option so you can convert them to Admin or Legal and finish provisioning them.

Tip: When a user wears two hats, combine roles instead of escalating to Admin. Assigning Legal plus Compliance is safer than handing out Admin "just to be sure."

Viewing Role Permissions

When you'd do this. Before assigning a role you have not used before, or when answering a teammate's question about whether a specific feature is open to their role.

Click View Role Permissions in the top-right of the Users panel (the icon is a question mark inside a circle). The same button also lives inside the Add User and Update User forms, next to the Role field.
A full-screen Role Permissions reference opens, listing every feature and settings area down the left side and every role across the top.
Each cell shows whether that role has read access, write access, both, or neither for that feature.
Your own role's column is highlighted so you can quickly see what you personally can do.
Features that depend on a premium subscription tier are flagged in the table. Features your organization does not have access to at all are hidden so the table stays readable.
Close the reference by clicking the X in the top-right corner, clicking the backdrop, or pressing Esc.

Frequently Asked Questions

Why don't I see an active Create User button? Creating users requires the matching permission, which in practice is the Admin role. If the button shows a feature-locked state, your account does not currently have that permission. Ask an Admin to grant you the role, or to add the new user on your behalf.

Can I change a user's email address? No. The Email field is locked once the user is created. If the email is wrong, recreate the user with the correct address.

Can I update my own role? If you are not an Admin, no: the Role field does not appear when you edit your own profile. If you are an Admin, the Role field is available on your own record, so it is your responsibility not to remove your own Admin access by mistake. Keep a second Admin in place as a safety net.

Can a user have more than one role? Yes. Pick multiple roles from the Role dropdown when adding or updating a user. The user receives the combined permissions of every assigned role.

Can a user belong to more than one agency? A user is associated with one agency at a time through the Associate with Agency field. To move someone, an Admin edits their record and picks a different agency. Admin-role users span every branch automatically, so the field is locked for them.

Why does the Users table show "No Users Available" right after I filtered? Your filter probably excluded every user. Open the Filter dropdown and switch to All Agencies to confirm whether the issue is the filter or a genuinely empty roster.

What do the "Pending Admin" and "Pending Legal" badges mean? They are transitional roles assigned during onboarding before a user is fully activated. A user who holds only a pending role cannot see the Settings menu yet. Edit the user and assign them the standard Admin or Legal role to finish provisioning them.

Why am I seeing a "You do not have permission to update users" alert? Non-Admins can only open their own profile. Clicking any other user's row triggers this alert. Use Edit My Profile instead, or ask an Admin to make the change.

Best Practices

Assign Admin sparingly. The Admin role grants control over every setting, including who else gets Admin. Reserve it for the smallest group that genuinely needs it.
Keep at least two Admins. If your only Admin leaves or loses access, no one else can promote a replacement. Two Admins is the minimum safe configuration, and it also protects you if one Admin removes their own access by accident.
Match the role to the responsibility. Reach for Compliance, Legal, or Viewer first, and escalate to Admin only when none of those cover what the user actually needs to do.
Pin every non-Admin to the right agency. The agency filter, the per-branch documents view, and several reports rely on Associate with Agency being correct. Set it accurately when you create the user.
Combine roles instead of escalating. A user who needs both legal and compliance access should hold Legal plus Compliance, not Admin.
Double-check the email before clicking Add. Email is the only field that cannot be edited later. A typo means recreating the user.
Open Role Permissions when you are unsure. The matrix is the authoritative reference and is faster than guessing from a role name.
Keep names and positions current. Accurate First Name, Last Name, and Position values keep the Users table readable for everyone as the team grows.

Contacts (Settings): Keep one organization-wide directory of the people your agencies rely on when working with markets, scoped to one or more agencies with business roles.
Documents (Settings): Keep every compliance document (E&O, Cyber, Crime & Fidelity, W9) for your organization in one place, with each row showing whether an entity's document is current, expiring, expired, or missing.
Billing: Invoices: A single, searchable history of every Stripe invoice issued to your organization, so finance can reconcile what was billed, what was paid, and which card or account covered each charge.
Settings: Personal Notifications: Choose how Turris alerts you about activity across the agencies and agents you manage (email, in-app inbox, both, or neither), per event type.
Org Structure (Settings): Model your organization as a parent agency (TopCo) with branches underneath it, then review the hierarchy, add branches, rename them, take over market-created branches, and merge branches that share an NPN.
Payment Methods (Settings): Save and manage the cards billing admins use to pay Turris invoices for renewals, license fees, and subscription charges, so the next checkout takes one click.