Support more than 20 organizations in Organization Picker

Feedback
1

I work on a multi-tenant service that allows users to be members of multiple organizations. External users are typically only members of a small number of organizations, so the current Organization Picker works great for them – either they bypass the picker to log in to their single organization, or they select from a short list.

Internal users, on the other hand, often have access to well over 100 organizations. For example, our support staff needs to log in to organizations to understand problems reported by the external users. For them the current Organization Picker is inadequate, since it is only capable of displaying 20 organizations.

My suggestion is that the Organization Picker become a searchable drop-down list once the number of organizations exceeds 20, and include all of a user’s organizations. Typing a small part of the organization name to filter the list would allow them to easily select the organization they want and the drop-down control would occupy far less real estate on the form than 100+ individual buttons.

2

For what is worth, I have exactly the same use case, thus the same problem, any idea when this will be implemented?

1 Like
3

Ditto, the dashboard my team has built and supports needs support for more than 20 orgs in the picker. It should be rather easy to impl. and I’m not quite sure how this was released without pagination-like support.

1 Like
4

Hi all, until such a time as support for more than 20 orgs is added to the organization picker, please consider using the MGMT API to fetch organizations from within your application. You can fetch 50 orgs per page so pagination will be necessary. You may also consider using an Organization Switcher in your internal app similar to what is demonstrated in the UI Components: Auth0 Lab - UI Components

5

Agreed here. WE have implemented a TEA tool that helps keep the total amount at any given time in check (we have many thousands of tenants/clients) while also being a good security practice. However, even with aggressive expiry periods, 20 is limiting for team roles such as a support agent.
Some sort of filter/search would be greatly simplifying.