Teams may choose to manage matters across multiple Everlaw organizations when they have sub-teams with different admins or distinct agencies, or when a single organization does not provide a sufficient information access barrier.
As a result, Everlaw offers parent organization reporting — centralized, aggregate reporting for admins managing these organizations.
Parent organization reporting is accomplished by designating an individual organization as a parent organization and one or more existing organizations as sub-organizations nested under that individual parent. A centralized parent organization landing page then provides access to all designated sub-organizations and a consolidated report of their data usage.
Note
If you need to create additional Everlaw organizations, to use as either a parent organization or as sub-organizations, please contact your Customer Success representative or support@everlaw.com.
Your organization must have an annual subscription to enable parent organization reporting.
Parent organization reporting is configured in two steps:
- First, turn on the parent organization reporting tool in the designated parent organization.
- Then select which of your organizations you would like to designate as sub-organizations. Reporting on these sub-organizations will be aggregated in the Sub-organizations tab.
If you're considering creating multiple organizations, we recommend reading this article's section titled considerations around managing multiple Everlaw organizations.
Enable parent organization reporting
Required permissions: Organization Administrator for the organization being designated as the parent organization.
To enable parent organization reporting, and before designating sub-organizations, you must first switch the feature on for one of your existing organizations. Doing this, makes the organization a parent organization.
An ideal organization to configure parent org reporting in is one that is your central or "default" organization — one that does not have matters belonging to a distinct sub-team. All Organization Admins of the parent organization can see the reports containing information on linked sub-organizations.
If you do not have an existing organization set up for this purpose, you may request to set up a new organization by contacting your Customer Success representative or support@everlaw.com
To make an organization the parent organization:
- Go to the Organization home
page. You should be on the Projects & Users tab.
- Select the Security Settings tab.
- In the Parent Organization section, switch on Add parent organization reporting to this organization.
Once parent organization reporting has been configured from the desired organization, this organization is the parent organization and a Sub-organization tab is added to the Organization Admin page.
The Sub-organizations tab is the only tab that contains information pertaining to all sub-organizations. All other tabs in the left menu only contain information on the databases and projects within the parent organization and do not contain information from the sub-organizations (e.g. the Users table in the Projects & Users tab of the parent organization displays only members of the parent organization and does not include members of the sub-organizations).
After configuring parent organization reporting, a dialog informs all organization admins accessing the “Sub-organizations” tab for the first time about the new tab.
Permissions of the parent organization
The permissions of Organization Admins of the parent organization are configured and displayed in the Users table in the Projects & Users tab of the parent organization. Any Organization Admin can access the Sub-organizations tab, add sub-organizations that they are also organization admins for, and view all linked sub-organizations in the tables.
Important
An organization admin of the parent organization who is not an organization admin of a particular sub-organization can still see information about the sub-organization in the tables, including the names of its databases and projects, but they cannot navigate to or access the sub-organization.
Permissions on the parent organization are separate from the permissions on sub-organizations. Please see the section below for information about the Organization admin page of sub-organizations.
- Organization admins of the parent organization are not granted new permissions to a sub-organization when it is linked to the parent organization.
- Organization Admins of the parent organization may administer databases and projects in the parent organization the same way they can in any other organization. Parent organization reporting does not change any permissions of the parent Organization Admins on the other tabs on the Organization Admin page.
Share single sign-on (SSO) settings
Sub-organizations can use the same single sign-on (SSO) SAML metadata and settings as the parent organization, as long as both the sub-organization and parent organization have switched on complementary settings in their respective organizations.
To share SSO information, an Organization Admin for the parent organization needs to switch on a setting in the Projects and Users > Security Settings tab.
Then, an Organization Admin for the sub-organization needs to switch on a complementary setting in the Projects and Users > Security Settings tab of the sub-organization. This toggle is only enabled when the toggle on the parent organization is switched on.
Once both a parent and sub-organization have switched on the setting, then members of the sub-organization will log into Everlaw using the same SSO setup as members of the parent organization.
Learn more in Propagate Parent Organization Single Sign-On (SSO) Settings to Sub-Organizations.
Summary of Organization Admin permissions
| Org Admin permissions | Access Parent Organization Reporting (Sub-orgs tab) | Administer Parent Organization | Administer Sub-Organization |
|
✅ Yes | ✅ Yes | ✅ Yes |
|
✅ Yes | ✅ Yes | ❌ No |
|
❌ No | ❌ No | ✅ Yes |
Designate organizations as sub-organizations
Before you start: This action requires an organization with parent organization reporting enabled and one or more additional organizations (to be designated as sub-organizations). If you need to create additional organizations, to use as either a parent organization or as sub-organizations, please contact your Customer Success Representative or support@everlaw.com.
Required permissions: You must be an Organization Admin on both the parent organization and any organizations you are designating as a sub-organization.
You can designate existing organizations as sub-organizations via the Sub-organizations tab of a parent organization. To do this:
- Go to Organization home
> Sub-organizations.
- Select +Add sub-organization to select existing organizations that you currently administer to become sub-organizations.
This opens the Add sub-organization dialog.
You can only add sub-organizations that have not already been added to your parent organization or any other parent organization. Remember that all other Admins of the parent organization will be able to see information for the sub-organizations you add, even if they do not have permissions on the sub-organizations. - Select the organization(s) to make into sub-organizations.
Their names appear in the Selected organizations list. - Select Continue.
- Confirm that the information on the next page of the dialog is correct and select Confirm.
Sub-organizations table
Once added, all sub-organizations are displayed in the table alongside information on the number of databases, projects, and users within each sub-organization. The counts in the table include:
- databases that do not yet have billable data
- databases with OA Access disabled
They do not include databases or projects that have been deleted. Select the Organization Admin button in the table to navigate to the Organization Admin page of the sub-organization (if you are an Organization Admin of the sub-organization).
If you do not have access to a sub-organization, the Organization Admin button is disabled.
Export sub-organization user data
Parent-level Organization Admins can download a single CSV report of all users across a parent organization and its sub-organizations. This is helpful for accelerating and standardizing access reviews and compliance reporting for large account hierarchies.
This setting is enabled by default for all sub-organizations but can be disabled by a sub-organization Organization Admin if they do not want to share this information with their parent organization. User data from projects where OA access has been disabled will be omitted from this report.
The report includes the following columns:
- First Name
- Last Name
- User Identification Labels (formatted as a comma separated list)
- User type
- Primary org
- Date added to org (e.g. Nov 05, 2024 9:28 am PST)
- Date account created
- Date last project login
- Org admin permission
- Organization Name
- Number of Active Projects
- Number of Suspended Projects
To export this report, go to Organization home > Sub-organizations, and select Export all user data. This downloads the report to your computer.
Exports only include user data from sub-organizations that have user information export access granted to parent Organization Admins. To see which sub-organizations support this access, view the sub-organization table’s User data access column.
Data usage table
In the Data usage table within the Sub-organizations tab, you can view usage data for all sub-organizations with billable data. You can filter and export data from this table.
The default view of this report is aggregated by sub-organization. If the parent organization itself has billable data, it is displayed as a row in this table and is included in the totals across the top of the page.
To display all databases and projects of the sub-organizations and the parent organization, select the View by fields Database / Project option.
To export organization sizes, database sizes, or project sizes, select the table's Export button. Then select your option from the menu.
Organization admin page of sub-organizations
When added to a parent organization, a sub-organization does not change and functions exactly the same as any other organization. The sub-organization does not inherit any properties from the parent organization.
The only difference between a sub-organization and any other (non-parent) organization is that you cannot enable parent organization reporting in a sub-organization.
Organization Admins of the sub-organization can also view the history of which user added the organization to a parent organization in the User Access History tab.
Considerations around managing multiple Everlaw organizations
Teams may choose to manage matters across multiple Everlaw organizations when a single organization does not provide a sufficient information access barrier. Subteams with distinct admins, distinct agencies that operate independently, or teams that have a subset of matters that are highly confidential may benefit from managing matters in separate Everlaw organizations and utilizing parent organization reporting to report across all matters.
However, for teams that can use the OA Access feature to sufficiently control administrator access to matters in a single organization and create Database Fields to label and categorize matters, a single organization offers the most robust reporting across all matters. A single organization also gives organization admins a single page to configure settings, like API.
A user cannot be a member of multiple organizations that both require SSO and log in with SSO to each one if the organizations use different SAML metadata. However, a user who is a member of both a parent and sub-organization that share SSO settings can be required to login using SSO to both. See the above section Share single sign-on (SSO) settings or the article Propagate Parent Organization Single Sign-On (SSO) Settings to Sub-Organizations to learn more.
Additionally, a given email domain cannot be associated with multiple organizations. Please refer to our support articles for more information on single sign-on and organization security.