Actions and approvals
Home · Actions and approvals
Goal
This page explains the governed action workflow: propose an action, get it approved, reject it when needed and understand when it is actually executed.
Propose an action
- Open the signal, PM Document or page that proposes the action.
- Select the available action, such as publishing to SharePoint or creating a Jira ticket.
- Review content, destination and summary.
- Add a justification if requested.
- Submit the action.
- Check its status.
Approve or reject
- Open Actions & approvals.
- Filter pending actions.
- Open the action details.
- Review evidence, destination, impact and requester.
- Select Approve or Reject.
- Add a clear reason when requested.
Approved is not executed
An approved action is authorized. Executed means the target action actually happened. External actions require a validated connector, permitted policy and live mode when applicable.
Common blockers
| Blocker | Meaning |
|---|---|
| Insufficient role | Your role cannot propose or approve |
| require approval | Approval is mandatory |
| deny | The policy forbids the action |
| Not bound | The project is not connected to the integration |
| Not healthy | Connector or provider is not operational |
| Live mode off | No real external object will be created |