Centrik 5 User Guide - System Overview (Understanding Subsystems and Zones)

Overview

Subsystems and Zones help you organise and separate information within Centrik, making it easier to manage access to different areas of the system.

In most modules, information is organised into Subsystems. Each subsystem has its own content, records and, in some modules, its own configuration settings.

The Compliance module uses an additional level of organisation called Zones. A zone groups together one or more subsystems, allowing compliance activities to be separated by operational area, business unit, regulatory approval, or any other organisational requirement.

As a result, the structure of most modules differs slightly from the structure used within Compliance:

Most modules:

• Module
  • Subsystem
  • Subsystem
  • Subsystem

Compliance Module:

• Zone
  • Subsystem
  • Subsystem
• Zone
  • Subsystem
  • Subsystem

Although Zones provide an additional layer of separation, Compliance records and permissions are still managed through subsystems. Zones simply provide a higher-level grouping of those subsystems.

Example of 3 Compliance Zones (Ops, CAMO, Third Party):

When working within Compliance, select a Zone first. Depending on the audit type being used, the available subsystems can then be viewed in:

• The Checklists schedule tab for Checklist and Self Audit activities.
• The Third parties tab for Third Party Audit activities.
• The Surveys tab for Survey type audits

Understanding how subsystems and zones work can help you choose a structure that reflects your organisation while ensuring users only have access to the information relevant to their role.

About Subsystems

A subsystem is a separate area within a Centrik module.

Each subsystem has its own:

• Content
• Records
• Access rights

This allows information to be separated by department, function, business unit, operating certificate, or any other organisational requirement.

For example, users with access to only one subsystem will not be able to view content held within another subsystem.

Why use subsystems?

Use subsystems when different groups of users need access to different information within the same module.

Common examples include:

• Separating Flight Operations from Ground Operations
• Separating business units within a larger organisation

Because permissions are assigned at subsystem level, administrators can control exactly which areas of a module users can access.

Requesting a New Subsystem

Subsystems can only be created / modified / deleted by TrustFlight Support.

If you require an additional subsystem, contact TrustFlight Support with details of:

• The module where the subsystem is required
• The name of the subsystem
• Any specific configuration settings (if known)

Once created, administrators can configure role permissions to determine who receives specific access to the subsystem. This approach helps ensure users only see the information required for their role.

An example Training module subsystem structure could be:
 

Then with access rights, for example, a Crew Training Administrator could be given access to the Flight Crew and Cabin Crew Training subsystem without being granted access to Engineering Training records.

View Available Subsystems or Zones

If your user profile / job role has access to multiple subsystems or zones, you can switch between them using the main navigation menu.

To view available subsystems or zones:

1. Select the downward arrow next to the appropriate module.
2. Review the list of available options.
3. Select the subsystem or zone you want to open.

The options displayed depend on the permissions assigned to your user account.

If you only have access to a single subsystem or zone, there often won't be a dropdown selector on the main navigation menu.