Everlaw automatically places users into organization groups based on the domain of a user’s email. These organization groups are mainly meant to help facilitate sharing within an organization, but can also be used to manage organization-specific permissions.
When sharing items in Everlaw, you can select recipients by organization. This is particularly useful if you want to dynamically share an item, meaning that the item will be automatically shared with all current and future users in the organization. For example, if you share a binder with an organization, not only will current users in the organization receive the binder, but all future users added to the case under that organization will automatically receive the binder. This is true for Outlines, Assignment Groups, and the Chronology. Dynamic sharing does not work for searches, individual documents, and messages (they will only be shared with current users in the organization).
Organizations also behave exactly like a user group, which means that they can be used to manage permissions by organization. However, they are not meant to replace user groups when deciding case permissions. As a consequence, unlike default user groups, organizations are not given any default permission settings at the outset of a case. Instead, case admins must explicitly choose which permissions they want users within an organization to have.
When inviting users to a case, they must be associated with a user group, and they will be added automatically to an organization group. When users belong to multiple groups, if those groups have different permission levels for the same field, the user is given the higher permission level. In the example below, the case admin gave all users in Demo Firm case admin privileges. This means that a user from the organization who is in the “reviewer” or “viewer” user group now has the ability to administer the case, even though their user group doesn’t have that permission level.
Because editing organization-level permission settings will affect users across different user groups, we recommend caution when managing organization permissions.