Manage customer tenants, pre-onboard new customers, monitor workspace health, and configure modules from one central location.
The Workspace Center is your administrative control panel for every customer tenant. Monitor active workspaces at a glance, pre-onboard new customers, and drill into per-workspace settings.
Workspaces represent individual customer tenants in ContraForce. Each workspace has its own data, configurations, modules, and user permissions.
Green: healthy. Amber: needs attention. Blue: pre-onboarded. Hidden on the service provider’s own workspace
Workspace name
The customer’s friendly name
Tenant ID
The customer’s Microsoft Entra tenant ID, in muted text below the name
Inline chip
”Your workspace” on the service provider’s own card; “Service provider” if the row represents the MSP itself with no monitoring on it
Modules pill
Visible on the Workspaces tab. Healthy when at least one detection module is configured
Agent pill
Visible on the Workspaces tab. Healthy when an Agent Center is deployed
Health pills only appear on the Workspaces tab. The Onboarding tab uses the blue pre-onboarded status light instead, since health checks are not meaningful until the customer admin completes their onboarding.
Click any card to open the workspace’s settings page.
Workspace settings page after clicking a card
The settings page exposes four areas:
General
Account Information and Service Provider Information: account identifiers, points of contact, account ID, account type, and subscription information
Allow Service Providers to Run Gamebooks: manage the team members responsible for approving Gamebooks that require manual authorization. Only users with the Workspace Owner role can be assigned as Gamebook Approvers
Modules: configure and manage detection and response modules
IAM: manage users, groups, and permissions at the workspace level
Notifications: configure the notifications module for Microsoft Sentinel
Pre-onboarding lets you prepare a customer’s workspace before they complete onboarding themselves. The customer admin receives an invite email and finishes the rest. See Customer Workspace Onboarding for the customer-side flow.
Click the Onboarding tab at the top of the Workspace Center
2
Click Add workspace
The button is in the top-right of the toolbar. The right-hand rail panel opens with the Add workspace form
Add workspace rail open on the Onboarding tab
3
Fill in customer details
Field
Description
Workspace name
Friendly label you’ll use to refer to this customer
Tenant ID
The customer’s Microsoft Entra tenant ID
Primary point-of-contact email
The customer admin who will receive the invite
Detection modules
Pre-select the security tools the customer is bringing
Response modules
Pre-select the response capabilities the customer will use
4
Click Send Invite
ContraForce sends an invite email to the POC. The new workspace appears as a card on the Onboarding tab with a Pending customer setup badge
New pre-onboarded workspace card
Click any pre-onboarded card to see its onboarding progress in the right-hand rail. Use this to confirm which modules the customer has connected so far.
You’ll receive a real-time Customer onboarding complete notification in the portal. The card moves from the Onboarding tab to the Workspaces tab, and the status light flips from blue (pre-onboarded) to green (healthy) or amber (needs attention) based on what the customer connected.For the post-go-live verification runbook, see Workspace Onboarding Verification.
Each workspace can have different modules enabled based on customer needs. Open a workspace’s settings page (click the card), then go to the Modules tab.
Click the workspace card to open its settings page
2
Go to the Modules tab
Find the module that needs consent
3
Click Consent
A Microsoft authentication window opens
4
Sign in as a Global Administrator
Sign in with a Global Administrator account. ContraForce uses app-only Microsoft Graph permissions, so Cloud App Admin or Application Admin cannot grant this consent
5
Review and accept
Review the requested permissions and click Accept
Consent requires Global Administrator privileges in the customer’s Microsoft tenant. Work with your customer’s IT team if you don’t have Global Administrator access.
Learn more about platform permissions
Complete guide to platform users, groups, permissions, and modules