User Story #203 (closed)
Opened 18 years ago
Closed 14 years ago
Permissions should be applicable to an entire hierarchy.
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | minor | Milestone: | OMERO-Beta4.2 |
| Component: | Security | Keywords: | hierarchies, permissions |
| Cc: | jburel | Story Points: | n.a. |
| Sprint: | n.a. | Importance: | n.a. |
| Total Remaining Time: | n.a. | Estimated Remaining Time: | n.a. |
Description
If it is possible to define the semantics, Permission definitions should (optionally) be applied to an entire hierarchy (P/D/I or CG/C/I). The assumption being that if a user wants to make a Project unreadable, that the Datasets and Images should be equally invisible.
This may be a UI issue, i.e. offering the right tick boxes.
Change History (2)
comment:1 Changed 18 years ago by jmoore
- Milestone changed from 3.0-M3 to GatherReqs
comment:2 Changed 14 years ago by jmoore
- Milestone changed from GatherReqs to OMERO-Beta4.2
- Resolution set to fixed
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
This ticket is covered by the implementation of #1434. Rather than applying to an entire hierarchy, a whole group will have its permissions changed.