> For the complete documentation index, see [llms.txt](https://docs.cogram.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cogram.com/agent/agent-connectors.md).

# Connectors

Understand which identity and permissions Agent uses for connected systems.

Connectors let Agent search or act in another system. Cogram permissions still apply, along with the connected system's permissions.

Open [Connectors](https://app.cogram.com/dashboard/agent/connectors) for Agent-native connections such as Slack, Custom API, file server connector, and Autodesk Construction Cloud. An Agent's **Connectors** tab also lists connections managed elsewhere in Cogram.

## Identity and access

| Connection                      | Identity and permission boundary                                                                             |
| ------------------------------- | ------------------------------------------------------------------------------------------------------------ |
| **Autodesk Construction Cloud** | Your Autodesk account; read-only and limited to its projects. Admin approval applies to each Autodesk hub.   |
| **Calendar**                    | Your connected Google or Microsoft calendar account. Each user connects separately.                          |
| **Outlook email, SharePoint**   | Your connected Microsoft account. Each user connects separately.                                             |
| **File server connector**       | Organization connector with your mapped Windows identity and file permissions.                               |
| **Unanet ERP A/E**              | Organization setup with each user's Unanet login and permissions.                                            |
| **Procore**                     | One Procore user's OAuth connection is stored per Cogram project. Agent users share that project connection. |
| **Deltek Vantagepoint**         | Organization service account; Cogram limits supported data and project access.                               |
| **Microsoft Teams**             | Organization setup; Agent answers with the requesting user's Cogram access.                                  |
| **Slack**                       | Organization bot; sees only internal channels it was invited to. Automations can post at Read and write.     |
| **Custom API**                  | Any Agent user can invoke the organization credential within its upstream permissions.                       |

Two users can receive different results from the same Agent because their accounts or project access differ. Shared Agent instructions never grant shared source access.

## Set up a connector

Organization admins and owners manage organization connections. Personal connections require each user to sign in. Project connections are configured for each project.

Setup guides:

* [Autodesk Construction Cloud](/integrations/connecting-autodesk-construction-cloud.md)
* [File server connector](/integrations/connecting-your-file-server.md)
* [Deltek Vantagepoint](/integrations/connecting-vantagepoint.md)
* [Unanet ERP A/E](/integrations/connecting-unanet.md)
* [Procore](/integrations/connecting-procore.md)
* [Microsoft Teams](/agent/microsoft-teams.md)

For **Custom API**, an admin provides the base URL, API description, and authentication in [Connectors](https://app.cogram.com/dashboard/agent/connectors). Cogram stores the secret outside the model and restricts calls to the configured host. Write methods require explicit confirmation in chat.

Never place credentials in a description, skill, document, or chat message. Use only the connector's secret fields.

Before connecting a service account, check that its upstream access is appropriate for everyone who may use the connector. Its access may be broader than each user's own account.

## Troubleshooting

**I cannot configure a connector**

You may need organization admin, personal account, or project-management access. Open the connector to see where its setup is managed.

**Agent cannot find a record**

Confirm that the connection is active, your identity can open the source, and the correct Cogram project is selected. Some connectors also require a project or folder mapping.

**Agent asks me to provide a file**

The file may be unavailable, unsupported, or outside the mapped location. Attach it to the chat or add it to the correct project or [Library](/agent/agent-library.md).

## Next steps

* [Agent](/agent/agent.md)
* [Specialist Agents](/agent/agents.md)
* [Library](/agent/agent-library.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cogram.com/agent/agent-connectors.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.