Participant management in Legatics ensures that the right people have the appropriate level of access to your matters. By effectively managing users, roles, and permissions, you can streamline collaboration and maintain control over sensitive information. This guide provides an overview of participant management and its key features.
Prerequisites: To manage participants, you need to be a Matter Admin
Understanding the participant structure
Organizations group related users within a matter. Roles group related organizations. Permissions can be granted to roles, organizations or users, with the matter administrator permission granted to all users in an organizations.
Element | Explanation | Examples |
Roles | Group related organizations together | Lawyers, Borrowers, Buyer team, Seller team |
Organizations | Group related users together | Goldman Sachs, Citibank, A&O, Linklaters, EY, PwC |
Users | People who have been invited to the matter | John Doe |
Matter Admin | This permission gives all users in the organization granted it full access to view and edit everything within a matter | N/A |
Permissions | Determine what actions participants can perform, such as viewing lists, rows, files, or comment | View list |
Key elements of participant management
This article explains how to set up and manage roles and organizations within a matter. You'll learn how best to use roles and organizations to maintain control and security in your matters.
You'll understand the responsibilities of a Matter Admin, how to assign this permission to ensure proper oversight, and how to revoke these rights when they are no longer needed.
Understand how to manage individual users in your matter. It walks you through adding new users, inviting them, and removing those who no longer require access, ensuring your matter stays organized and secure.
Interaction of permissions with the participant structure
Permissions in Legatics work in tandem with the participant structure, ensuring that roles, organizations, and users have tailored access to data within a matter. Here's how permissions interact with each layer of the participant hierarchy.
Tip: Permissions dynamically update depending on your selections. For example, if you uncheck a role, then global will become unchecked.
Global
If you grant global permissions, all participants in the matter will have the same level of access.
Roles
Permissions can be assigned to a role, granting all organizations and users within those organizations the same level of access.
Example: The "Borrower" role is restricted from viewing a list. Every organization and user inside assigned to that role won't be able to view that list (including any new organizations added to that role).
Organizations
Permissions can also be applied to an entire organization. This allows you to manage access efficiently for all users within a specific organization.
Example: The "Goldmans Sachs" organization is the only organization in the role who can view a list. Adding another organization to the role won't give them permission to view the list.
Users
User-specific permissions override those assigned at the role or organization level. This provides flexibility to grant unique access to certain participants while maintaining broader permissions for roles or organizations.
Example: Sally from the "Goldmans Sachs" organization is the only user in the organization who can view a list. Other users in the Goldman Sachs organization won't be able to see the list.