Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Note

Page is under construction.

Table of Contents

A user role is a consolidation of several permissions. A permission is a 'delegation of authority' or a 'right' assigned to a user or a group of users to perform an action on a system. Permissions can be granted to or revoked from a user/user group/user role automatically or by a system administrator. For example, if a user has the permission to log in to a systems, then the permission to log out is automatically implied without the need of granting it specifically.   Instead of associating permissions with a user, admins can associate permissions with a user role and assign the role to users. User roles can be reused throughout the system and prevents the overhead of granting multiple permissions to each and every user individually.

...

  • publisher - users in this role will be allowed to create new assets (i.e., an asset author would belong to this role).
  • reviewer - users in this role are considered as the store reviewers. Every asset needs to be reviewed by a user in this role, before the asset is published into the ES Front.
  • private_{username} - users’ private role. Every user in the ES are automatically associated with a role that is created by prefixing their username with private_ . This role is used to control per user permissions.

Permissions associated with user roles

User roleAllows Actions
Publisher
  • Create assets.
  • Submit assets to the in-review state.
  • Publish approved assets.
  • Unpublish assets.
  • Deprecate published assets.
  • Retire deprecated assets.
  • Delete retired assets.
  • Delete rejected assets.
reviewer

Approve or reject assets that are in the in-review state.

private_{username}?

...