Title: Company workspace and team · Help · Steerbay
URL: https://www.steerbay.com/en/docs/company/
Language: English (Česky: https://www.steerbay.com/cs/docs/company/)
Summary: Shared context, workflows, roles and result review, on a dedicated server, with members' personal work kept separate. It starts with a call.

---

# Company workspace and team

Shared context, workflows, roles and result review, on a dedicated server, with members' personal work kept separate. It starts with a call.

## What the company workspace includes

- Shared company context the agents work from.
- Reusable workflows with versions and an acceptance check for the result.
- Owner, admin and member roles.
- Model selection for the work.
- Human review of results and a work history for audit.

Three starter templates are ready: supplier offer comparison, invoice review and a weekly operations brief.

We start the company workspace together, and it begins with a call. On it we go through your recurring work and agree the setup, the dedicated server, the scope and the price; scope and price are agreed individually. The For companies page describes how the call works and what to prepare. Book the call with the short form on the home page or the For companies page.

## A dedicated server

The company workspace runs on a server we set up for your company alone. No one else uses it.

- The company's data, meaning files, conversations, workflows and results, is stored on our servers only, not with other services.
- The agent's browser, tasks, schedules and the work on files run on this server.
- Data is encrypted in transit and at rest.
- Strict rules forbid sending data off the server. Only what the company approves goes out, such as a website the agent is to work on, or the model that reads the requests.
- Only people the company approves can reach the server and its data.

Which model the server uses, and what it may see, is agreed on the call. The Private deployment in Czechia guide has the details.

## What stays with each member

Shared context and workflows are separate from members' personal conversations and sign-ins. Website sign-ins and personal conversations stay with each member's account, and usage and limits are counted per member. SSO and pooled company billing are not available. Do not share one personal account instead of a company workspace.

## Company systems

Company systems are connected through setup notes and the agent's browser, not through ready-made universal connectors. The agent works in a system the way a person with an assigned account would. Check access with a read-only task first, then extend the workflow.

## Rollout: start with one process

1. Choose recurring work with available material and a clear result check, such as comparing offers or a regular brief.
2. Name the process owner, the permitted sources, the steps that must not happen and the person who judges whether the output is correct.
3. Do the task the usual way and record the time and the corrections it needed.
4. Try the workflow with the agent on authorized material and keep the request, the output and the errors found.
5. Run more examples, including an incomplete one, and compare consistency. Expand only once the criteria you set in advance are met.

## Teach the team to work with the agent

A team learns best on its own work, work it knows and can check. Everyone should be able to handle:

- one small task from request to reviewed output,
- the difference between a chat, a file, a signed-in website and a scheduled run,
- fixing an unclear request and handling missing information,
- pausing a workflow, removing access and handing a problem to the responsible person.

Before someone changes role, list the running schedules, the website accounts in use and where the important files are, and agree on new responsibilities.

Missing an answer? The AI help searches every guide and shows its source.