Although it can be implemented quickly for individual services, consistent management of identities and access (Identity & Access Management, also known as IDM or IAM) poses a number of technical challenges as the number of users, services and providers increases: different repositories must be connected, roles described, suitable access authorisations defined and implemented in a technically sound manner. In addition to experience, this requires a specialised system to ensure that you don't lose track: a trustworthy, open and scalable IAM that combines all services in a central location.
It's not always about self-service scenarios. Access to critical services will continue to be assigned by hand - but to existing identities. IAM supports this and uses workflows to make it clear why a user has access to which resource, and who authorised them to do so and for what purpose. IAM is therefore much more than ‘single sign-on’ and requires a consistent organisational process in addition to suitable systems.