SpacePermission

Permission type to do anything in Confluence that can't affect the system on which it runs. Users with this permission should be allowed to perform most administration tasks but not install plugins or write macros.

Permission type to do anything at all in Confluence. Users with this permission should be allowed to do virtually anything in Confluence. All actions should check for this permission.

A permission type to control whether a user can update their user status.

View content within the space, including pages, blogposts etc.

A permission type to control whether a user can view user profiles within the system. This only applies to the anonymous user.

represents all permissions which can be used to build SpacePermissions.

A list of all global permissions

A list of all permissions that can not be assigned to the anonymous user

A list of all possible permissions

Creates a new SpacePermission with the attributes of another. Does not copy the id, or other ConfluenceEntityObject state.

For CONF-9469 the equals implementation will ignore the case of the permission user name and group name. Confluence is supposed to be case insensitive with regard to username and group names.

Convert a form parameter name into a space permission. The form parameter name should have been generated from toFormParameterName(String).

Returns the default global permissions that are created when Confluence is set up. These will exist in a newly set up system but may be removed afterwards. Note that the returned objects are freshly created and therefore do not have IDs or other persistence data. By default, confluence-administrators group has admin access, the confluence-users group can view the system and anonymous access is disabled.

The space of this permission.

Is this an administrative permission either globally or at a space level? The previous use of this method was to list the top level permission either globally or at space level. At least one top level permission is required globally and for each space to ensure that somebody can administer it. That method could no longer be called isAdministrativePermission because CONFLUENCE_ADMINISTRATOR_PERMISSION is clearly an administrative permission, but not one that is required.

One permission is dependent on another if the other permission is a guard permission that applies to the same space/global scope, and to the same group or user as this permission. It is used when determining which permissions should be removed as the result of removing a guard permission.

Is this a guard permission, either globally or at the space level? Guard permissions are required before any more permissions can be added for a particular user/group in a particular scope. Globally, USE_CONFLUENCE is a guard permission, at the space level, VIEWSPACE is theguard.

Some permissions are not valid as they can not be assigned to the anonymous user. Really, we should just refuse to create such permissions from the outset, but for now we've just got this check.

Convert the space permission into a form parameter name that can be used for form checkboxes. The reverse of this method is fromFormParameterName(String, Space, String) The format of the parameter name is:

Note: the space is NOT encoded in the form parameter name, and must be kept separately.