Lifecycle Permission Transition
- Former user (Deleted)
When assets move from one state to another in their lifecycle, a permission transition will take place. The permission transitions together with the registry resource permissions available at each state in the lifecycle is as follows:
Action | Initial State | New State | private_{author} | reviewer | Internal/everyone |
|---|---|---|---|---|---|
Create | Initial | Created | +add | Â | -add |
Submit | Created | In-Review | -add | +add | Â |
Reject | In-Review | Rejected | +add | -add | Â |
Re-Submit | Rejected | In-Review | -add | +add | Â |
Approve | In-Review | Approved | +add | -add | Â |
Publish | Approved | Published | +add | Â | Â |
Unpublished | Published | Unpublished | +add +authorize | Â | Â |
Publish | Unpublished | Published | +add +authorize | Â | Â |
Deprecate | Publish | Deprecated | +add +authorize | Â | Â |
Retire | Deprecated | Retired | +delete | Â | Â |
| Deprecate | Unpublished | Deprecated | +add | Â | Â |
- Anonymous users can be given permission to access ES assets by specifying +get for the
system/wso2.anonymous.rolerole. - Users who have logged into ES can be given permission to access ES assets by specifying +get for the
Internal/everyonerole.