This article covers parent organization reporting, which is intended for teams managing multiple Everlaw organizations. If your organization wishes to create new Everlaw organizations on the platform to utilize parent organization reporting, please contact your Customer Success representative.
- 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
Parent organization reporting offers centralized, aggregate reporting across multiple Everlaw organizations. Higher-level admins who administer multiple Everlaw organizations can configure parent organization reporting to set up a centralized landing page to access 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.
Configuring parent organization reporting
If you already manage multiple organizations on Everlaw, you may enable parent organization reporting in the Security Settings tab under Projects & Users from an existing Everlaw organization, or you may request to set up a new organization for this purpose by contacting your Customer Success representative or Everlaw Support.
You should keep in mind the permissions of the parent organization when considering which organization to configure parent organization reporting in. All organization admins of the parent organization can see the reports containing information on linked sub-organizations. An existing organization that is already your default organization or one that has matters that may not necessarily belong to a distinct subteam or agency may be an ideal parent 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 owned directly by 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 user with “Admin” permissions can access the Sub-organizations tab, add sub-organizations that they also organization admins for, and view all linked sub-organizations in the tables.
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. Organization admins of the parent organization are not granted new permissions to a sub-organization when it is linked to the parent organization.
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.
Configuring parent organization reporting also does not change any permissions of the parent organization admins on the other tabs on the organization admin page, which contain information on the databases and projects owned directly by the parent organization. Organization admins of the parent organization may administer these databases and projects in the same way they can in any other organization.
Adding sub-organizations
To add a sub-organization, you must be an organization administrator on the sub-organization. Click the “Add sub-organizations” button above the table 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.
Sub-organizations table
Once added, all sub-organizations will be 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, as well as databases with OA Access disabled, but do not include databases or projects that have been deleted. Clicking on the Organization Admin diamond icon in the table will navigate you 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 will be disabled.
Data usage table
In the second table within the Sub-organizations tab, you can view usage data for all sub-organizations with billable data. The default view of this report is aggregated by sub-organization. If the parent organization itself has billable data, it will be displayed as a row in this table and will be included in the totals across the top of the page.
Changing the view to by Database / Project will display all databases and projects of the sub-organizations and the parent organization. From this table, you can export organization sizes, database sizes, or project sizes by clicking on the export icon above the table.
Organization admin page of sub-organizations
When added to a parent organization, a sub-organization does not change and should function 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:
- Multiple organizations cannot use the same SAML metadata for their SSO configuration.
- 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.
0 Comments