---
title: "Plan your team and agent keys"
description: "Plan who joins your workspace with which role, who gets an agent key, and a Gatlas agent for Slack."
url: https://www.gatlas.ai/docs/playbooks/team-and-access
markdown_url: https://www.gatlas.ai/docs/playbooks/team-and-access.md
---

# Plan your team and agent keys

Gatlas copies a business's numbers and files from the tools it uses into one place that AI agents can read. This playbook plans who reaches that data: the people in the workspace and their roles, the agent keys that let each person's agent read it, and a Gatlas agent that answers in Slack.

## How to run

Run the section the person's prompt names. If it names none, ask what they want to do and pick the section that fits.

No Gatlas tool makes these changes, so you work in this chat: interview the person, plan and draft, and leave each click in Gatlas to them. You need no Gatlas connection for any of it.

Ask one question at a time, and wait for the answer before the next. Never ask for a key or a password in this chat. Never delete anything.

## Invite your team

Help the person plan who to invite to Gatlas and with which role. Member explores all data, runs syncs, changes a dataset's settings and uses the agent keys an admin creates. Admin has full control of connections, datasets, briefs and members. Lead admin is an admin who can also add and remove admins. Each person sees all companies or specific ones.

Ask who needs access and to what, then give them a table of each person, their role and the companies they see, with the lowest role that does the job. The person invites each one under Settings, Members, themselves.

## Plan agent keys

Help the person plan who gets an agent key to Gatlas. A key lets one person's agent read Gatlas data. Each is Read-only or Read/write. A whole-workspace key reaches every company; a guest key, made for someone else, reaches only the companies or datasets they choose.

Ask who will ask questions, what each person should see and whether they should build datasets. Then give them a table of keys, each with a name, its permission and its access, and recommend Read-only for anyone who only asks questions.

The person creates each key on Agent access in Gatlas themselves. Each person then adds Gatlas as a custom connector in their agent with the server URL https://www.gatlas.ai/api/mcp. Each key's agent install link carries the key, so never ask for a key in this chat.

## Plan a Gatlas agent

Help the person plan a Gatlas agent for Slack. It answers questions about their companies' data in the channels they add it to, sees only the companies they choose, and stays within a monthly AI credit limit an admin sets.

Ask which channel it should answer in, who will ask it questions and which companies it should cover. Then suggest its name and its companies. The person creates the agent on the Gatlas agents page and adds it to Slack themselves.
