Staff and Roles
Part of the MountDev Ops Workspace documentation. Updated November 18, 2026
MountDev Ops Workspace documentation | Updated November 18, 2026
Who Can Use Your Workspace
Anyone your company has authorized on its MountDev account can sign in to your workspace. The first person to sign in becomes its owner. Everyone after that starts as a member, and an owner or admin can change their role.
The Staff Page
Staff (its first part is Team Members, formerly People) is where your business manages its staff members. It is the first page of the Staff app, in the People section of the menu (Staff). For companies without MountDev Ops in their plan, the same page is called Users and is in the Managed Services menu, after Transactional Email: everyone who can sign in to your account. The old Team address opens it. Hours and Pay, at the top of the list, opens People: everyone's hours and, for owners and admins, their pay and what their hours cost. Owners and admins see two tabs: People, and Groups, sets of people who share a kind of work, such as Support (Groups). The gear's Staff opens the page. What each person may do in each app, roles, and templates are in Staff, Permissions (Access and Permissions); Access beside a person opens theirs there.
It lists everyone in one place:
- In the workspace: each person's name (the name they chose in Profile, with the name they sign in with beside it when the two differ), email, role (Owner, Admin, or Member), role in each app, and when they were last seen.
- Invited: people on your MountDev account who can sign in (they approve paid work) and have not signed in yet. A contact on the account who cannot sign in, such as someone who only gets the monthly report, is a contact, not staff, so they are not listed here; find them in Billing, under Approvals and Reports.
- Turned off: people whose access an owner or admin turned off.
- Removed: people removed from your account, listed under Removed so their names stay on what they did.
Who approves paid work and who receives reports are settings of your MountDev account, so they are in Billing, under Approvals and Reports (The Workspace). The page refreshes on its own when anything changes, and every minute for your MountDev account.
Everyone in the workspace can see the list (action core.people.list, which also gives AI agents the list and changes nothing). Only owners and admins make changes, and nobody changes themselves:
- Invite a Person adds them to your MountDev account, the same as adding a person to the account, so they sign in with the one sign-in. They can sign in and approve paid work, and they get the monthly report; change either in Billing. We email them how to sign in. They join as a member the first time they sign in. Inviting someone whose access was turned off turns it on again.
- Invite a Person (accounts that sign in on their own) is on Users when your account has no account at the hub. Type their name and email address, choose the permission group they join, and choose Save Invitation (action
core.members.invite). The invitation is saved and nothing is emailed: the invitation email is off until the email list is final, so share the sign-in address with them yourself. They join as a member of that group when they accept, and they show on Users as Invited until they do. Cancel Invitation takes one back (core.members.cancel). Anyone with the permission to add and remove people sees the button, and a closed account does not have it. - Edit opens one person: their role in the workspace, and whether they are an AI assistant, with a link to their access in Staff, Permissions (Access and Permissions). Save changes only what you changed.
- Pay Rate, in the same pop up, is what the person costs an hour, an hourly rate or a salary, from a day on, with every rate they have had (Pay Rates). Only owners and admins see it.
- Turn Off Access stops them signing in and using the workspace, after you confirm. Everything they did and own stays as it is. Turn On Access lets them back in.
- Remove takes them off your MountDev account and removes their access, the same as Remove Access in Staff, Permissions (Client Protection), after you confirm. It works for someone whose access is already turned off too.
Turning off someone's access, or removing them, also takes them out of every group (Groups).
Your staff come from your own workspace people, never from a client's contact. When a person's contact moves from your account to another company (for example, a client account of their own), their access to your workspace is turned off, never deleted, and their name stays on what they did.
Removing a Person
Removing someone, with Remove here or Remove Access in Staff, Permissions, is the same everywhere in the workspace:
- Gone from every list. They are no longer offered anywhere you choose people: assigning work, owners and project managers, groups, channel members, @mentions in Chat, calls, and who is available for website chat. Nothing brought in later, such as an import, adds them back. The same is true while someone's access is only turned off.
- History stays. Everything they did, wrote, and own keeps their name, marked (Removed): their messages in Chat, the owner of their records, record history, and the Activity Log. Records they owned keep them as owner until someone gives the record to another person; nothing is reassigned for you. Open work they owned is worth handing to someone else.
- Direct messages stay readable. Your direct message with them stays in Chat, marked No longer on the team | Read only, and is closed to new messages. Nobody can start a new one with them.
- Signed out everywhere. Their open screens close at once, every device stops getting notifications from the workspace, and nothing new waits for them on the bell.
Inviting them again, or turning their access on, brings them back on the team, and the (Removed) mark goes away.
Roles
| Role | What it can do |
|---|---|
| Owner | Everything, including making or removing other owners. |
| Admin | Everything except changing who is an owner. |
| Member | Use the apps they have access to. |
Changing a Role
Changing someone's role (action core.people.set_role) needs the Manage People permission, which owners and admins have.
- Only an owner can make someone an owner, or change an owner's role.
- Every workspace keeps at least one owner. Make someone else an owner before changing your own role.
- Every role change is recorded in the activity log.
Turning Access Off and On
Turning someone's access off or on (action core.people.set_access) needs the Manage People permission, which owners and admins have.
- Nobody changes their own access, and only an owner can turn an owner's access off or on, so an owner with access always remains.
- A person whose access is off cannot sign in, use any screen, reach the Managed Services and Account pages, or act through an AI agent they connected. It takes effect on their very next request, even in a window they already have open. Their records, history, and roles stay as they are.
- Their roles in each app are kept, and come back into effect if they become a member again after being an owner or admin.
- Every change is recorded in the activity log.
AI agents can never change people, roles, or access. Those stay with people.
AI Assistants on the Staff Page
Sometimes a sign-in belongs to an AI assistant rather than a person, for example an account your team set up for an assistant to work in the workspace. Owners and admins open that sign-in with Edit on the Staff page and check This is an AI assistant, not a person (action core.people.set_assistant). Its row then shows AI assistant.
- The box shows for anyone who has signed in to the workspace at least once. Someone invited who has not signed in yet gets it after their first sign-in.
- An AI assistant is never offered when assigning work, such as a Helpdesk ticket, and assigning work to it is refused.
- Its access, roles, and everything it did stay as they are. Uncheck the box to make it a person again.
- Nobody marks themselves, and AI agents can never mark anyone. Every change is in the activity log.
AI agents people connect (AI Agents in the Account menu) and API keys are never listed as people, so they are never offered for assigning either. When two people share a name, their email address shows beside it wherever you assign work.
The Activity Log
The activity log (action core.audit.list) shows every change to your workspace's people and setup, and every file uploaded, downloaded, previewed, renamed, moved, or deleted (Files on Records): who did it, when, and whether an AI agent did it on someone's behalf. It also shows every call made with an API key, marked API key with the key's name, and every automation run that failed, marked Automation. Every Export Everything is there too: who started it, when it was ready, each download, and when its prepared copy was removed. Owners and admins can see it, 50 entries at a time, newest first, in the Activity Log card at the end of Settings (the Settings gear at the bottom of the menu, then Activity Log). The old Activity Log address opens it there.
The activity log is your company's alone. No one at MountDev can read it.
