Team and security

A workspace belongs to a team. Settings → Team decides who is in it and what each person may do, and Settings → General holds your own account, sessions and single sign-on. Settings → MCP access lets you use Polo from an editor or a terminal.

Roles

Role	What it lets you do
Viewer	Sees tasks, results and settings. Can’t assign work, approve changes or change settings.
Operator	Assigns tasks and manages recurring work. Answers Polo’s questions. Approves changes where the approval rules allow operators. Can’t manage members, connections or AI models.
Administrator	Everything an operator can do, plus members, connections, AI models and approval rules.

Who may approve a particular change also depends on the approval rules. Administrators can always approve; viewers never can. A change of role or a removal takes effect immediately.

Invite someone

1. Open Settings → Team and press Invite someone.
2. Enter their Email and choose a Role.
3. Set Link expires after (hours) and press Create invitation.
4. Copy the invitation link and share it with that person. Polo shows it only once.

The link works only for that email address and can be used once. The Invitations tab lists the links you have sent and whether they were used. Press Revoke invitation to cancel one.

Manage members

The Members tab lists everyone in the workspace with their role and when they joined. Search by name or email.

1. Press Change role or remove on a member.
2. Choose a new Workspace role and press Save role, or press Remove member.

Removing a member ends their sessions in this workspace and stops their MCP access tokens.

Your account and sessions

Settings → General has three tabs.

Tab	What it holds
Account	Who you are signed in as, your role, the theme, Switch workspace and Sign out
Security	Email verification, your password and your browser sessions
Single sign-on	Sign-in with Google or Microsoft

• Password. A password has at least 12 characters. Changing it signs out your other Polo sessions across workspaces; the session you are in stays signed in.
• Browser sessions. Lists where you are signed in to this workspace. Sign out one session, or press Sign out other sessions.
• Email verification. Press Request verification link to confirm the address you sign in with.

Sign-in attempts are rate limited, and a session expires after a fixed time set by whoever runs Polo (7 days by default).

Single sign-on

Members can sign in with Google or Microsoft where the deployment has single sign-on turned on. If it is not, the tab says so; ask whoever runs Polo for your team.

For an administrator:

1. Open Settings → General → Single sign-on.
2. In your identity provider, add the redirect address the page shows as a web redirect URI.
3. Open Configure Google or Configure Microsoft, enter the provider’s client credentials and save. Microsoft also needs your directory.

For each member:

1. Open the same tab and choose Link my Google account or Link my Microsoft account.
2. Continue to the provider and sign in.

Google accepts Google Workspace or Google accounts with a verified email. Microsoft accepts work accounts from the configured directory.

Caution

Saving new provider credentials signs out everyone who signed in with that provider. Disabling a provider ends its active workspace sessions. Unlinking your account signs you out of the sessions you started with it.

MCP access

Polo is also an MCP server. From Claude Code, Codex, Cursor or any client that speaks MCP over Streamable HTTP, you can ask your agents, follow their work and set their rules.

Create an access token

1. Open Settings → MCP access and press Create access token.
2. Enter a Name after the client that will use it, such as “Claude Code on my laptop”.
3. Choose what it may do: Read only or Read and act. Optionally tick Also let it approve or reject proposed changes.
4. Choose when it Expires: in 30 days, 90 days, 1 year, or never.
5. Press Create token and copy it now. Polo keeps only a fingerprint and cannot show it again.
6. Under Connect a client, pick Claude Code, Codex, Cursor or Other and copy the command or configuration shown.

What a token can do

Scope	Allows
Read only	See tasks and their results, agents, approvals, incidents and monitors, cloud infrastructure, connections, knowledge, reports and cost. Changes nothing.
Read and act	Also ask an agent to do work, answer its questions, stop a task, tell an agent what it must always or never do, and add monitors, recurring tasks and knowledge.
Approve changes	Also approve or reject a proposed change. The approval rules still decide who may approve what.
Never	No token reaches passwords and sign-in, team members and roles, the vault’s secrets, AI model keys or the tokens themselves.

A token works as you, within your role. A viewer’s tokens are read-only. A change an agent proposes still waits for approval. Press Revoke on a token and its client stops at once; a token also stops when it expires or when you leave the workspace.

The same token signs in the plungo command line, which the MCP access page shows how to install. Details for client developers are in MCP.

Connecting MCP servers to Polo

This is the other direction: giving your agents tools from an MCP server you run. It is on the Tools page (Apps → MCP servers). Polo lists what a server offers, and an administrator grants individual tools to agents. A tool that changes something needs a read tool that verifies it, and still waits for approval on the task.

What protects a workspace

• Each workspace’s data is separated from every other workspace’s in the database.
• Secrets, model keys and runner keys are encrypted and never returned by any page or API.
• Every change outside Polo’s own working copy needs an approval and is recorded with who approved it.

For the full list of controls, see Security.