Skip to content
SurogateDocs

Members and roles

The Members tab lists the people in your active project and what each of them may do. Every member has one of three roles: Viewer, Editor or Owner. Owners add people, change roles and remove members. Anyone can leave, except the last owner.

The tab is in Settings and shows the active project; switch projects first to manage another (see The project switcher).

You need the Owner role.

  1. Open Settings, then Members.
  2. In the row above the table, type the person’s username or email in Username or email.
  3. Pick their role. The picker starts on Editor.
  4. Choose Add member.

The person must already have a Surogate account. The match is exact, so a part of a name or email finds nothing. If the add is refused, the form keeps what you typed and shows why:

  • No account has that username or email.: nobody matches exactly.
  • That account is deactivated.: the account exists but is switched off.
  • That person is already a member of this project.: change their role in the table instead.
  • Surogate Hub could not be reached, so nothing changed. Try again.: a temporary error; try again.

Roles rank Viewer, then Editor, then Owner, and each can do everything the one before it can.

WhatViewerEditorOwner
See the project’s agents, datasets, knowledge bases, skills, models, training runs and evaluationsYesYesYes
Create, edit and delete them, start and stop agents, run training and evaluations, save keys in the Vault. This covers anything that spends creditsNoYesYes
Chat with an agent, or in the PlaygroundNoYesYes
Open the project’s Sessions (conversations)NoYesYes
See who is in the project, and leave itYesYesYes
Add or remove members, change roles, rename the projectNoNoYes
See and cancel Paused workNoNoYes
Read the project’s sign-in settings (Authentication) and change themNoNoYes
See the plan, credits and usageYesYesYes
Change the plan, update the payment method, top up, change add-onsNoNoYes
Set up payouts for monetized agentsNoNoYes
Create, edit and delete a monetized agent’s offersNoYesYes

Platform administrators pass every one of these checks, in every project.

A viewer can look around but not touch. Controls that would change something are switched off, with the hint Viewers can’t change this project. The chat, the Playground and the Sessions page show that message instead of their content: a session holds a member’s chat with the agent, so viewers can’t open the project’s conversations. Make someone an editor if they need to read sessions.

An editor works in the project: builds and edits agents, runs training and evaluations, chats, and reads every member’s sessions. An editor can’t touch members, billing or the project’s own settings. Billing controls show Only owners can change this.

Owners also manage people, billing and project settings. The creator is the first owner; a project always keeps one.

Only the person who started a session can continue it (reply, take over the browser, archive, delete); others see Only the person who started this session can continue it under the chat box. Sessions started by end users on a channel have no starter, so members can only read them.

The platform copilot’s conversations are private to each person. Other members, including owners, don’t see them.

The table shows each member’s name, email, role, and when and by whom they were added. Owners also get a role picker on every row, and a Remove button on every row except their own. To leave yourself, use Leave project (below).

Change a role by picking another one in the row. It applies at once. You can change your own role, for example to hand ownership on and step down. Demoting the last owner is refused with A project needs an owner. Make another member an owner first.

Above the table, owners also see Project name with a Rename button.

Removing someone asks you to confirm, then takes away their access to the project. Data Hub groups follow automatically.

Leave project is under the table, for every role. It asks you to confirm and then removes you from the project. Your schedules and missions in it are paused, and the project disappears from your list. If you were the only owner, you can’t leave until you make another member an owner.

Work in a project runs as the person who started it. When that person can no longer run work there, the platform pauses it so it doesn’t keep spending the project’s credits. This happens when a member is removed, leaves or becomes a Viewer: their running sessions, schedules and missions are all paused.

Promoting someone back to editor does not resume anything. Their paused work stays paused.

Owners see the paused schedules and missions in a Paused work list under the members table. It appears only when something is paused. Each row shows the Kind (Schedule or Mission), the Title, the Member and when it was Paused. Choose Cancel on a row, then Cancel work to confirm. A cancelled schedule or mission can’t be resumed. Choose Keep to leave it as it is.

In Dev mode, the top of the navigation shows the active project and your role in it. Choose it to open a list of your projects, each with your role. Pick one to switch. Everything in the app, including the Members tab, then shows that project.

The list ends with New project, which asks for a Name and a Color. You become its owner.

The Work navigation has no switcher. Work uses the project you last picked, which your browser remembers, so switch in Dev mode first.

In every mode, platform administrators also get the Users and Phone numbers tabs in Settings. This page doesn’t cover them.

Enterprise installations differ in three ways. Only platform administrators create projects (others aren’t offered New project), and the Billing and Authentication tabs are hidden. Members and roles work as described above.