Start with onboarding
Know who is involved
See the provider team and customer contacts against the tenant you selected.
MSSP/MDR · Process
Every customer and sub-tenant in one tree.
Set targets once, override where needed.
Tenant Architecture puts your whole book of business in one hierarchy. Select a customer to see its provider team, customer contacts and connectors, and set response targets at the group level for its sub-tenants to inherit.
Customers and sub-tenants in Tree or Graph viewMSSP Team and Customer Team per tenantResponse targets inherit parent and global settings
Tenant ArchitectureNorthstarHarbor Retail
Open casesOpen cases47
Connectors32
Team53
Tree
Your MSSP
Northstar
Harbor Group
Harbor Retail
Harbor Logistics
Juniper
Select a tenant to inspect its team, connectors and service settings.
Northstar
- MSSP lead
A. Rivera- MSSP Team
3 analysts- Customer contact
E. Vos- Customer Team
2 contacts- Connectors
- 3
- Open cases
- 4
Select a tenant to inspect its teams, connectors and service settings.
Tree
Your MSSP
Northstar
Harbor Group
Harbor Retail
Harbor Logistics
Juniper
Select a tenant to inspect its team, connectors and service settings.
MSSP Team
A. RiveraLead
M. KayaSecurity Analyst
J. DahlSecurity Analyst
Customer Team
E. VosCISO
T. BakkerIT manager
Tree
Your MSSP
Northstar
Harbor Group
Harbor Retail
Harbor Logistics
Juniper
Select a tenant to inspect its team, connectors and service settings.
Connectors
Microsoft SentinelTenant-specific connectionOwn profile
CrowdStrike FalconTenant-specific connectionOwn profile
Microsoft SentinelTenant-specific connectionCrowdStrike FalconTenant-specific connectionServiceNowShared connection
SharedThis panel lists connections without showing their credentials.
Tree
Your MSSP
Northstar
Harbor Group
Harbor Retail
Harbor Logistics
Juniper
Select a tenant to inspect its team, connectors and service settings.
SLA Matrix
Critical / TriageHarbor Group
InheritedHigh / InvestigationHarbor Group
InheritedMedium / ContainmentPlatform settings
Global defaultThese are workflow targets for tracking your service, not a promise of response times from Imperum.
Team assignments and target overrides apply immediately to the selected tenant.
Find Northstar in the provider’s customer hierarchy.
Review the provider analysts and customer contacts assigned to Northstar.
Inspect Northstar’s own and shared connectors without exposing credentials.
Select Harbor Retail to inspect its service targets inherited from Harbor Group.
Illustrative customer workflow
01 - What it does
Give each customer a place and a team.
A customer group can contain sub-tenants without losing the people responsible for each one. Tenant Architecture puts the hierarchy beside the selected tenant’s operational settings, ready for the next handover.
Open the tenant before the handover.
The Tree and Graph views organize customers and sub-tenants. Selecting a tenant brings its provider analysts, customer contacts and connectors into view. The MSSP Team identifies the lead, while the Customer Team keeps the customer’s contacts close to the work. The SLA Matrix shows whether a target is an override, inherited from an ancestor or taken from a global default. Assignments and target overrides take effect immediately for the tenant you selected.
A handover starts with the customer’s team and service settings already in view.
Harbor Retail: service setupExample
- Parent
- Harbor Group
- MSSP lead
- A. Rivera
- Connectors
- Own and shared
- Targets
- Inherited
Illustrative customer and configuration. Not customer performance data.
Reuse service targets
Sub-tenants can inherit targets, with overrides where the service requires them.
02 - How it works in the product
Select a node. Work on that tenant.
The hierarchy sets the working context for the detail panels. Review the customer’s team and connections before adjusting service targets, so changes reach the tenant you intend.
- 01Onboard New Customer
Add the customer to the provider’s tenant hierarchy.
- 02Tenant Architecture
Open Architecture under Multi-Tenant and explore the Tree or Graph view.
- 03MSSP Team and Customer Team
Select the tenant, assign the provider analysts and review its customer contacts.
- 04Connectors
Inspect its own and shared connectors without viewing their credentials.
- 05SLA Matrix
Set targets by priority and phase, retaining inherited defaults where appropriate.
Rule-specific targets take precedence, followed by the tenant or nearest ancestor setting, then the global default. These are workflow targets for tracking your service, not a promise of response times from Imperum.
03 - How it connects
Put the customer map beside the case work.
Tenant Architecture establishes the customer context. Casebook supplies the work carried out in that context, while connector profiles supply access to each customer’s tools.
Works with
In the editions
The PortalDefault module
Multi-Tenant is a default module of this edition.
Autonomous SOCOutside the defaults
Confirm a license that covers provider operations.
SecOps PlatformIncluded
Multi-tenant operations are part of this tier.
04 - What it means for your service
Onboard a subsidiary as a node, not a project.
A sub-tenant joins under its parent and inherits the group's targets, so onboarding a subsidiary does not mean rebuilding its settings. The next operator finds the customer's people and targets in one place instead of in separate notes.
Less context to reconstruct
The selected tenant brings its team, connectors and service settings together.
Fewer repeated target settings
Inheritance carries parent or global targets down the customer hierarchy.
Contacts stay with the customer
The Customer Team panel identifies the people attached to that tenant.
Start with one customer
- 01Map one customer group
Place its sub-tenants under the intended parent.
- 02Review the people
Check the provider lead and the customer contacts on the selected tenant.
- 03Inspect the targets
Check inherited cells before adding the overrides the service needs.
Questions about Customers and sub-tenants.
1Can a customer have sub-tenants?
Yes. Customers and sub-tenants form a hierarchy that you can explore in Tenant Architecture. Service targets can inherit from a parent tenant or global settings, with tenant and rule-specific overrides where configured.
2Who can see a sub-tenant?
Authorized provider operators and administrators can access the customer scope assigned to them. Tenant context scopes supported views, API operations and connector credentials; placing a tenant in the hierarchy does not replace access permissions.
3Are inherited targets a promise of response time?
No. These are workflow targets for tracking your service, not a promise of response times from Imperum. Rule-specific targets take precedence; otherwise a tenant override, the nearest ancestor setting or the global default applies.
Have any other questions? Talk to our team
A clear customer map.
A clearer handover.
Review your customer hierarchy, teams and service targets with the Imperum team.