Actions
Feature #4351
closedGlobal user permissions need to be delivered to angular pages
Status:
Duplicate
Priority:
Normal
Assignee:
Category:
Web UI
Target version:
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.
Updated by Thomas McKay about 11 years ago
- Status changed from New to Assigned
- Assignee set to Thomas McKay
Updated by Walden Raines almost 11 years ago
- Related to Feature #5217: As a user, I should have CRUD permissions for all entities that are exposed to me. added
Updated by Walden Raines almost 11 years ago
- Is duplicate of Feature #5503: Available UI interactions should reflect a user's permissions added
Updated by Walden Raines almost 11 years ago
- Status changed from Duplicate to New
- Priority changed from High to Normal
Updated by Walden Raines almost 11 years ago
- Is duplicate of deleted (Feature #5503: Available UI interactions should reflect a user's permissions)
Updated by Walden Raines almost 11 years ago
- Related to Feature #5503: Available UI interactions should reflect a user's permissions added
Updated by Walden Raines almost 11 years ago
- Related to deleted (Feature #5503: Available UI interactions should reflect a user's permissions)
Updated by Walden Raines almost 11 years ago
- Is duplicate of Feature #5503: Available UI interactions should reflect a user's permissions added
Actions