Getting started
Connecting services to spaces
Connect an outside service once, then choose which spaces use it: one space at a time, by tag, or by integration.
Last updated:
Connection and access
A connection (your Yandex Disk, for example) is made once on the Integrations page of the dashboard. On its own it opens nothing to the agent: the service is available only to the spaces you attach it to.
- Only the space owner can attach and detach. An archived space cannot be attached.
- The agent acts as the account you connected and sees what that account sees. Every member of the space who may address the agent gets that access.
- Keys and tokens are stored encrypted and are never sent to the browser or to a model.
- Detaching takes effect immediately; files and data in the service itself stay where they are. Reconnecting the same account restores the earlier attachments.
Three ways to attach
| Way | What gets access | When it fits |
|---|---|---|
| By space | One space you pick | Targeted access, for example one working chat |
| By tag | Every space with that tag, including future ones | Groups of spaces: a team, a client, a project |
| By integration | Every space of one integration, for example all chats of a Yandex 360 organization | The whole company needs the service |
Each connector's page shows the ways available for it. When a space gets a service in more than one way, the direct space attachment is the one that applies.
Space capabilities
Besides attachments, a space has a list of enabled capabilities (web search, files, images, Yandex Disk and others). The owner changes it on the Settings tab of the status page. For Yandex 360 spaces the default set comes from the integration console. Details per service: Yandex Disk, Yandex Tracker, Yandex Mail, Google.