Orgs and Locs Main Bar Dropdown visible with a org filter role in place

Problem:
Orgs and Locations top drop down menus are visible even with filter set to limit them.

Expected outcome:
Org and Locs are not visible when a filter is in place.

Foreman and Proxy versions:

rubygem-hammer_cli_foreman_ssh-0.0.3-1.el9.noarch
rubygem-hammer_cli_foreman_salt-0.1.0-2.el9.noarch
rubygem-hammer_cli_foreman_kubevirt-0.2.0-1.fm3_11.el9.noarch
foreman-obsolete-packages-1.10-1.el9.noarch
rubygem-foreman_statistics-2.1.0-3.fm3_11.el9.noarch
rubygem-foreman_maintain-1.10.3-1.el9.noarch
foreman-release-3.15.0-1.el9.noarch
rubygem-hammer_cli_foreman-3.15.0-1.el9.noarch
rubygem-hammer_cli_foreman_tasks-0.0.22-1.fm3_15.el9.noarch
foreman-selinux-3.15.0-1.el9.noarch
foreman-3.15.0-1.el9.noarch
rubygem-foreman-tasks-11.0.0-1.fm3_15.el9.noarch
rubygem-foreman_remote_execution-16.0.3-1.fm3_15.el9.noarch
rubygem-foreman_salt-17.0.2-1.fm3_15.el9.noarch
foreman-dynflow-sidekiq-3.15.0-1.el9.noarch
foreman-libvirt-3.15.0-1.el9.noarch
foreman-ovirt-3.15.0-1.el9.noarch
foreman-postgresql-3.15.0-1.el9.noarch
foreman-redis-3.15.0-1.el9.noarch
foreman-service-3.15.0-1.el9.noarch
foreman-vmware-3.15.0-1.el9.noarch
rubygem-foreman_kubevirt-0.4.1-1.fm3_15.el9.noarch
rubygem-foreman_puppet-8.1.1-1.fm3_15.el9.noarch
rubygem-foreman_templates-10.0.8-1.fm3_15.el9.noarch
rubygem-foreman_vault-3.0.0-1.fm3_15.el9.noarch
rubygem-hammer_cli_foreman_remote_execution-0.3.2-1.fm3_15.el9.noarch
foreman-cli-3.15.0-1.el9.noarch
rubygem-hammer_cli_foreman_puppet-0.1.1-1.fm3_15.el9.noarch
foreman-proxy-3.15.0-1.el9.noarch
foreman-installer-3.15.0-1.el9.noarch

When applying a filter in a role, and limiting it to name = org name it does indeed hide it from Orgs when navigating to Admin → Orgs. However, it is still visible on the drop down menu from the top main bar. The way to remove visibility from the top bars seems to be to uncheck All Users from the Org settings. While this may make sense, this means when having to manage some 300+ Orgs with some 3,000+ users, an admin would need to individually add each user to each org. This isnt sustainable or manageable.

Is there a better way to do this? Are we doing something wrong?

At the moment probably not. I do however have a RFC which could still be relevant in this situation, even though it does not propose exactly what you ask for here.

1 Like