Console
What the console can make AgentX on a computer do.
These are the actions the hosted console can take on AgentX on a connected computer, and who can take them.
Any signed-in member of the team, including a viewer, can start a session and, when remote shell is on, start a shell. A viewer can stop and resume a session the owner started. Any active member of a team, including a viewer, can give an agent instructions by starting a session on it and sending or typing there. A viewer can also type into a session the owner started. A viewer's message into the owner's session is refused. Creating, changing, pausing, deleting, or running an automation does not check the member's role.
On an enrolled team, an owner or an admin can create, change, or delete any agent, including its avatar. A member can do that only for an agent they own. A viewer cannot. An active listed computer manager can also create, change, and delete agents. A manager is a person listed as a manager of that computer. The person who connected the computer can add or remove its managers.
Saving an environment variable is limited to an owner, an admin, a member on an agent they own, or an active listed computer manager. A viewer cannot.
Any member of an enrolled team, including a viewer, can save an MCP server. It is saved in the agent's MCP configuration, which its program reads when it starts. The same member can turn that server on or off, or delete it. There is no role check on those actions. Reading one saved value still needs the same permission as saving an environment variable.
A viewer can download a file from the team's file list, for example a file in an agent's workspace. Sending a file to an agent does not check the member's role. The check is that the person is signed in and that the file belongs to the team.
An owner or an admin can delete any chat. Another signed-in member can delete only a chat they own.
Reading output, chat history, the file list, skills, and memories checks that the person is signed in and that the object is on the team. It does not use the create, change, or delete permissions.