> ## Documentation Index > Fetch the complete documentation index at: https://docs.hyperspell.com/llms.txt > Use this file to discover all available pages before exploring further. # Configuration > Every setting in the Hyperspell dashboard, what it does, and who can change it. Almost everything in Hyperspell is configured from Settings in the dashboard. Settings are split into two groups. Personal settings affect only you: your profile, your connected accounts, your agents. Admin settings affect the whole organization: integrations, members, content rules, API keys. Admins see both groups. Members see only the personal group. This page walks through each section. [Content rules](/advanced/content-rules) and [connecting agents](/agents/overview) have their own pages and are only summarized here. ## Personal settings ### Profile Your name and avatar, and the dashboard theme: light, dark, or follow the system. The theme applies to the browser you set it in. ### Connect Agents Setup instructions for Claude, ChatGPT, MCP clients, and the command line tool, each pre-filled with what you need. See [Connecting agents](/agents/overview). Below the agent options is your personal API keys list. Keys created here are tied to your account and see exactly what you see. Create one for an agent that acts on your behalf, and revoke it here when you no longer need it. Revoking takes effect immediately. ### Connections The tools your admin has set up as personal integrations, with your own connection state for each. Click Connect to sign in to a tool with your account, or Disconnect to remove your connection and the data it brought in. Some tools let you narrow what Hyperspell reads from your account: * Slack and Microsoft Teams let you pick channels. Direct messages and private channels are included only if your admin allows them and you select them. * Google Drive and Dropbox let you pick folders. You can also choose whether files shared with you that sit outside any folder are included. If a tool supports several accounts, for example two Gmail addresses, you can connect each one, provided your admin has allowed multiple connections for that tool. ## Admin settings ### Organization Your organization's name and logo, as shown to members. Admins can edit both. Usage and billing live on the same page: your current plan, how much of each limit you have used, and, where self-service is enabled, the option to change plans. Any member can see usage. Only admins can change the plan. ### Members The people in your organization and their roles. | Role | Can do | | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Member | Use the brain, connect their own personal tools and agents, create personal API keys. | | Admin | Everything a member can, plus: add and configure integrations, write content rules, invite and remove members, change roles, create organization-wide API keys, manage billing. | Invite people by entering one or more email addresses. Invitations show as pending until accepted. For existing members, the Edit menu lets you change a role or remove someone from the organization. Removing a member revokes their access, deletes documents only they could see, and keeps everything that was shared. See [When people leave](/core/permissions#when-people-leave). ### Integrations The list of tools connected to your brain, with a health indicator for each: syncing, live, waiting for first sync, reconnect required, and so on. #### Adding an integration Click Add Integration and choose a tool. You are then asked how it should be set up: * Shared: one credential for the whole team, connected once by an admin. Its data is visible to everyone in the organization. * Personal: each member connects their own account. Their data is private to them by default. * Both, where the tool supports it. Shared is offered only for tools that support a service account or API key. Email and calendars, for example, are personal only. The choice is not permanent; you can change it on the integration's page later. Hyperspell does not copy the source tool's permission settings. Everything a shared credential can read becomes visible to everyone in your organization. Choose shared only for tools whose content the whole company may see, and use [filter rules](/advanced/content-rules#filter-rules) to hold back specific categories. Meeting-notes tools are the one exception: Gong, Fireflies, Fathom, Fellow, and Granola. Recordings often include one-on-ones, so a shared connection for these tools does not make its content visible to everyone automatically. If you want a company-wide meeting corpus, [tell us](mailto:hello@hyperspell.com) when you connect it and we will turn that on. #### Configuring an integration Each integration has its own page. At the top, two switches control the connection modes: * Allow personal connections. Members can connect their own accounts. * Allow shared connections. A team-wide credential can be set up. Turning a mode off hides its settings but never disconnects existing connections. To remove connections, do so explicitly in the sections below. The Configuration section holds the options that shape what gets indexed. The exact options depend on the tool. The most common are: | Option | What it does | | ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | | History window | How far back to index: 30, 90, 180, or 365 days, or everything. Defaults are 180 days for documents and issues, 90 days for mail, messages, and CRM records. | | Channel defaults (Slack, Teams) | Which channels new connections index by default: public channels, private channels, direct messages. Members can still narrow their own selection. | | Folder options (Drive, Dropbox) | Whether to index only files the connecting person owns, whether to require a folder selection before anything syncs, whether to include spreadsheets. | | Mail options (Gmail, Outlook) | Skip newsletters, bounces, and auto-replies. Optionally surface only conversations the person took part in. | | Object types (CRMs) | Which record types to index, such as contacts, companies, and deals. | | Repositories and file patterns (GitHub, GitLab) | Which organizations and repositories to include, and file patterns to include or exclude. | Changing an option applies to data received from then on. When you save, Hyperspell asks whether to also re-sync existing connections so the new options apply to what is already indexed. The Personal connections section lists each member's connection with its folder or channel selection, lets you allow multiple connections per person, and offers a re-sync. The Shared connection section is where an admin enters the service account or API key, or replaces it later. Each tool's [integration page](/integrations/overview) shows where to find these credentials. Deleting an integration disconnects every connection for every member and stops syncing. Already indexed content is not deleted but stops updating. You are asked to type the integration's name to confirm. #### External MCP servers If your company runs its own MCP servers, for example over an internal database or a custom tool, admins can register them as live sources. Hyperspell queries them at answer time and cites the results, but never indexes or stores what they return. Registering a server takes a label, a public HTTPS URL, and an optional bearer token. Hyperspell then lists the server's tools, and you approve the ones the brain may call. Nothing is approved by default, and a tool whose definition changes is suspended until you approve it again. All members share the one credential you enter, so only connect servers whose content the whole organization may see. ### Content rules Filter rules and sharing rules. See [Content rules](/advanced/content-rules). ### API Keys Keys created here are organization-wide. They are not tied to a person and see only content shared with the whole organization. Use them for a team bot, an internal tool, or any agent that should never see personal data. When creating a key you choose a label and the permissions it carries: reading memories, adding and removing memories, reading and managing connections, running actions, and organization-level access. A write permission includes its read counterpart. New keys default to read-only. The key is shown once, at creation. Copy it then. Personal keys that members created from Connect Agents are listed separately on this page, with the owner's name, so admins can see and revoke them. ### Advanced Settings that most organizations never need to touch. Webhooks let another system know when something happens in Hyperspell. Enter a URL, choose which events to send, and use the test button to check the connection. Events available: a member connects a new account, a data source finishes syncing, and a new memory becomes available. The redirect URL is where Hyperspell Connect, the hosted page for connecting accounts, sends people when they are done. Most organizations leave it empty. Source weights let you tell the brain to lean on some tools more than others when compiling pages: high, normal, low, or excluded per tool. A separate switch controls whether compiled pages include citations back to their sources. ## Generated pages Hyperspell compiles pages about your company, its projects, and its people from what it has indexed. These are what the [command line tool](/agents/cli) syncs to disk and what agents read with the context tools. A few things about them can be configured, under File System in the dashboard. * Organization type. Hyperspell detects whether you are, for example, a client services firm, a sales-driven company, a legal practice, or an engineering organization, and adjusts which pages it writes. You can override the detection. * Structure. Admins can adjust the instructions used to write each tier of pages, or define a custom set of pages with their own prompts and search queries. * Canonical documents. Documents you write or upload that outrank anything Hyperspell infers. Use them for policies, org charts, or the official version of a process. * Category filter. Categories stripped from shared pages before they are stored: HR matters, personal information, fundraising, passwords and secrets, hiring and firing, plus any you add. This applies only to generated pages. Filter rules for indexed content are covered under [content rules](/advanced/content-rules). * Skills. Procedures and memos delivered to agents word for word, without any rewriting. * People. The directory used to write personal pages and to identify people on the command line tool. ## Regions Your organization lives in one region, chosen at sign-up: the United States or the European Union. Data is stored and processed in that region and never copied to the other. The dashboard, API, and MCP endpoints differ by region. See [Regions and data residency](/resources/data-residency). ## Not configurable from the dashboard A few things need a message to [support](mailto:hello@hyperspell.com): * Renaming or deleting the app that holds your brain. * Erasing all of your organization's data. * Moving an organization between regions, which is not possible; create a new organization in the other region instead.