Feature #4351
closed
Global user permissions need to be delivered to angular pages
Added by Thomas McKay about 11 years ago.
Updated over 6 years ago.
Description
Currently permissions are embedded in individual results objects, however this does not satisfy global or complex permissions for pages.
For example, before there are any activation keys the "create" button needs to be disabled based upon current user's perms.
Another example would be a user viewing an activation key but not having permission to view or edit subscriptions. The subs perms need to be delivered in this case.
- Status changed from New to Assigned
- Assignee set to Thomas McKay
- Assignee changed from Thomas McKay to Walden Raines
- Related to Feature #5217: As a user, I should have CRUD permissions for all entities that are exposed to me. added
- Status changed from Assigned to Duplicate
- Is duplicate of Feature #5503: Available UI interactions should reflect a user's permissions added
- Status changed from Duplicate to New
- Priority changed from High to Normal
This is not an exact duplicate of #5503.
We need to figure out a way to allow more complex, cross resource permissions.
- Tracker changed from Bug to Feature
- Is duplicate of deleted (Feature #5503: Available UI interactions should reflect a user's permissions)
- Related to Feature #5503: Available UI interactions should reflect a user's permissions added
- Status changed from New to Duplicate
- Related to deleted (Feature #5503: Available UI interactions should reflect a user's permissions)
- Is duplicate of Feature #5503: Available UI interactions should reflect a user's permissions added
- Translation missing: en.field_release set to 13
- Translation missing: en.field_release deleted (
13)
- Translation missing: en.field_release set to 166
Also available in: Atom
PDF