Page Comparison

Table of Contents

...

Internal/publisher - users in this role are allowed to create new assets (i.e., an asset author would belong to this role).
Internal/store - This is a sample role that is meant to demonstrate the permissions required from a Store user.
Internal/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 Store.
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_ . Use this role to control per user permissions.
Internal/everyone - This is a system reserved role to create system operations.
Info
If you wish to prevent external operations being carried out by the Internal/everyone role, ensure to revoke operations from the role.

...

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

User role	Allowed Actions
`Internal/publisher`	Login to ESthe Publisher. View the asset list. Create and update assets. Submit assets to be reviewed. Publish approved assets. Unpublish assets. Deprecate published assets. Retire deprecated assets. Retire unpublished assetsView the lifecycle management page.
`Internal/reviewer`	Login to the Publisher. View the asset list. View the lifecycle management page. Update the lifecycle state.
`Internal/`	`store`	Login to	the Store. View the asset list. View details of an asset. Bookmark assets. Add a review and rate assets.
`private_{username}`	By default, only the login permission is assigned to this role. However, if there are permissions that need to be allowed to specific users, they can be assigned using this role. Ensure to replace the {username} with that specific user's username.

...

Versions Compared