Skip to main content
Almost everything in Libra can be shared: projects, chats, Review templates, Discovery templates, Assistants, Workflows. The model is the same in every case: a General access setting for the whole resource, plus an explicit list of people and groups, each with a permission level.
Libra mascot presenting
When a user has both a direct and group share, the highest wins. View won’t downgrade group-granted Edit. To restrict, remove from the group.

​
What you can share

ResourceWhere to find ShareNotes
ProjectHome → project menu → Share, or inside the project.Sharing a project gives access to everything inside it (chats, documents, Reviews, Discoveries).
ChatInside the chat → Share button.Recipients must already have access to the parent project.
Review templateTemplates → template editor → Share.Project-independent. Travels with the user across every project.
Discovery templateTemplates → template editor → Share.Project-independent.
AssistantTemplates → Assistant editor → Share.Project-independent.
WorkflowTemplates → Workflow editor → Share.Project-independent. Recipients also need access to any Assistants the Workflow uses.
DocumentDocuments panel → file menu → Share.Recipients must already have access to the parent project.

​
Who can share what

A simple rule: the owner of a resource can share it. The owner can grant Edit or Admin rights to others, who can then share further.
Your team role (Admin, Member) doesn’t determine sharing rights. Sharing is controlled by the permissions on each individual resource.

​
Three ways to grant access

Pick specific colleagues by name or email. Useful for one-off collaboration.
Share with a named group (“Corporate Law”, “Berlin Office”, “Associates”). Every member of the group gets access. New members of the group get access automatically. See Team management for creating groups.
Set General access to Everyone in the team. Anyone in your firm can find and use the resource without you adding them individually. Useful for templates the firm has standardised on.
You can combine all three. A Review template can be set to Everyone in the team with a specific Edit permission for the practice group that maintains it.

​
Permission levels

PermissionAllows
ViewUse the resource: open the chat, run the template, view the document. No edits.
EditEverything in View, plus modify the resource and share it further.
AdminFull control: edit, share, and delete.
When a user has access through multiple shares (e.g. directly and via a group), the highest permission level applies.

​
Sharing, step by step

1

Click Share on the resource

The Share button is on every shareable resource, in toolbars, on cards, and in editors.Share dialog with General access, Share with, and Who has access sections
2

Set General access (optional)

The General access dropdown sets the default for the whole firm:
  • Only people invited: only people you explicitly add can access.
  • Everyone in the team: anyone in the firm can access without being added.
3

Add specific people or groups

Type a name, email, or group in the Share with field. Matching results appear as you type.
4

Set the permission level

Pick View, Edit, or Admin from the dropdown next to the search field before clicking Add.Permission dropdown showing View, Edit, and Admin options
5

Click Add

The person or group lands in Who has access with the chosen permission.
6

Review and adjust

The Who has access section lists everyone who can see the resource. Click someone’s permission to change it; click the delete icon to remove them.Who has access list with a user group expanded

​
Special rules

A few resource types have extra rules to be aware of.
A chat is project-scoped. Sharing a chat with someone who doesn’t have access to the parent project does nothing. Share the project first, then the chat.
A Workflow that uses three Assistants requires the recipient to have access to all three (unless the Assistants are public). Libra warns you when this isn’t the case.
Templates aren’t project-scoped. Once you share a Review template with a colleague, it appears in their Templates library across every project they work in.
A document in a shared project is visible to everyone who has access to the project. You can also share an individual document with people inside the project for tighter control, but you can’t share a document with someone who isn’t in the project.

​
Removing access

1

Open the Share dialog

Click Share on the resource.
2

Find the person or group

The Who has access section.Who has access list with people and groups
3

Click the delete icon

Access is revoked immediately.
Removing access to a project also removes access to every chat and document inside it.
Libra mascot looking worried
Edit quietly carries the right to re-share. To let a colleague use a template but not redistribute, grant View. Only Admin and Edit unlock Share.

​
Tips for sane sharing

Group-based sharing scales as your team grows. Individual sharing means manual maintenance every time someone joins or leaves.
Standard NDA templates, standard policies, the firm’s house-style Assistant: these are good candidates for Everyone in the team. Reserve invitation-only for sensitive matters.
Admin lets someone delete the resource. Grant it to people you’d genuinely want to be co-owners, such as your fellow practice-group lead or the partner you co-counsel with, not casually.
Once a quarter, open Home, scan your shared projects, and review Who has access. Remove people who’ve left the firm, the team, or the matter.
All sharing is scoped to your firm/team. To collaborate with outside counsel, the cleanest path is to export the relevant work as a PDF or Word document.

​
Next steps

Team management

Create user groups and manage roles.

Projects

The most common thing you’ll share.