Skip to main content
Workspaces let one organization run more than one Minerva operating context. Each workspace has its own screening configuration, saved presets, and audit history, so administrators can tune settings away from production before deciding what to promote into Live. Access: Requires the Admin role or above. Use the workspace selector in the sidebar to switch your current workspace. To manage workspaces, go to Administration > Configuration, then open Workspaces. Use this guide when you need to:
  • understand what changes when you switch workspaces
  • tune configuration in a Calibration workspace without changing Live
  • save reusable workspace presets
  • promote a preset from Calibration to Live
  • decide which settings are workspace-scoped and which settings are tenant-wide
Live is the default production workspace. Calibration is the recommended workspace for testing configuration changes before they are used in Live screening and risk-assessment workflows.
Calibration is isolated from Live, but it still uses real Minerva workflows. Use representative approved test cases, avoid unrelated customer data, and confirm the selected workspace before creating or changing records.

​
Switching Workspaces

The workspace selector appears in the main sidebar. The selected workspace controls the workspace-aware configuration that the app uses for the current organization. The example below shows the actual Workspaces configuration page with the selector open. Most organizations start with two active workspaces:
WorkspacePurpose
LiveThe default production workspace for active operations, production API usage, onboarding, ongoing monitoring, and analyst review.
CalibrationA separate workspace for testing match scoring, repeated alert suppression, and other operational settings before those settings are used in Live.
Additional active workspacesOptional team, region, product, or integration-specific workspaces when your organization needs more than one non-production context.
Archived workspacesWorkspaces that are no longer selectable for active use. API keys tied to an archived workspace should be treated as disabled.
When you switch workspaces, the sidebar label changes immediately. Configuration pages, presets, and workspace-scoped API behavior should then reflect the selected workspace.
If a result or configuration does not look familiar, check the workspace selector before editing. Many troubleshooting cases come from reviewing Calibration while expecting Live, or the reverse.

​
What Is Workspace-Scoped

Workspace-scoped configuration changes with the selected workspace. It is owned by the workspace so that Calibration can safely diverge from Live while administrators test changes. Workspace-scoped settings include:
  • Match scoring, including feed thresholds, workflow thresholds, and News data filtering
  • Role-aware adverse media, including article labels, confidence thresholds, and automatic adverse-media filtering
  • Repeated Alert Suppression, including repeat-alert rules and suppression state
  • screening source and feed settings where available
  • automatic disposition and alert tuning settings where available
  • risk-assessment and continuous risk review settings where available
  • webhook and integration settings that are explicitly workspace-specific
  • profile groups and screening frequency settings for the selected workspace
  • custom workspace presets and configuration history for each supported configuration page
Tenant-wide settings do not change only because you switch workspaces. These usually include identity, authentication, and account bootstrap behavior such as SAML SSO and SCIM.
Workspace-aware API and service calls use the current workspace context behind the scenes. In the app, the selected workspace is sent with requests. For integrations, API keys and server-side authorization determine which workspace configuration applies.

​
Configurations And Presets

Configuration pages usually combine three related concepts:
ConceptWhat it means
Active configurationThe configuration currently used by the selected workspace. Saving a reviewed change updates this configuration and writes a history entry.
Built-in presetA fixed Minerva preset, such as Balanced, Narrow, Wide, Conservative, or Aggressive. Built-in presets are available across workspaces and cannot be edited directly.
Workspace presetA custom saved preset that belongs to one workspace. It can be reused in that workspace or promoted into another workspace, such as from Calibration into Live.
Use workspace presets when a configuration has an operational purpose that you may want to reuse later. A good preset name and description should explain why it exists, what workflow it supports, and whether it is intended for Live use or continued calibration.

​
Promote A Workspace Preset

Promotion copies a saved workspace preset from the current workspace into another workspace. The common path is to tune and save a preset in Calibration, then promote that preset into Live. Promotion does two things:
  1. Copies the saved preset into the target workspace.
  2. Optionally applies that preset to the target workspace immediately.
The immediate apply option is deliberate. Leaving it off stages the preset in the target workspace so an administrator can review it later. Turning it on updates the target workspace’s active configuration as soon as the promotion is confirmed. The same promotion model is used by other workspace-aware configuration pages that support custom presets. Use the immediate apply option only when you are ready for the target workspace to use the promoted configuration for new activity. For Live, that can affect new screening, monitoring, API, and risk-assessment behavior depending on the configuration being promoted.

​
Calibration To Live Workflow

Use this sequence when testing configuration changes before production rollout:
  1. Select Calibration from the sidebar workspace selector.
  2. Open the configuration page you want to tune, such as Match Scoring or Repeated Alert Suppression.
  3. Start from the closest built-in preset or the current Calibration preset.
  4. Make one focused set of changes and add a clear change description when saving.
  5. Test with representative approved cases in Calibration. For screening, compare result volume, false positives, missed-risk sensitivity, and analyst workload. For risk assessments, compare the retrieved evidence and final reasoning against expected behavior.
  6. Save the calibrated settings as a workspace preset with a name and description that explain the intended Live use.
  7. Promote the preset to Live. Leave immediate apply off if you want to stage the preset for a final Live review, or turn it on only when you are ready to deploy the configuration.
  8. Switch to Live, confirm the configuration and active preset, then monitor the first affected workflows.
Keep Calibration and Live changes small enough to explain in one history entry. Small, named changes are easier to audit and easier to roll back than broad tuning passes across several independent settings.