As of today, inSided’s custom user roles are meant to increase a user’s visibility/engagement. Our use case is different: When a user joins our community, we give them full access to all pages in the Community - Ideas, Product Updates, Groups, Events, Forums, etc. The majority of our customers want full access.
But a small number of our customers don’t want their employees to view a few certain sections of our Community. So we would like to auto-assign (via Zapier) some custom user roles to these customers so that their viewing permissions are limited. This would require Custom User Roles to override whatever primary user role a member has.
As of now, primary role permissions override custom role permissions and we cannot do this.
The other option would be for us to create new primary roles so that we could create additional primary roles with limited permissions. We could then use zapier to assign some customers to a limited primary role and some customers to a full primary role. This would be easier.
I understand that we could edit the Registered User primary role so that it’s permissions starts off as limited, and then assign a custom user role that increases permissions. But this would require us to create hundreds of “Zaps” through Zapier in order to adequately assign the custom user role to 99% of our customers who should have full access to the community. This would cost us more more money through Zapier and we’d always having to add more zaps every time we get a new customer in our BoB. Instead, we just want to be able to limit a small select group of people via a limited primary role (or limited custom role that overrides the primary role).
This is critical for us and our Community.