Data Flow through the OpsAnalitica Platform

As we discussed earlier, the OpsAnalitica Platform supports a Parent-Child organization relationship. Meaning that the parent org can have children orgs, and those child orgs can have their own children, etc.., etc.., etc.

With this hierarchy of organizations, data flows from the top down and from the bottom up to make the platform usable at all levels.

This document will explain how this data flows up and down the platform.

Key Concepts:

Parent Organization: when you become an OpsAnalitica Client we create an organization within the platform for your company.
- The organization is the container for all of your checklists, locations, users, and data.
- If you use our multi-org structure we would refer to the original organization as the Parent Organization.
Ancestor Organization: any organization that is above your current organization in the hierarchy.
Descendant Organization: any organization that is below your current organization in the hierarchy.
Ex: From the image above - Child Org 1 is a descendant organization of the Parent Organization and an Ancestor Organization to Child Org 2.
Home Organization: is the organization that an entity was created in, a checklist could be created in Child Org 1 and that would be it's home organization.

Inheritability:

Throughout the platform, you will see the Inheritable button on certain entities: locations, tags, rules, checklists, roles, and filters.

When an ancestor organization makes a checklist inheritable they are allowing their descendants to use the checklist. An example: Parent Organization makes a food safety checklist, they make it inheritable, and then all of their locations in Child Org 1 & 2 are able to use that checklist as well.

An inherited item flows down the hierarchy and can be used by all descendants.

Benefits of Inheriting Entities:

Manage the entity in one place.
- A Parent Organization can have one Food Safety Checklist for their entire chain vs. having to make it multiple times.
Descendants cannot change the entity.
- Child Org 1 & 2 can use the Food Safety Checklist but they cannot edit or change it.
Simplifies administration and reporting of the platform.

Rules around Inheriting Entities:

You cannot control with descendant org get an inherited entity. All descendants get access to the entity. You can control who can see the entities through filters after the fact.
Changes to the entity can only be made in the organization where it was created.
Inherited entities will be sorted at the bottom of a list of entities and show a down arrow next to it in the admin portal.

Data Flow:

Item	Inheritable	Data Flow Down	Data Flow Up
Checklists	Can be made inheritable.	Can be completed by descendant organizations.	Only inherited checklist responses flow up to the ancestor org where the checklist was created. Checklists created in the current org will not flow up to an ancestor.
Users	Users, by default, always have access to their descendant organizations. They need the proper roles in the system to navigate to their descendant orgs.	Users with proper roles can change navigate from their current organizations to descendant organizations and come back. Users with inherited roles can do everything they are allowed to do in their parent organization in a descendant organization.	Users from ancestor organizations who complete inherited checklists in a descendant org will have their checklist response sets flow up to the ancestor org that originally created the checklist. Users from ancestor orgs will appear in report filters in their ancestor orgs if they completed checklists that were inherited. Users can never navigate to an ancestor organization above the home organization they were created in.
Locations	Locations can be inherited to descendant orgs. This is not a common practice.	Locations that are inherited to their descendant orgs will function the same as a native location in that organization from a checklist and reporting perspective.	Locations created in the current org will not be available in an ancestor organization, in report filters, unless it was the location where an inherited checklist was completed.
Roles	Roles can be inherited to descendant orgs.	Users can use inherited roles in their descendant organizations.	N/A
Filters	Filters can be inherited to descendant orgs.	Filter results will only show the users or locations that match the filter in the current org where the filter results are being viewed. If you are viewing a filter in the parent org, it will not show results from the descendant orgs.	In reporting filters will show results from the current org and descendant orgs as long as the checklists that are being reported off of were inherited down.

Next Section