Once a repository is connected to Nerdio, all applications are visible within the catalog. This means an admin within Nerdio could assign any application if they have sufficient rights. Some applications are department specific or out of scope for some admins.
I've had a request from a customer to provide additional filtering on applications within Nerdio. The easiest way I could think to do this would be to make application visibility within the catalog subject to workspace assignment in RBAC but some clients also have everything in one workspace which would negate this.
Perhaps additional filtering objects could be introduced and assignable from RBAC roles in the form of deployment groups? Applications could be grouped and those groups could be assigned to specific users or groups authorized to deploy them.
Comments (0 comments)