# Who sees what

Everything you create is visible only to you at first: an agent, a skill, a task, a prompt template, a connection, a chat. Teammates in your organization see it only once you share it. You share each thing separately: for example, share a skill and an integration with the organization while keeping the agent and your chats to yourself.

## Access levels

Wherever you can share, the choice is named the same way:

- **Only you**: only you see and use it. This is the default.
- **Organization**: everyone in your organization.
- **Anyone with the link**: anyone who has the link. Available for skills and chats.
- **Selected members**: only the teammates you check. Available for integrations.

| What | Levels | Where to change it |
| --- | --- | --- |
| Agent | Only you, Organization | Settings → Agents → the agent → Access → Who can message the agent |
| Skill | Only you, Organization, Anyone with the link | Settings → Skills → the skill → Visibility, or Share skill |
| Task | Only you, Organization | The task → Visibility |
| Prompt template | Only you, Organization | Settings → Prompt templates → the template → Access |
| Integration | Only you, Organization, Selected members | Integrations → the connection → Access → Who can use it |
| Chat | No link, Organization, Anyone with the link | Chat header → Share → Who can access |

Whoever created it can change access. An organization admin can also share or unshare an integration.

## Chats

- **A direct chat** (you and one agent) is seen only by you. Neither teammates nor admins read it.
- **A group chat** is seen by its members: the agents and teammates you invited. More: [Group chat](/help/group-chats).
- **Chat link.** With **Share** you can open a chat to the organization or to anyone with the link. A shared chat is read-only: only its author writes in it and continues the work. Turn the link off and the chat is yours alone again.
- **A chat with a shared agent.** When an agent is shared with the organization, everyone in it can read its chats. See below.

## An agent for the organization

You can share an agent with the whole organization: teammates message it themselves, and nobody has to set up the same agent again. There is still one owner, and the owner manages the agent's settings.

What teammates get:

- **Instructions.** A teammate sees the published instructions and accepts them with **Review and accept** before messaging the agent. When you change the instructions, teammates keep using the previous version until you click **Publish changes**.
- **Their own chats and services.** Each teammate messages the agent in their own chat and gives it their own connections. Your keys, your memory and your usage don't pass to them.
- **Read access to every chat with the agent.** Teammates can read the agent's full history, including your chats with it, and you can read theirs. Everyone writes only in their own chat: someone else's chat shows "This is …'s chat. You can only read it." Teammates' chats open from the **Agent chats** menu in the chat header.

**A shared agent opens its chats**
Teammates will also be able to read what you discussed with the agent before you shared it. If your chats should stay yours, keep your personal agent on Only you and create a separate agent for shared work, then share that one.

### Share access
Settings → Agents → the agent → **Access** → **Who can message the agent** → **Organization**. You can also ask the agent in a chat: it sends a card with a **Share** button, and you click it.

### The teammate starts a chat
The agent appears for the teammate in Settings → Agents under **Organization agents**. **Start a chat** opens its main chat.

### The teammate connects their services
While accepting the instructions, the teammate picks which of their connections to give the agent. If the integration is shared with the organization, no key of their own is needed.

To stop sharing, switch back to **Only you**. Teammates can no longer message the agent, their running replies stop, and their tasks with it pause. Your settings and chats stay as they are, and teammates no longer see your chats.

## Skills, tasks and templates

- **Skill.** Visible only to you by default. On Organization, teammates find it in the skill catalog and can use it; on Anyone with the link, any Сам Решу user can open it. You can also change a skill's visibility in a chat: "share the Supplier markup skill with the organization". More: [Agent skills](/help/skills).
- **Task.** Visibility: Only you (plus organization admins) or Organization, in which case everyone in the organization sees the task and its runs.
- **Prompt template.** On Organization, the template shows up in teammates' template list. When you save a template from a message, there is a **Share with organization** checkbox.

## Integrations

You can share a connection with teammates in its card, **Access** tab → **Who can use it**:

- **Only you**: you are the only one who can use the integration;
- **Organization**: any member of the organization;
- **Selected members**: only the teammates you check.

Teammates work through your connection, but only you and organization admins can see the keys: everyone else only gets to use them. Agent actions in the service run as the account the connection was created with, so a shared integration is better on a separate work account than on a personal one.

### Each employee's own email and 1C

- **An account for each person.** An employee signs in with their own email and connects their own mailbox, their own 1C database and other services. A connection starts on Only you: teammates don't use it and don't see its keys. Each employee needs their own seat in the organization's plan.
- **One account for several people.** A service can have several connections: in the connected service's card, click **Add another**, for example for a second mailbox. Then in each agent's card, under **Services**, leave only its own connection on. But sign-in, chats, memory and usage are shared on such an account: everyone who signs in to it sees everything. For separate chats and access, use separate accounts.

To make the organization's agents only read a service, an admin sets the **Changes** row in the connection card to **Read-only**: the agent then changes nothing, even when asked. More: [Connected services](/help/integrations).

## What an admin sees

- every task in the organization and its runs, including tasks on Only you;
- the keys of integrations shared with the organization;
- shared agents: an admin can stop sharing any of them but doesn't configure someone else's agent.

An admin doesn't read your direct chats, or group chats they aren't in, in the app.

## Inviting teammates

Invite a teammate in Settings → **Members** → **Invite a member**. Roles:

- **Member** works with agents and their own tasks, without access to billing and settings;
- **Admin**: everything a member does, plus people, billing, connections and settings. Only the owner assigns it.

Each teammate needs a free seat in the organization's plan. To work with someone from another company, add them in **Settings → Contacts**.