When configuring (CRM) roles a minimum of one manage entityID needs to be configured. However, some (CRM) roles allow access to many single-tennant instances of the same application. E.g. SURFeduhub-beheerder would allow access to 16 single-tennant manage entityID's.
This in itself isn't a problem, but the invitation for the role tells the user that they will have access to 16 applications of which they don't recognise 15 when they accept the role. Apart from not recognising the tennant, it also clutters the invitation mail and the welcome landingpage.
When configuring (CRM) roles a minimum of one manage entityID needs to be configured. However, some (CRM) roles allow access to many single-tennant instances of the same application. E.g. SURFeduhub-beheerder would allow access to 16 single-tennant manage entityID's.
This in itself isn't a problem, but the invitation for the role tells the user that they will have access to 16 applications of which they don't recognise 15 when they accept the role. Apart from not recognising the tennant, it also clutters the invitation mail and the welcome landingpage.