Organization Admin: Parent Organization Reporting

This article covers parent organization reporting, which is intended for teams managing multiple Everlaw organizations. Parent organization reporting offers centralized, aggregate reporting for Organization Admins of clients currently managing multiple Everlaw organizations.

If your organization wishes to create new Everlaw organizations on the platform to use parent organization reporting, please contact your Customer Success representative or support@everlaw.com. Your organization must have an annual subscription to enable parent organization reporting.

• Configuring parent organization reporting
  • Permissions of the parent organization
• Adding sub-organizations
• Sub-organizations table
• Data usage table
• Organization Admin page of sub-organizations
• Considerations around managing multiple Everlaw organizations 

Introduction

Organization admins who administer multiple Everlaw organizations can configure parent organization reporting to set up a centralized landing page to access Everlaw organizations designated as sub-organizations and to view a report of data usage for all sub-organizations.

Teams may choose to manage matters across multiple Everlaw organizations when they have subteams with different admins or distinct agencies or when a single organization does not provide a sufficient information access barrier. Please see the below section for considerations around managing multiple Everlaw organizations.

Parent organization reporting is configured in two steps. First, you turn on the parent organization reporting tool in the designated parent organization. Then you select organizations to designate as sub-organizations whose reporting will be aggregated in the Sub-organizations tab.

Configure parent organization reporting

Required permissions: Organization Administrator for the organization being designated as the parent organization.

All Organization Admins of the parent organization can see the reports containing information on linked sub-organizations. 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 subteam.

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:

1. Select the O diamond to go to the Organization Admin page. You should be on the Projects & Users tab.
2. Select the Security Settings tab.
3. Toggle on the Parent Organization toggle. 

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. 

Permissions on the parent organization are separate from the permissions on sub-organizations. Please see the section below for more information on 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.

Add sub-organizations

Required permissions: You must be an Organization Administrator on both the parent organization and any organizations you are adding as a sub-organization.

You designate sub-organizations  from the Sub-organizations tab of the Parent organization. To do so:

1. Navigate to the Sub-organizations tab of the Organization Admin page.
2. Select +Add sub-organization to select existing organizations that you currently administer to become sub-organizations. 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.  
3. Select the organization(s) to make into sub-organizations. Their names appear in the selected organizations table.
4. Select Continue.
5. Confirm that the information on the next page of the dialog is correct and select Confirm. If it's not correct, select cancel.

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. Click on the Organization Admin diamond icon 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 icon is disabled.

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. From this table, you can export organization sizes, database sizes, or project sizes by clicking on the export button above the 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. 

Change the view to by Database / Project to display all databases and projects of the sub-organizations and the parent organization. 

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 single sign-on (SSO) and API.  Managing matters in a single organization may also be best suited for teams wishing to require SSO for all organization members because:

1. Multiple organizations cannot use the same SAML metadata for their SSO configuration.
2. Users cannot be members of multiple organizations that both require SSO and log in with SSO to each one.

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.