OURTeams · Multiplayer workspaces

Your whole team,
one workspace.

Owners, operations staff, account managers, developers — and the agents working alongside them — in one workspace with scoped roles. Everyone works from the same company context; everyone approves the part of the work that is theirs.

5collaborators · Core
15collaborators · Pro
50viewers · Pro
Customseat limits · Enterprise
OURA day in one workspace

Four people. Four kinds of approval.

The owner approves the payment

A supplier invoice is ready to pay and a refund is waiting on a complaint. Both stop at the owner with the amount, the reason and the history attached — one tap each.

MoneyOwner

Operations runs the report

The weekly numbers are pulled, reconciled and written up. Operations checks the commentary and sends it on — without needing anyone's permission to run it.

ReportingOperations

The account manager reviews the reply

A drafted answer to a customer, written from your policies and that account's history. The account manager edits the tone and approves the send.

CustomersAccount management

The developer reviews the code change

For teams that also write software: the change arrives as a pull request on your branch with your CI green. A developer reviews the diff and merges it.

SoftwareEngineering
One shared context

Everybody works from the same picture.

Prices, policies, suppliers, past jobs, connected tools and email history live in one place that every person and every agent reads from. The reply the account manager approves quotes the same number as the invoice the owner pays — because there is one source, not four copies in four inboxes.

  • Real-time presence — see who is active and on which job
  • Shared integrations, one place to manage credentials
  • Complete history of every run, scoped to your team
Review flow

One person proposes. Another approves.

Anyone with an editor role can set a job running. What the agent produces waits for a person before it leaves the building — whether that is an email, an invoice, a published page or a merge. The approval is recorded against the person who gave it.

  • Any editor runs the job; the consequential step waits for sign-off
  • Admins hold the credentials and the integrations
  • Every approval attributed — who signed off, when, on what
Roles & permissions

Right access, right people.

Three built-in roles cover every team structure. Enterprise plans add custom roles with per-action granularity.

PermissionAdminEditorViewer
Run a task, report or build
Invite teammates
Approve what the agent produced
Manage integrations & credentials
View audit log
Read workspace output

Your whole team,
assembled in minutes.

Invite the owner, the operations staff, the account managers and the developers — roles, review flows and audit logs live from day one.

or talk to us about teams