[
https://issues.apache.org/jira/browse/OPENMEETINGS-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prytsepov Andrey reopened OPENMEETINGS-1796:
--------------------------------------------
For this algorithm admin must create group, acess someone as groupadmin after
this groupadmin have access to do something. Many steps. Must be, admin just
once make “manager” and “manager” have access to create many groups and other
accesses that I wrote before in jira. In this schema admin just once but not
always make manager and he no need always do someone as group admin.
Sometimes I need to send email manually, so automatically it is just half of
functionality that needed.
> 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)
