> For the complete documentation index, see [llms.txt](https://alludium.gitbook.io/alludium-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://alludium.gitbook.io/alludium-docs/administration/6.-applications/7.-connections.md).

# Connections

Connections are the authenticated links between Alludium and an integration. They let Alludium use an external system without exposing credentials directly to agents.

**Location:** Administration -> Integrations -> open an integration -> Your Connections

Members may still be asked to create a personal connection when a task, project, or shared workflow needs access on their behalf.

## What A Connection Does

A connection stores scoped access for an integration. Depending on the provider, this may use OAuth, API keys, or another authentication method.

Connections can be:

* **User-scoped** - Each user connects their own account. This is common for personal tools such as email or calendar.
* **Workspace-scoped** - A shared workspace connection is used by workflows that should operate through shared credentials.

## How Connections Work

1. An Admin or Owner opens an integration, or a Member is prompted from a workflow that needs a personal connection.
2. The user reviews whether a connection is required.
3. The user creates a connection through the provider's setup flow.
4. Alludium stores the credential securely.
5. Tools from that integration become available where the workflow is allowed to use them.

Agents and tasks do not store credentials. They request tool access through Alludium's connection layer.

## Authentication Methods

### OAuth

OAuth redirects you to the provider so you can approve access without sharing your password with Alludium.

Common OAuth-style integrations include email, calendar, docs, CRM, communication, and project management providers.

### API Keys

Some integrations require an API key or token. Treat API keys as sensitive credentials:

* Use the least privilege key available.
* Rotate keys regularly.
* Remove keys that are no longer needed.
* Prefer read-only keys when a workflow does not need write access.

## Connection Health

A connection may be active, inactive, expired, or disconnected. If a workflow fails because it cannot reach an external system, check the connection first.

Before deleting a connection, review any agents, project setups, tasks, or automations that depend on it. Removing a connection can stop those workflows from running successfully.

## Shared Agents

When an agent is shared across a workspace, connection scoping matters. The builder may use shared connections for workspace-level systems, while each user may need to connect personal accounts for user-specific systems.

See **Agent Sharing in Workspace** for more detail on shared-agent connection behavior.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://alludium.gitbook.io/alludium-docs/administration/6.-applications/7.-connections.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.