Ticket #230 (Nouveau Amélioration)
Management of config-specific groups
| Reported by: | gdelannay | Owned by: | |
|---|---|---|---|
| Priority: | Haute | Milestone: | PloneMeeting / HubSessions unplanned |
| Component: | Produit PloneMeeting | Severity: | Non bloquant |
| Keywords: | Cc: |
Description
At present, management of groups and roles is shared by all meeting configurations. For the "communes" use case, it is a problem. So we must refine the PloneMeeting? roles/group model to allow users have different roles in different meeting configs.
Change History
comment:1 Changed 2 years ago by gdelannay
- Milestone changed from PloneMeeting 1.3 to PloneMeeting 1.5
comment:2 Changed 2 years ago by gdelannay
- Milestone changed from PloneMeeting 1.5 to PloneMeeting 1.6
comment:3 Changed 2 years ago by gdelannay
We could also define categories that are specific to a group (global or specific to a meeting-config).
Note: See
TracTickets for help on using
tickets.
