Strategy Workflows
Control & DirectionStrategy Workflows govern how security strategies move through review and approval before becoming active. SecureHive provides a configurable workflow system that supports tenant-level defaults and per-strategy overrides, ensuring that each strategy receives the appropriate level of governance scrutiny.
Strategy Workflows integrate with Strategy Management (strategy lifecycle), Steering Committee (committee approvals), and Settings (tenant-default configuration).
How approval works
The strategy approval process follows a defined sequence from submission through final committee sign-off.
Submit for approval
From the strategy detail page, click Submit for Approval. This moves the strategy into the configured approval workflow and notifies the assigned reviewers.
Workflow stages
The strategy progresses through the workflow stages defined in the active workflow template. Each stage can have its own reviewers and approval requirements. Reviewers receive notifications and can approve or reject at each stage.
Steering Committee approval
If the workflow includes a Steering Committee approval stage, the strategy routes to the linked Steering Committee for formal review. Committee members assess the strategy’s alignment with organizational goals, review resource requirements, and record their decision.
Activation
Once all workflow stages are complete and approvals are recorded, the strategy can be moved to Active status.
Workflow Configuration tab
Each strategy’s detail page includes a Workflow Configuration tab. This tab allows you to view and manage the approval workflow assigned to that specific strategy.
From this tab you can:
- View the list of available STRATEGY workflow templates defined at the tenant level.
- See which workflow template is currently assigned to the strategy.
- Override the tenant-default workflow by selecting a different template for this strategy instance.
- Configure instance-level role mappings that determine which users fill each workflow role (e.g., reviewer, approver) for this particular strategy.
Per-strategy workflow overrides only affect the individual strategy. They do not change the tenant-default workflow used by other strategies.
Approvals tab
The Approvals tab on the strategy detail page provides a consolidated view of the approval process:
Workflow Status Display — Shows the current state of the workflow, including which stage the strategy is in, who has approved, and what stages remain.
Approval Action — If you are an assigned reviewer or approver for the current stage, you can take action directly from this tab. Record your decision (approve or reject) with comments.
Steering Committee approval history — Displays the full history of committee-level approvals, including the approver, decision, date, and any comments provided. All decisions are permanently recorded for audit purposes.
Tenant defaults vs. per-strategy overrides
SecureHive uses a two-tier configuration model for strategy workflows:
| Level | Scope | Where to configure |
|---|---|---|
| Tenant default | Applies to all new strategies unless overridden | Settings |
| Per-strategy override | Applies only to the specific strategy | Workflow Configuration tab on the strategy detail page |
When a new strategy is created, it inherits the tenant-default workflow. If a strategy requires a different approval path — for example, a high-impact strategy that needs additional review stages — override the workflow from the strategy’s Workflow Configuration tab.
Permissions
Configuring workflows at the tenant level requires the strategy:manage permission and access to the Settings page. Taking approval actions (approve, reject) on a strategy requires the user to be assigned to the appropriate workflow role for that strategy instance.