[
https://issues.apache.org/jira/browse/OPENMEETINGS-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Solodovnik resolved OPENMEETINGS-1796.
--------------------------------------------
Resolution: Won't Fix
I see no value in creating another role which is very close to admin
Current design is solid.
Admin(s) creates groups
Groups might represent "academic group of student", "department of
organisation" etc.
This is something not very volatile .....
You can create additional admins to modify everything on regular basis
> Need add more control in access rules
> -------------------------------------
>
> Key: OPENMEETINGS-1796
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1796
> Project: Openmeetings
> Issue Type: Improvement
> Components: BuildsAndReleases
> Affects Versions: 4.0.0
> Environment: OM 4.0.0, Windows 10 Professional
> Reporter: Prytsepov Andrey
> Assignee: Maxim Solodovnik
> Priority: Critical
>
> Now we have access groups: soap, admin, dashboard, room, login
> It is not flexible as i need.
> I think need to add user group "managers".
> Admin have all rights to OM, but it is need to give some users rights to
> organize webinars without admin help.
> Admin musn't give access more than need to people who organize webinars, but
> in this case admin must waste his time on tasks that he mustn't do.
> As i think "managers" must have access to: create/delete users but not
> create/delete admins, create/delete rooms, create/delete groups, send email
> from OM, view/delete/replace records, connections(drop users but not admin).
> Another options they must have like other default users.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
