New "Full Access" User Role and Enhanced Multi-Tenancy Tiers

Hello,

I would like to submit a feature request for a new user permission role that falls between the current Group Administrator and Group Viewer roles.

Most of my customers are Service Providers, VARs, or Agents. They frequently need to grant their end customers the ability to manage their own configurations and make changes without giving them the power to create or modify other users.

Currently, the Group Administrator role is too broad for many end-user scenarios because it allows for user management. The Group Viewer role, on the other hand, is too restrictive for customers who need to be “hands-on” with their hardware. A “Full Access” or “Operator” role that excludes user management would be the ideal middle ground. Please let me know if this role exists and if I just may have simply overlooked the configuration.

Additionally, I would like to request support for deeper multi-tenancy tiers (Parent/Child accounts). Currently, creating separate Organizations or manually adding users to multiple Groups adds significant complexity to monitoring, notifications, and general account maintenance. Having a traditional multi-tenant hierarchy where a parent account can seamlessly manage multiple nested child accounts. I think this would greatly simplify the workflow for partners managing a large client base.

Thank you for considering these improvements!

5 Likes

For the second point, adding accounts to multiple organisations works well, you can just select the org you want in the dropdown.

We manage our user adding/disabling automatically with some automation that monitors a group in Entra ID via Microsoft Graph, and then calls the IC2 API to check each organisation and add/remove users.

3 Likes

Thank you for feedback! This may be something we consider. Although there is something to be said for standing up and maintaining your own infrastructure vs it being built in.

1 Like

We’ve had to move to building our own IC2 management layer via IC2 API due to the limitation in RBAC capabilities with Peplink ID.

2 Likes

Can you elaborate more on how you managed this?