Sign inBook a demo
Organisation agents

Shared agents for every team, owned by the organisation.

Create an agent for a department once. It runs on company credentials, follows its own policies, works from the organisation Brain, and installs in Slack as its own named bot. People @mention it where work already happens, and every action stays under one policy and one audit trail.

Create once, deploy where work happens

A team agent with its own identity.

An admin creates the agent, grants it the company tools it needs and decides who can use it. Hosted agents install in Slack as a named bot with approval cards built in.

  • Its own identity, owned by the organisation, not by one employee
  • Company tools connected once by an admin, with shared credentials kept in the vault
  • Install as a named Slack bot, such as @finance-agent, in a few clicks
  • Organisation routines that run on a schedule as the organisation
Organization agentsCreate once. Deploy where work happens.
Admin managed
＋Create organization agentHosted · Operations
O
Operations agentHosted · Operations group
Governed
Named Slack bot@operations-agent · Approval cards and @mentions
One policy and audit trailConnected once
Examples

One agent per team, doing the work the team repeats.

@finance-agentFinance
StripeGoogle Drive

Answers "what did we bill Acme last quarter?" in Slack and chases overdue invoices every Monday.

Needs approvalRefunds over $500 wait for a finance approver.
@it-helpdeskIT
JiraSlack

Triages access requests and opens Jira tickets with the details already filled in.

Needs approvalGranting admin access always waits for IT.
@policy-agentPeople and legal
ConfluenceNotion

Answers policy questions from the handbook and links the source page.

BlockedIt can read policy pages, never edit them.
@sales-opsRevenue
SalesforceHubSpot

Keeps the pipeline clean and posts the Friday forecast to #leadership.

BlockedDeleting CRM records is not allowed.
Governed like every agent

Its own policies. The same guardrails.

Organisation agents never borrow a person's access. They get exactly the tools and actions an admin grants, and the platform guardrails apply on top.

Company credentials, connected once

An admin connects the company's Stripe, Jira or Salesforce once. Credentials stay in the vault, never with a person or the model.

Its own policies

Each agent gets exactly the tools and actions it is granted, with its own allow, approval and block rules.

Approvals reach the right person

When someone asks it in chat, the approval goes to them. A scheduled routine routes approvals to the operators you choose.

The same guardrails as every agent

Moderation, injection defence, automatic pause on breaches and per-agent spend caps apply from the moment it is created.

Give every team an agent it can rely on.

See an organisation agent answer in Slack, run a routine and route an approval in a 30-minute demo.