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

# Third-Party Connectors

Lab Atlas allows you to connect a variety of third-party tools, such as cloud storage providers, electronic laboratory notebooks, and source code management systems. These integrations allow you and your team to pull files & data in from these systems, as well as propagating records & automating actions in the external services.

Everything below is managed from the **Integrations** page in the sidebar, which every member of your organization can open.

<figure><img src="/files/STX2ws1pd2JkvdZpHooi" alt=""><figcaption><p>The integrations page</p></figcaption></figure>

## Organization and personal integrations

Integrations come in two kinds, and the difference matters for who can set them up and who can use them.

An **organization integration** is connected once by an admin and shared by everyone in the organization. It uses a single set of credentials belonging to the organization, and the resources it exposes — an S3 bucket, a SharePoint site, a Benchling tenant — are available to members according to the normal project and folder permissions. Only Organization Admins can connect or modify one.

A **personal integration** is connected by you, for you, using OAuth. You sign in to the provider yourself, Lab Atlas never sees your password, and the connection acts strictly as you. Nobody else in your organization can see or use it, and a storage folder reached through a personal integration is never shown to other members. Any member can connect one, with no admin involvement.

## Organization integrations

* [Benchling](/integrations/benchling.md)
  * Automate creation of notebook folders & entries
* [Microsoft 365](/integrations/microsoft-azure.md)
  * Read and write files from SharePoint
  * Automate creation of storage folders for projects, studies, and assays
* [Amazon Web Services](/integrations/amazon-web-services.md)
  * Read and write files from S3
  * Automate creation of storage folders for projects, studies, and assays
* [GitLab](/integrations/gitlab.md)
  * Automate the creation of source code groups and projects
* [CDD Vault](/integrations/cdd-vault.md)
  * Automate creation of notebook entries

## Personal integrations

* [Egnyte](/integrations/egnyte.md)
  * Connect your own Egnyte account for project and shared storage

To connect one, open the **Integrations** page and choose the provider from the personal section. You will be sent to the provider to sign in and approve access, then returned to Lab Atlas. You can disconnect it again at any time from the same page, which revokes Lab Atlas's access immediately.

{% hint style="info" %}
Because a personal integration acts as you, the folders it exposes follow your own permissions in the connected service — not your Lab Atlas organization's. Storage reached this way stays private to you.
{% endhint %}