Overview
This article explains how user access works in a Group Management setup within the Cye Exposure Management Platform. You'll learn how administrators and power users can manage membership across parent and subsidiary companies, and how authentication methods impact the login experience.
If you're managing access between multiple entities, this guide helps ensure a smooth experience for your team without extra registration steps.
Who Can Access What
Parent-company administrators or power users can view:
The Group-Level Overview
Aggregated risk data
Basic KPIs for subsidiaries
To access detailed data for a subsidiary (e.g., findings, plans):
The user must be a member of that specific subsidiary.
Adding Members Across Companies
In a Group Management setup, all members belong to the same organization. This means you can add existing users from the parent company to a subsidiary (or vice versa) without making them go through the standard registration process.
Here’s how it works:
A the Cye platform administrator uses the regular Defining Members workflow.
The member receives an email notification.
No registration is needed — the account is automatically activated for the new instance.
This applies to:
Adding a parent-company member to a subsidiary
Adding a subsidiary member to the parent company
Customizing the Group-Level Overview Experience
If you're using the Cye platform in a Group Management setup — especially as a Service Provider (MSSP) or part of a Private Equity (PE) firm — you likely need a dashboard experience that reflects the way your organization actually works. That includes the language you use and the data that’s most relevant to you.
the Cye platform offers two customization options to help you tailor the dashboard:
Custom terminology
The option to hide the aggregated mini-dashboard
Let’s look at both.
1. Use Custom Terminology
You can define the terms that appear across the dashboard to better align with your organization’s structure. For example, instead of “Parent company” and “Subsidiary,” you might prefer to use “Service Provider” and “Client” — or any terms that suit your setup.
How to customize terminology:
Go to Settings > Company profile
Define your preferred terms for:
Managing entity (default: Parent company)
Sub-entity (default: Subsidiary)
Once set, these terms will replace all default labels in the dashboard interface.
Default terms: Parent, Subsidiary
Who can change this: Only Admins can modify these settings.
This flexibility helps you align the platform vocabulary with how your team communicates — whether you're managing portfolio companies, business units, or clients.
2. Hide the Aggregated Mini-Dashboard
In some setups, especially where companies under the same the Cye platform account are not directly related, the aggregated mini-dashboard (which displays combined exposure and maturity data) may not be useful.
To keep the interface focused on individual entities, you can choose to hide this section.
How to hide the aggregated mini-dashboard:
Go to Settings > Company profile
Toggle the Aggregation widgets option to Show or Hide the mini-dashboard
By default, the mini-dashboard is visible.
When hidden, the layout will adjust to show only individual company data, making the dashboard cleaner and more relevant to your needs.
This setting is available in Parent company settings only.
Who can change this: Only Admins can modify this setting.
Together ("Use Custom Terminology" + "Hide the Aggregated Mini-Dashboard") these options give you greater control over how the Cye platform looks and feels — so it works the way you do.
Authentication and Seamless Access
If the same authentication method (e.g., SSO or credentials) is used in both instances:
Users can switch between the parent and subsidiaries without logging in again.
If different methods are used:
The user will be asked to log in again when switching between instances.
Wrap-up / Next Steps
Managing users across multiple the Cye platform instances doesn’t have to be complicated. With automatic registration and shared organization membership, you can quickly grant the right access where needed. Just keep authentication methods in sync to reduce login friction.