Databases

A database is a set of documents you assemble once and reuse everywhere. Unlike Project files, which belong to a single matter, a database sits at the workspace level: it isn’t tied to a project, and any project can draw on it. That makes databases the right home for the sources you reach for again and again — your firm’s precedent bank, a client’s full contract set, a body of regulation you check against — rather than for the working documents of one matter.

​

Before you start

Databases are part of the Team plan, and your firm administrator has to switch them on. If your plan includes them but they haven’t been enabled yet, ask your administrator. If your team is below the Team plan, Databases appears with an upgrade prompt in place of the list. See Subscription. When databases are available to you, Databases appears in the global part of the sidebar, next to Home and Templates — above the project switcher, because it doesn’t belong to any one project.

​

The two kinds

Both behave the same once built. The difference is only where the files are stored and who keeps them up to date.

​

What’s inside one

Opening a database shows its documents in a browser you can sort by name, author, or date added. Each row carries the document’s author, when it was added, and your access to it. Folders behave as first-class items: you can select, move, and delete a whole folder and everything under it. You can fill a database by uploading files or entire folders, or by pulling in documents that are already in a project’s Project files — those are linked, not re-uploaded, so there’s only ever one copy.

​

Using a database

A database is a source you can point Libra at from anywhere: Because the database is shared, the answer a colleague gets in another matter is drawn from exactly the same sources as yours.

​

Sharing and access

The person who creates a database owns it and controls sharing. When a database is shared with you, your role on it — Viewer, Editor, or Admin — is shown in the browser and decides whether you can add or remove documents.

​

Your page allowance

Uploading into a Libra database draws on a page allowance that scales with your subscription: each billed seat grants 100,000 page-equivalents, pooled across the team. Two things to know about it:

• It’s a total, not a monthly reset. The allowance covers everything your team has ever ingested into Libra databases.
• Deleting documents doesn’t give pages back. If you’re close to the limit, add seats or buy more pages rather than clearing space.

Documents in a SharePoint database don’t count toward it, because Libra doesn’t ingest them. If an upload would take you past the allowance, Libra refuses it and tells you how many pages are left.

​

Next steps