# Roll out Opisense in a company

Rollouts that work start with a few teams and a few real jobs, prove the time saved, and then grow
team by team. This page covers the decisions to make first, a pilot, and what keeps it running.

## Decide where it runs

- **Opisense Cloud** at [bots.opisense.com](https://bots.opisense.com): nothing to install.
  Opisense runs the models and the bots' computers, and the team pays per seat. See
  [Account and billing](/docs/account/#billing-on-opisense-cloud).
- **Your own server**: your network, your models (including ones you run yourself), and sign-in
  through your company's identity provider.<!-- self-hosted --> See
  [Self-hosting](/docs/self-host/).<!-- /self-hosted -->

Choose your own server when data must stay inside your network, when you need single sign-on, or
when you must use your own model contracts.

## Check what you need

| You need | What Opisense offers today |
| --- | --- |
| Single sign-on | On your own server, one OpenID Connect provider, such as Microsoft Entra ID, Okta or Google Workspace.<!-- self-hosted --> See [Sign-in and accounts](/docs/self-host-accounts/#openid-connect-sso).<!-- /self-hosted --> Passkeys work everywhere. No SAML or SCIM yet. |
| Roles | Owner, Admin and Member. See [Teams](/docs/teams/#roles). |
| Keeping work apart | A team space per department, project or client. Chats, memory and app connections are per person. See [What's shared in a team space](/docs/team-setup/#whats-shared-in-a-team-space). |
| Control over actions | Approval mode and Block rules per person; **Disable a tool** on a shared bot for everyone. There is no company-wide approval policy yet. See [Approvals](/docs/approvals/). |
| Bots in meetings | On Opisense Cloud on a paid plan, and on your own server once meeting bots are set up, anyone in the team can send a bot to a Google Meet, Zoom or Microsoft Teams meeting; owners and admins can turn **Meetings** off for the whole team. Opisense keeps the transcript, the meeting chat and the notes, and stores no audio or video. See [Meetings](/docs/meetings/). |
| An audit trail | Invites, role changes, approvals, tool use and credential changes are recorded. Owners and admins can export it. See [Audit log](/docs/teams/#audit-log). |
| Data protection | Encryption at rest, per-person export and deletion. Chats are kept until deleted; there's no retention setting yet. See [Security and privacy](/docs/security-and-privacy/). |
| Cost control | One shared pool of credits that only the owner tops up. No spending caps yet. |
| Paperwork | DPA, security documents and subprocessors in the [Trust Center](https://www.opisense.com/en/trust-center). |

## Run a pilot

1. **Pick one or two teams and two or three jobs each**: work that repeats every week, such as
   meeting prep, a weekly report or first replies to requests. Write down how long each takes today.
2. **Name the people**: one owner who handles billing, one or two admins, and a champion in each
   team who collects feedback and helps colleagues.
3. **Set it up**: a team space per pilot team, one shared bot per job, your
   [design system](/docs/design-system/), and [knowledge sources](/docs/memory/#knowledge-sources) for
   the documents those jobs need. Follow [Set up a team](/docs/team-setup/).
4. **Agree on approvals**: approval settings are per person, so put the baseline in the welcome
   message. For example: keep **Auto review** or **Ask me**, never use **Never ask** in a space where
   bots read email or the web, and add a **Block** rule for anything nobody's bot may do.
5. **Run it for two to four weeks.** Each week, champions bring back what went wrong, and each
   bot's owner fixes its instructions.
6. **Measure** against your notes from step 1: time per job, how many people use the bots each
   week, and runs that failed or waited (in **Activity**). Ask people to check their own
   **Settings → Usage**, since there's no team-wide view yet; the owner sees what's left of the
   team's allowance and credits in **Settings → Billing**.

## Roll out

- Expand team by team. Start each new team with the bots that proved themselves: make the same bot in
  the new team's space and copy its instructions from **Advanced** → **Instructions**.
- Invites go one address at a time, at most 50 a day per team, so plan a large rollout over a few
  days.
- Keep one page that lists the team's bots, what each is for and who owns it. A bot can make it:
  "make a page listing our shared bots and their owners", then share it with the space.
- Give people a short first session: chatting with a bot, answering approval cards, connecting
  their apps, and what never to paste into a chat (passwords and keys go in the Vault).

## Keep it healthy

- **Every shared bot has an owner.** Only its maker and the admins can change it. Before someone
  leaves, decide who takes over their bots and knowledge sources. See
  [When someone leaves](/docs/team-setup/#when-someone-leaves).
- **Review each quarter**: archive bots nobody uses, check who is admin, decide whether
  **Public page links** and **Meetings** should stay on, and look through the audit log.
- **Changes are traceable**: each bot's **Instruction history** shows every version, and the audit
  log records approvals and tool use.
- **New bots go through an owner.** Ask people to check for an existing bot before making a new
  one, and to build bots that act outside the company, such as in a customer's Slack, with an admin.
