In Libra, your organization is your team’s shared workspace. Team members can share assistants and chat conversations, access shared document libraries, collaborate on projects, and use shared workflow templates.
Team features are available on Enterprise plans.
Team Member Permissions
Team members added to a shared project can:| Action | Team Members Can |
|---|---|
| View Documents | See all documents in the project library |
| Add Documents | Upload new documents to the project |
| View Discoveries | Access all discovery results in the project |
| Create Chats | Start conversations using project context |
| Use Assistants | Access shared assistants within the project |
Changing User Roles
Admins can change the role of any team member between Admin and Member. This is useful when you need to promote a team member to admin or reduce someone’s permissions.Available Roles
| Role | Permissions |
|---|---|
| Admin | Full access to team settings, can manage users, assign licenses, and configure organization settings |
| Member | Create and manage personal content only, no access to team settings |
How to Change a User’s Role
Open the Team Members page
Click your profile picture in the bottom left corner.
Open the user menu
Find the team member whose role you want to change. Click the three-dot menu (…) on the right side of their row.
Select the new role
In the Change Role dialog, you’ll see the user’s current role. Use the New Role dropdown to select the new role (Admin or Member). The dialog shows the permissions for the selected role.
Assigning Packages to Team Members
If your organization has purchased Otto Schmidt research modules, admins can assign these packages to specific team members. This allows you to control which users have access to each legal research module.Select team members
From the Team Members tab, check the boxes next to the team members you want to assign packages to. A toolbar appears at the bottom showing the number of members selected.
Select packages
In the Assign packages dialog, check the boxes next to the packages you want to assign to the selected members. The dialog shows how many licenses are available for each package.
You can only assign packages if you have available licenses. Purchase additional licenses from the Subscription tab if needed.
Best Practices
Use descriptive project names
Use descriptive project names
When sharing projects with team members, use clear names that indicate the project’s purpose. For example: “Acme Corp - Due Diligence 2026” or “Employment Law Research Q1.”
Add team members at creation
Add team members at creation
Add team members when you create the project rather than later. This ensures everyone has access from the start and can contribute to building the project’s knowledge base.
Review team access regularly
Review team access regularly
Periodically review who has access to your shared projects. Remove team members who no longer need access to maintain proper information security.
Use shared projects for matters
Use shared projects for matters