Restrict Scroll Versions activation by space

Nils Bier
Last update: Mar 11, 2016

Info

Only Confluence administrators can configure these restrictions, and the restrictions don't apply to Confluence admins. They will always be able to activate and deactivate Scroll Versions modules in any space. A warning will still be displayed when a Confluence admin enters the space admin section in a space that isn't permitted to use Scroll Versions.

Confluence administrators can restrict which spaces Scroll Versions modules can be activated in. To do so:

If multiple modules that use the Advanced Plugin Settings are enabled.

Choose Scroll Platform.

Edit versions.restrict.to.spaces and insert the space keys for each space where Scroll Versions should be able to be activated, separated by commas.

Once this feature has been configured, no Scroll Versions modules can be activated in spaces that aren't in the list. If a space admin views the Scroll Add-ons tab in a space that isn't in the list, no Scroll Versions screens will be displayed.

No changes will be made to spaces where Scroll Versions is already enabled, but a warning will be displayed in the space admin section. Modules that were already enabled will still be active, and it will still be possible to add further versions, variants etc. No further modules can be activated, but active modules can be deactivated.

When publishing to a new or existing space, required modules (e.g. Permalinks) will be enabled in the target space but no new modules can be enabled until that space key is added to the restriction list.

If all Scroll Versions modules are disabled, the Scroll Add-ons space admin section will become unavailable after a page reload.

Info

These restrictions also apply to REST calls. If a space isn't on the restriction list, space admins will only be able to disable modules using the REST resource, not enable them.