scope of the contacts menu is too broad

For a Nextcloud instance with a lot of users (e.g. from a user directory like LDAP) the scope of the contacts menu may seem way too broad as on first click it tries to load all users of that instance and shows the first 25 entries instead of just real "contacts".
This may take a long while depending on the LDAP connection and within an organization of >10.000 users the first 25 alphabetically sorted users may just seem random people, not contacts.
This behaviour might also be especially confusing when the contacts app is not enabled.

So it would be great if there was a way to disable the contacts menu or alternatively to at least limit it to users I really had interactions with, like file sharing or adding to the buddy list of the chat app, etc.

The issue names no files, tests, or entry points. Start by locating the contacts menu implementation and the query that loads users, then review how contacts, sharing, and chat interactions are represented. Done should mean the chosen scope is explicit, avoids loading an entire large directory, and is covered by a reproducible test or documented behavior.