The Gridsz platform distinguishes two levels of admin accounts: Cluster admin and Site admin. Depending on the type of party your account is linked to, you can have cluster and/or site admin access rights.

Clustered structure

A cluster represents a Passive Operator (PO) and the parties related to its infrastructure. Within each cluster only one PO party can exist. Depending on the Active Operators (AOs) that are allowed to place orders on the PO’s network and the contractors that are performing the work on the PO’s network, the cluster is created using the AO and Contractor parties as building blocks.

Additionally next to the PO a Network Operating Centre (NOC) party can also be added to the cluster. A NOC party is on the same level of the PO, allowing NOC parties to provide network management if the PO has outsourced that work, but the core of the cluster is still the singular PO entity.

Cluster admin

The cluster admin manages its own cluster settings (depending on the available modules), such as:

• Reset password for other Cluster Admin users and Site Admin users
• Manage party roles
• Manage its cluster parties (within the bounderies provided by Gridsz)
• Manage routing rules
• Manage Service providers
• Manage Service levels
• Manage Status transitions and dependencies
• Manage Reason Codes, Labels
• Connection Statuses
• Upload routing files

The Cluster admin can only reset passwords, but may be allowed to toggle to the Site admin view to have more user manager functionality.

Site Admin

Every party always has at least one Site admin (A PO party’s Site admin can also be Cluster admin). A site admin can only manage its own party and users settings:

• Create and manage users within its own party
• Manage roles, confined by what is allowed by the party role
• Manage the system configuration
• Manage party email notifications
• Manage automated workflows

The individual functionality is described in the dedicated articles.