# What to ask your administrator for

> A checklist for IT: the connector, the document connection, the space as the workplace, sections and folders, the connection test; systems not in the catalogue.

Your IT specialist connects documents to a space once. Here is what to hand over: a five-point checklist and links to the technical pages. They do not need to understand how your department works — only where the documents are and which space reads them.

## Checklist

Copy it, fill in the blanks and send it to IT.

1. **The connector is installed** — on a machine in the company network that has access to the documents and outbound internet access; for Figma without a list of files and projects, also inbound access from the internet to the event receiver. One connector serves all departments; if it is already installed for another department or for development, there is no need for a second one. → [Installation](/en/docs/connector/install)
2. **The right connection is set up from the catalogue** — `___` (Notion / Confluence / Google Drive / files on a server and network folders / Figma / tracker / internet). → [Catalogue](/en/docs/connector/marketplace), source pages: [Notion](/en/docs/connector/notion), [Google Drive](/en/docs/connector/google-drive), [Files on disk](/en/docs/connector/files), [Confluence and Figma](/en/docs/connector/knowledge), [Trackers](/en/docs/connector/trackers), [Internet](/en/docs/connector/web)
3. **The connection names the space** — the connection’s “Development project” field holds the space name `___` (yes, that is what the field is called — the space goes into it too). Without this the AI agent in the space will not see the connection’s tools. → [Tools and the model](/en/docs/connector/tools)
4. **Sections and folders are selected** — the connection’s roots: links to Notion pages `___`, Confluence space keys `___`, Drive folders `___`, paths on the server `___`, Figma files or projects `___` (if left empty, the connector’s event receiver must be reachable from the internet and a `FILE_COMMENT` webhook must be set up in Figma, otherwise questions in design comments will not get through); exclusions — folders that must not be read (personnel files, archive). For trackers an empty list means “nowhere”; for Notion, Confluence, Google Drive, Figma and files it means “everything the account can access”; selecting sections explicitly is more reliable either way. → [Scope](/en/docs/connector/knowledge#visibility-scope)
5. **“Test connection” has passed** — the check answers not with “ok” but with who signed in and how many of the selected sections are actually accessible; the connection’s status is “running”. → [Management](/en/docs/connector/manage)

**What to prepare on your side:** where the documents are (section addresses, folders), the name of the space, who in the department needs access and with which role (see [Roles](/en/docs/teams/roles)).

## What you can do yourself, without IT

- **Google Drive** — share the folder you need with the account address IT gives you (looking like `name@project.iam.gserviceaccount.com`), with the “Commenter” permission: that is enough for reading and for replying in comments.
- **Notion** — add the integration to a section: on the root page, menu “…” → “Connections” → pick the integration. Everything nested opens along with it; connect a section, not the whole workspace.

## A system not in the catalogue

A CRM (Bitrix24, amoCRM), 1C, a helpdesk, a messenger, SharePoint, an HR system — they are not in the ready-made catalogue, and that does not mean “not supported”. Your own system is connected with **your own tool** — [your own MCP server](/en/docs/connector/custom-mcp) (MCP is the standard way to connect a program to an AI agent; this is IT work): IT downloads a ready one (the vendor’s server or one from an open repository) or writes one, adds it to the connector and marks the tools that only read — and the system is available to the AI agent at once, on a par with the catalogue, in every question and research in the space.

Two differences from the catalogue are worth knowing: such a tool gives the AI agent read-only access to the application — it cannot take requests as comments from inside the system; and its code has not been checked by Buff, so IT confirms the installation explicitly.

## If the answer after connecting is “not found”

The three usual causes — the folder is not selected as a root, the connection is not running, the account has no access to the folder — are covered on the [How to ask a good question](/en/docs/asking-well#what-not-found-means) page. The status and last error of each connection are visible in the app’s “Connectors” section.