Skip to main content

Company Segregation and Visibility Settings

Updated

Purpose: Use this article to understand how Company-level data segregation and visibility settings work in Administrate.

These settings control whether records are shared across all Companies or restricted to specific Companies.

This article explains:

  • Company-level visibility settings
  • Course Template visibility
  • Account segregation
  • Workflow segregation
  • Cross-Company data access behavior

Company segregation settings control how data is shared or restricted between Companies in Administrate.

These settings determine whether records such as Course Templates, Accounts, and Event Workflows are visible across all Companies or restricted to specific Companies.

Organizations with multiple branches, divisions, subsidiaries, or business units can use these settings to control operational separation and data visibility.

Table of contents

Overview

Company segregation settings determine whether selected records are shared across all Companies or restricted by Company.

These settings are especially useful where confidentiality is important, where business units operate independently, or where different Companies need to manage their own customers, workflows, or course catalogs separately.

Depending on your organization’s operational model, you may choose to:

  • share records globally across all Companies
  • restrict records to specific Companies
  • allow selected cross-Company access where appropriate

Note

These settings affect Company-level visibility and segregation behavior. They are separate from User Roles and User Permissions, which control what actions Users can perform in Administrate.

Enable Global Course Template List

Default setting: No

This setting controls whether Course Templates are shared across all Companies or restricted individually.

  • Enabled: All Companies can view and use all Course Templates.
  • Disabled: You can manually select which Company each Course Template is applicable to, including all Companies, on a per-template basis.

Enable this setting when all Companies should share a common course catalog and operational structure.

Disable this setting when different Companies need to maintain separate Course Templates or control which business units can access specific training products.

Choose the Company a Course Template belongs to
 

Choose the Company a Course Template belongs to.

Enable Account Segregation

Default setting: No

This setting determines whether Accounts are shared across Companies or restricted.

  • Enabled: You can select which Company an Account is applicable to, including all Companies (Everyone), on a per-account basis.
  • Disabled: All Companies can see all Accounts.

Enable this setting when different Companies manage separate customer bases or require controlled access to account data.

This is especially useful where:

  • business units operate independently
  • customer confidentiality is required
  • different Companies maintain separate account ownership
  • sales or delivery operations should remain isolated

Account segregation setting
 

When enabled, you can choose which Company an Account belongs to.

Enable Workflow Segregation

Default setting: No

This setting controls whether Event Workflows are shared across Companies or restricted to the Company that created them.

  • Enabled: Workflows are restricted by the Company that created them.
  • Disabled: All Companies can view and use all workflows.

For example, if your Edinburgh Company creates an Event Workflow, your Glasgow Company would not be able to view or use it while workflow segregation is enabled.

Enable this setting when different Companies:

  • use different operational processes
  • maintain separate workflow standards
  • require isolated automation behavior
  • should not access each other’s workflow logic

Note

Workflow segregation affects visibility and usage of Event Workflows between Companies, but does not change User-level permissions or Roles.

Related articles