What this page is for
This is where you decide that Production will not publish Maya's homepage hero until Priya and Jordan have both approved it — and that Staging will not wait. The story of why is on Approvals. The clicks are here.
Settings belong to the project, not to one environment page. Opening Staging or Production in the same project shows the same Approval Settings card. The two environments still have their own switches, their own minimums, and their own lists.
Open Approval Settings
- Open the organization → team → project → any environment home. The card is not inside a widget.
- Find Approval Settings. The line under the title is "Require approvals before widgets and collections are published to Staging or Production."
- Click Staging settings or Production settings. You only see a button for an environment you can view. If you can view neither, the card is not on the page.
The page title is Approval Settings. Tabs across the top are Staging and Production. Each tab is its own screen, so a person who can manage Production and only view Staging sees an editor on one tab and a read-only page on the other.
A team created before approvals existed does not have these groups yet. On the team's User Groups page, open Import New User Groups and import them. They land under User Group To Manage Approvals.
View Approval Settings In Staging and View Approval Settings In Production can open the screen. Manage Approval Settings In Staging and Manage Approval Settings In Production can change it. Ask someone in Manage User Groups to add you.
If you can view but not manage, the toggle, the minimum, and the names are on the page, and Save is not. The notice tells you which Manage group you need.
Turn Production on
- On the Production tab, turn on Collections and widgets require approvals. The description under the switch says widgets and collections in Production must be approved before they can be published.
- Set Minimum required approvers. The hint under the field says the number is from 1 to 50. Two means Priya and Jordan both have to approve. One means either of them is enough.
- Under Approvers, use Add an approver. The menu lists active teammates who are not already on the list, as a name and email. Click Add. The summary above the list reads like "2 approvers · 2 required."
- Click Save. The page says Approval settings saved. Discard changes puts the form back to the last save. Save stays disabled until something changed and the form is valid.
The hint under the menu is the rule: only active team members can be approvers. If someone is missing, invite them from Organizations & Teams and wait until they accept. Pending invitations are not on the menu.
You can list up to 50 people. The minimum cannot be higher than the number of active approvers. If the list has one active person and the minimum is 2, Save stays off and the page says to add approvers or lower the minimum. An empty list with the switch on cannot be saved. The empty line is "No approvers yet. Add one below."
What each control is for
| Control | When you reach for it |
|---|---|
| Collections and widgets require approvals | Production should wait. Off means Publish Now works again in that environment. On means those buttons become Submit for approval. |
| Minimum required approvers | How many current approvers must say yes before Publish appears. From 1 to 50. It is not a percentage of the list. |
| Add an approver / Remove | Who may approve or reject in this environment. Removing someone does not delete approvals they gave in the past as history, but those approvals stop counting immediately. |
| Staging and Production tabs | QA publishes freely, the live site waits — or the reverse. Saving one tab does not change the other. |
Turning it off keeps the list
Turn the switch off and save. If people were on the list, the page says approvals are off, so nothing needs approval before it is published, and the approver list is kept for when you turn approvals back on.
Turn it back on. Priya and Jordan are still there. You do not rebuild the list. The minimum you saved is still the minimum.
Turning approvals off does not throw away a request that is already open. It does change what Publish Now means. With the switch off, that button publishes the current draft. The open request, if it is already approved, can still be published from Approval Requests, and that button publishes the frozen copy. Those are two different heroes if Maya edited after she submitted. Leave the switch on until the request you care about is published, rejected, or withdrawn.
Someone who left the team
An approver who is no longer an active member stays on the list with an Inactive badge. The note under the list says they cannot approve and do not count toward the minimum. The summary adds them in parentheses, as in "2 approvers · 2 required (1 inactive, not counted)."
If that drops you below the minimum, Save will refuse the next edit until you add someone or lower the number. A request that was counting their approval loses that count the moment they are inactive, even before you edit the settings.
Remove them when you want the list to match the team. Removing is not required for the count. Inactive already means "not counted."
What this screen does not do
- It does not publish, and it does not approve. Submitting is Submitting for approval. The queue is Reviewing and publishing.
- It does not email Priya. She sees work on the Approval Requests card.
- It does not apply to Development, or to an environment you named yourself. Those have no publish step.
- It does not change Promote to Staging, Promote to Production, or Copy To. Those still move drafts. They are on Widgets.