> ## Documentation Index
> Fetch the complete documentation index at: https://docs.libratech.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# SharePoint databases

> Link a SharePoint folder as a database: the files stay in SharePoint, Libra reads them live and read-only, and each colleague needs their own access to the folder.

<video autoPlay muted loop playsInline src="https://mintcdn.com/libra-4206ec93/AGKaF7jfNwgcblyi/assets/videos/features/databases-sharepoint.webm?fit=max&auto=format&n=AGKaF7jfNwgcblyi&q=85&s=994b281911a804ab26ed8bf4a1583ed0" className="rounded-xl border w-full" data-path="assets/videos/features/databases-sharepoint.webm" />

A **SharePoint database** connects an existing SharePoint folder instead of uploading its files. Libra always shows the current version of what is in the folder, so there is nothing to upload and nothing to keep in sync. In exchange it is a read-only view: you can look at, download and search the files, but uploads, changes and deletions still happen in SharePoint.

## Link a SharePoint folder

Linking a folder is a one-time job, but it depends on a Microsoft 365 setup being in place first.

<Steps>
  <Step title="Check the one-time setup">
    Open **Settings → Integrations → SharePoint**. **Setup required** means a Microsoft 365 organization administrator still has to grant Libra access, after which a Libra team administrator clicks **Enable for my Team**. Then connect your own Microsoft account from the same panel. The full sequence is on the [SharePoint integration](/en/integrations/sharepoint) page.

    <img src="https://mintcdn.com/libra-4206ec93/_JcRjdqeywA_CQSI/assets/images/app/databases-sp-setup-required.png?fit=max&auto=format&n=_JcRjdqeywA_CQSI&q=85&s=edd475a3f3b61ed1da82ccb5b7795ee3" alt="The SharePoint integration panel showing Setup required, with Open consent page, Copy link and Enable for my Team" width="3800" height="2160" data-path="assets/images/app/databases-sp-setup-required.png" />
  </Step>

  <Step title="Databases → New database → Add Sharepoint folder">
    The **New SharePoint database** dialog opens.

    <img src="https://mintcdn.com/libra-4206ec93/uIM4p-wnrkQLmhsv/assets/images/app/databases-new-menu.png?fit=max&auto=format&n=uIM4p-wnrkQLmhsv&q=85&s=2bd1ef6867b02a0b496272e339389bfb" alt="The New database menu with Add Sharepoint folder under Document integrations" width="3800" height="2160" data-path="assets/images/app/databases-new-menu.png" />
  </Step>

  <Step title="Pick the folder, name it and Create">
    **Select from SharePoint** opens Microsoft's folder picker. Only folders can be chosen; everything inside, subfolders included, becomes part of the database, and the folder's name is proposed as the database name. Adjust the **Database name**, add a **Description**, then click **Create**. The footer previews whether this database will search by meaning or by keyword.
  </Step>
</Steps>

You need the **Team** plan with Databases switched on, and you must be able to open the folder in SharePoint yourself.

## Give colleagues access

Two permission systems apply at once, and both have to say yes: Libra decides who sees the database, SharePoint decides who can open the files.

<Steps>
  <Step title="Share the database in Libra">
    **⋯ → Share**, as for any database. This decides who sees the database in their list. The dialog reminds you: *Users will need access to the folder in SharePoint in order to access it.*

    <img src="https://mintcdn.com/libra-4206ec93/_JcRjdqeywA_CQSI/assets/images/app/databases-share-dialog.png?fit=max&auto=format&n=_JcRjdqeywA_CQSI&q=85&s=16625d0f9d08adc0b922238706447970" alt="The Share dialog for a database, with Share with, General access and Who has access" width="3800" height="2160" data-path="assets/images/app/databases-share-dialog.png" />
  </Step>

  <Step title="Give them access in SharePoint, and have them connect">
    Every colleague browses the folder with their own Microsoft account, so they see only what SharePoint lets them see. Two things can stop them: without access to the folder they see the database but only *No access to this folder* inside it; and without a connected Microsoft account they see the card dimmed with *You are not connected to SharePoint.* and a **Connect your SharePoint account** link, with **Add to chat** hidden until they connect.
  </Step>
</Steps>

<div className="libra-buddy-callout">
  <img src="https://mintcdn.com/libra-4206ec93/wgVZXcGnHS4aJk9T/assets/images/libra-buddy/clipboard.png?fit=max&auto=format&n=wgVZXcGnHS4aJk9T&q=85&s=cde036cf23ea2d67cd50f1c295db549a" alt="Libra mascot with clipboard" width="725" height="605" data-path="assets/images/libra-buddy/clipboard.png" />

  <div className="libra-buddy-callout-content">
    Share the folder in SharePoint at the same time as you share the database in Libra. A colleague who can see the database but not its files will otherwise think Libra is not working.
  </div>
</div>

## Search it from a chat

A SharePoint database is attached differently from a Libra one, and Microsoft does the searching rather than Libra.

<Steps>
  <Step title="Attach it">
    An `@`-mention of its name, or **Add to chat** from its card or from inside the database (see [Usage](/en/features/databases/usage#add-a-database-to-a-chat)). SharePoint databases don't appear in **Tools → Select files**. On that picker's **SharePoint** tab under **Integrations**, **Attach entire SharePoint** searches your whole connected SharePoint rather than one folder, and single files you pick there are downloaded into the chat so Libra reads them in full.

    <img src="https://mintcdn.com/libra-4206ec93/_JcRjdqeywA_CQSI/assets/images/app/databases-mention-picker.png?fit=max&auto=format&n=_JcRjdqeywA_CQSI&q=85&s=b36ae821d31583c35f7ca7d9756edc76" alt="The at-mention picker in the chat input listing databases under Documents" width="3800" height="2160" data-path="assets/images/app/databases-mention-picker.png" />
  </Step>

  <Step title="Ask">
    Libra searches the folder through Microsoft: by meaning if you hold a **Microsoft 365 Copilot** licence, by keyword otherwise, checked at the moment you ask. Without Copilot, use the words the documents use.
  </Step>

  <Step title="Open the citations">
    A cited passage opens in a read-only preview, or in SharePoint itself if the preview can't be shown.

    <img src="https://mintcdn.com/libra-4206ec93/uIM4p-wnrkQLmhsv/assets/images/app/databases-citation-open.png?fit=max&auto=format&n=uIM4p-wnrkQLmhsv&q=85&s=995f51535e04f87b56b407c91df8e08c" alt="A citation opened from an answer, with the document in the side panel and the cited passage highlighted" width="3800" height="2160" data-path="assets/images/app/databases-citation-open.png" />
  </Step>
</Steps>

## Browse the folder

The browser is read-only, so it is for finding and reading files rather than changing them.

The browser lists the files with the date each was last **Modified** in SharePoint. Each file row offers **Download**, **Open in SharePoint**, **Copy link** and **Add to chat**; PDFs, Office documents and most text formats also offer **Preview** on hover, while other files such as images open in SharePoint. Folder rows offer only **Open in SharePoint** and **Copy link**. There is no search box, and nothing can be changed from Libra; the database itself can still be renamed, shared, favourited and deleted.

## Limits and troubleshooting

<AccordionGroup>
  <Accordion title="It costs no page allowance">
    A SharePoint database consumes none of the team's [page allowance](/en/features/databases/usage#roles-and-limits), however large the folder. Files picked *from* SharePoint while filling a Libra database are copied into Libra and do count.
  </Accordion>

  <Accordion title="File counts can lag">
    The **Files** count on the card is worked out per person and refreshed about once a day, so it can trail SharePoint and differ between colleagues who see different parts of the folder.
  </Accordion>

  <Accordion title="The folder was moved or deleted">
    The database reports *This folder is no longer available*. The link can't be repointed: someone with **Full access** deletes the database and links the folder from its new location, then shares it again.
  </Accordion>

  <Accordion title="Nobody new can connect to SharePoint">
    A team administrator may have used **Disable for Team** under the SharePoint integration. That blocks new SharePoint connections for the team, and Settings then shows *Your team admin must enable SharePoint before you can connect*. Re-enabling restores them, and nothing about the databases is deleted.
  </Accordion>
</AccordionGroup>

## Next steps

<Columns cols={2}>
  <Card title="SharePoint integration" icon="folder-symlink" href="/en/integrations/sharepoint">
    Admin consent, enabling for the team, connecting your account.
  </Card>

  <Card title="Usage" icon="message-square" href="/en/features/databases/usage">
    Attaching a database in chat, Review and Discovery.
  </Card>
</Columns>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.