Working with sub-organizations

Organizations and locations are the mechanisms for organizing clients into a logical structure and the way they are used is pretty straightforward. If you are interested in using sub-organizations, there are some things to consider.

First, let's start with some definitions:

Organizations

  • Represent the top-level structure of clients and can have as many locations as desired.
  • Each asset (configurations, documents, passwords etc.) can belong to only one organization and can be viewed by all users who have access to that organization unless access to that item is restricted.

Sub-organizations

  • Sub-organizations are a way of segmenting an organization so that there is a parent and one or more child organizations. It can be used for locations (or departments, groups, divisions, etc.), when needed.
  • Assets can belong to the sub-organization or the organization, but not both, and can be viewed by all users who have access to that sub-organization or organization unless access to that item is restricted.

Locations

  • Represent physical locations and addresses where the client's users may work.
  • Each asset can be shown to exist in a particular location only if a relationship is mapped (tagging); however, the asset will belong to the organization or sub-organization, not the location. 

Deciding whether to use sub-organizations

Some of your clients may be automatically set up with sub-organizations depending on the way your client billing has been set up in your PSA. If your PSA has parent/child relationships, and you sync those organizations with IT Glue, we will automatically match this parent/child structure in IT Glue.

For your other clients who are billed as one entity, organizations and locations will be enough to match the desired structure.

However, if the infrastructure used at a client location doesn't rely on the infrastructure of the parent organization, you may have a case for creating a sub-organization. The advantage is that the documentation can be structured in a way that will match better with client infrastructure and with location-based documentation needs.

Another advantage is that permissions can be managed such that an overarching authoritative user can be granted permissions for the parent and all child sub-organizations, and conversely a user can be granted access to just a sub-organization, and not to the parent.

Navigating to sub-organizations 

Sub-organizations have the same navigation and search options as organizations. 

In addition, when viewing an organization's home page, you can see its sub-organizations by scrolling to the bottom of the screen. When you click to view a sub-organization, you'll see the top-level organization in the breadcrumbs navigation near the top of the screen.

For information about setting up sub-organizations, see the following:

Was this article helpful?
4 out of 4 found this helpful