Start with onboarding
A place for customer updates
Customers return to requests and permitted cases to follow their work.
MSSP/MDR · Customer front door
Give customers a view of their own work.
Keep access in the customer context.
Give each customer a place to follow requests and permitted cases in the Self-Service Portal. Tenant context scopes supported views, while the portal configuration shapes the customer workflow, so your team can provide a shared point of reference for the work it delivers.
Tenant-scoped viewsPermitted customer casesPortal configured per customer
Security Operations Portal
Casebook
NS-104Privileged account activity
SummarySign-in activity under investigation
TimelineInvestigation in progress
NotesAnalyst context on the case
Northstar
- Tenant
- Northstar
- Portal
- Enabled
- Requests
- Customer requests
- Cases
- Permitted cases
Customer access
Requests and permitted security cases related to the organization.
Casebook
NS-104Privileged account activity
SummarySign-in activity under investigation
TimelineInvestigation in progress
NotesAnalyst context on the case
EntitiesAffected user account
Northstar caseNorthstar
Customer view
- Case
- NS-104
- Title
- Privileged account activity
SummaryInvestigation context
TimelineCase progress
Northstar
Customer view
- Tenant
- Northstar
- Portal
- Enabled
- Requests
- Customer requests
- Cases
- Permitted cases
NS-104
Summary
Privileged account activity is under investigation.
Timeline
A. Rivera is reviewing the sign-in evidence.
Cases
Security cases related to your organization.
Northstar
NS-104Privileged account activity
InvestigationCases
Security cases related to your organization.
- Request
- Access review
- Context
- Customer view
Harbor Retail
Suspicious OAuth consent grantCloud source
InvestigationCases
Security cases related to your organization.
- Request
- Incident report
- Context
- Customer view
What a customer sees follows their tenant and permitted cases, configured per customer.
Start with the Northstar case in the provider workspace.
Switch the illustration to Northstar customer context and review the visible case sections.
Read the Summary and Timeline in the customer view. This is an illustrative configuration.
Each portal shows its own permitted cases. The two customer views are shown side by side for comparison.
Illustrative customer workflow
01 - What it does
Give customers a shared point of reference.
A customer should be able to follow its own work without entering your provider workflow. The Self-Service Portal gives customers access to requests and permitted security cases related to their organization.
Start with the customer context.
Enable and configure the customer request portal for the tenant you serve. Customers use My Requests to follow submitted work and Cases to follow permitted security cases. Review access alongside the service catalog and approval rules during setup, so both teams have a shared reference for the work.
Customers follow their own requests and cases without entering your provider workflow.
Northstar: customer accessExample
- Portal
- Enabled
- Tenant
- Northstar
- Requests
- Customer requests
- Cases
- Permitted cases
Illustrative customer and values. Not customer performance data.
Scope stays explicit
Configure customer access around the tenant and service it receives.
02 - How it works in the product
Review access from the customer side.
Set up the customer workflow, then check what the customer can follow. Tenant context and permitted cases define the scope; review the configuration as part of onboarding rather than relying on the provider view.
- 01Self-Service Portal
Enable and configure the customer request portal for the tenant.
- 02Service Catalog
Choose the request types and forms the service offers, with their approval rules.
- 03My Requests
Check that the customer can follow submitted work in its context.
- 04Cases
Review the permitted security cases related to the customer organization.
Tenant context scopes supported views, API operations and connector credentials. Confirm permissions and the required data boundary during architecture review.
03 - How it connects
Connect the customer view to the service.
Casebook keeps the investigation record for your operators. The separately enabled customer portal gives customers access to their requests and permitted cases, while The Portal edition supports the provider workflow.
Works with
In the editions
The Portal, Autonomous SOC and SecOps PlatformEnabled per tenant
Customer-facing access is configured separately from the edition and its module entitlements.
04 - What it means for your service
Keep progress visible to the customer.
A defined customer view gives both sides a place to return for context. Review access during setup and use the permitted case record to support the service conversation.
Fewer context requests
Give the customer a place to follow its submitted requests and case work.
Access reviewed at setup
Check the customer tenant and permissions before using the portal.
A shared reference
Use the permitted case to keep the customer conversation tied to the work.
Start with one customer
- 01Choose a customer workflow
Select a request type and case your service needs the customer to follow.
- 02Check customer access
Review the configured portal in that customer context.
- 03Review the handoff
Confirm the customer knows where to follow requests and permitted cases.
Questions about Customer-scoped visibility.
1How is each customer’s data kept apart?
Multi-tenant mode uses tenant context to scope supported views, API operations and connector credentials. Customer profiles let you configure separate service connections. Authorized provider operators and administrators can access the customer scope assigned to them. Confirm the required data boundary, permissions and deployment arrangement for each customer during architecture review.
2What does a customer see in its portal?
Customers can browse the Service Catalog, follow their requests and view permitted security cases related to their organization. Enable and configure the customer request portal for the service you deliver.
3Does the customer view depend on The Portal edition?
The Portal is a provider edition. The Self-Service Portal is a separate customer-facing feature that is enabled and configured per tenant. Distinguish the edition and module entitlements from customer access and workflows.
Have any other questions? Talk to our team
Keep the customer
connected to its own work.
Review customer access and the portal workflow with the Imperum team.