Incontrol2 - permissions

Current the Role choices are:

Group Administrator: Group administrators have full access to the group. They can view the dashboard for this group, reports, settings, and device details. In addition, they can also make configuration changes. However, they cannot access other groups in your organization or social user data.

Group Viewer: Group viewers can view the dashboard, reports, device details, and some settings for this group. However, they have no editing ability, and they cannot access other groups in your organization.

Group Dashboard Viewer: Dashboard viewers can only see the dashboard for this group. They cannot see reports, settings, or device details. They have no editing capability, and they cannot access other groups in your organization.

Captive Portal Administrator: Captive Portal Administrators have access to the Captive Portal section in this group only. They also have read and deletion right on social user data.

Captive Portal Report Viewer: Captive Portal Report Viewers have access to the Captive Portal Reports in this group only. They also have read access right on social user data.

InTouch User: InTouch users have InTouch access to client devices over TCP/IP or devices’ serial ports.

Fleet Manager: Fleet Managers have access to the map on this group’s dashboard page only.

Can you add an option or role that allow the Organizations Admin to choices its role could have or not have. right now the canned role choice is the group user has all privileges or none.

In my case, I am using PepVPN’s with a balance 710, and users whose defined job function is to enable the PepVPN connection transfer data and disable the PepVPN. Have two concerns:
to achieve this behavior all the user in the group are group admin (as group viewers, they do not have access to Speedfusion VPN configuration) therefore:

  1. enabling and disabling PepVPN’s ONLY, no configuration, at a user level only, so the user would be group viewer with the additional PepVPN on/off access

  2. Prior version allow for cross group PepVPN connections and later was updated/changed to not allow. As an administer, this new behavior created a security risk, because now the group admin, which would be group viewer user with limited access to behaviors dictated by the organizations admin, have access to the head end router (Balance 710), trying to mitigate the risk to the network and devices and access is the goal, when I could [lace the Balance 710 in another group not access by the Group only the Organization, this provided a level of security. So could this be an OPTION, not change, to bring back