Skip to content

Greenlight: review an approval route

Give every approval a clear next step.

Read the getting-started checklist. Confirm module access, the target records and the change owner before proceeding.

  1. Choose a record type and define when approval is required.
  2. Configure stages, approver resolution and decisions. Include what happens when no eligible approver is found.
  3. Use the available test experience to inspect the route and expected effects before activation.
  4. Test a real submission only in an approved sandbox. Verify who can decide, what locks and how the request reaches a final state.
The route and its approversPlanned view of review steps, selected approvers and completion rules.Screenshot placeholder
Reserved for an approved product capture. No demonstration is available here yet.

Starting, deciding and administering approvals can update records and notify people. Notification and Teams behavior depends on the installed version and configuration.

Record the expected result and compare it with the actual outcome. Keep the configuration in draft or paused if the result or permissions are unclear. A screenshot slot is not evidence of release acceptance.

Developer reference and extension boundaries · Module overview