Space settings
This is the page to keep open while you configure a space. Space administrators find these under space settings, Capable Approval, across six tabs: Teams, Automation, Watchers, Overrides, Security and Banner.
Saved settings are cached for about five minutes, and the cache clears the moment you save. If a change does not seem to have taken effect on a page, reload the page.
#Teams
What each approval team does when it is used in this space. Creating the teams themselves is covered in Manage approval teams.
Setting | Default | Notes |
|---|---|---|
Enable approval team | OFF | A team is not usable in the space at all until this is on. |
Minimum approvers | The team size | Anything from 1 to the team size. |
Minimum rejections | 1 | Anything from 1 to the team size. |
Expiry | No expiry | 1 month, 3 months, 6 months, 1 year, a custom interval or an exact date. See Expiry and re-approval. |
Publish on approval | OFF | Hands the page to Capable Publishing once approved. See Publishing. |
#The space team
Every space has a built-in team of its own, listed as Space team. It holds up to 16 people, has the same settings as any other team, and is the default choice for automation. If you only ever need one reviewer group in this space, use it and skip creating anything.
#Automation
Covered properly in Automatic approvals. The defaults are here for reference.
Setting | Default |
|---|---|
Raise an approval on page creation | OFF |
Raise an approval on page update | OFF |
Default team | Space team |
Label routing, on creation and on update | Off, and the two switch independently |
Label rules | None, up to 50 |
#Watchers
People notified about every approval outcome in the space, whether or not they are approvers. Empty by default, up to 50 people.
Watchers hear about outcomes only, never about a request being raised or an approver being added. A watcher who cannot read the page gets nothing at all. See Notifications.
#Overrides
Settings applied to every approval in the space, whatever an individual chose on the page.
Setting | Default | What it does |
|---|---|---|
Approval expiry | OFF | Forces an expiry period on every approval in the space. |
Publish on approval | OFF | Wins over the team setting and over the individual approval. |
Allow users to edit approvals | ON | Turn it off and only space administrators can raise or change approvals here. |
Restrict who can edit approvals | OFF | Limits raising and editing to named users and groups. See Who can do what. |
Custom intervals accept days, weeks, months or years, with a minimum of 7 days or 1 of any larger unit.
#Security
Three switches
Allow users to edit approvals, on by default, choose whether users can edit approvals after they’ve been sent, useful when working with teams.
Restrict who can edit approvals, choose individual users who can handle approvals in this space.
Require 2FA to approve, off by default. Codes are 6 digits on a 30 second cycle, accepted for one period either side. This is per space, and there is no site-wide equivalent. See Sign approvals with a code.
#Banner
Controls the approval status banner across the top of pages in this space: follow the site setting, which is the default, show it here, or hide it here. The site-wide switch is in Site settings.
#A few things that catch people out
A team that exists but is not enabled here cannot be used in this space, including by automation.
Overrides beat both the team and the page, so check them first when a setting is not doing what somebody expected.
The five minute cache means a reload is often the whole fix.
Requiring 2FA is per space. Setting it in one space does nothing to the others.
#Related
Site settings
The settings that apply everywhere.
Manage approval teams
Creating teams and enabling them here.
Automatic approvals
The Automation tab, explained properly.
Set up a space for approvals
Setting a space up from scratch.
Notifications
Who the Watchers list actually reaches.
Who can do what
What the Overrides tab restricts.
Every switch in one place, with the default next to it.
