Currently, the Sitemaps in Model-driven Apps are static. In scenarios where multiple teams or security roles exist, it often becomes necessary to create separate apps to accommodate different access requirements.

It would be highly beneficial if Sitemaps could be configured based on Security Roles. This feature would allow administrators to define which areas or entities (e.g., Contacts, Accounts) are visible in the Sitemap for specific roles.

For example:

• A user without access to Contacts would not see the Contacts section in the Sitemap.

Key Benefits:

• Reduce the need to create and maintain multiple apps for different roles.
• Enhance user experience by showing only relevant sections in the Sitemap.
• Improve security and clarity by ensuring users only see what they have access to.

Thank you for considering this improvement!