• Stay ahead with

    Auto-provisioning of users

    Authway supports auto provisioning of users, which allows a smoother user experience, better efficiency and improved security.

    Illustration of how Authway handels auto-provisioning of users.
  • What is Auto Provisioning of Users?

    Automated provisioning of users handles the complete life-cycle of a user, including creating, maintaining and removing a user.

    Since Authway often is used in cooperation between organisations, it enables auto-provisioning of users without setting up complex integrations. Because there are no integrations, Authway will create and maintain users just-in-time when a user signs in.

    Auto-provisioning will not trigger the removal of users. Instead, Authway supports different clean-up jobs that remove users who haven’t signed in for a pre-defined time.

    Let’s take a closer look at these stages.

    Illustration explaining how auto provisioning provides a smoother user experience, better efficiency and improved security.
  • First stage

    Creation of users

    When a new user tries to sign in through Authway, it will identify the organisation by the e-mail address domain and automatically redirect the user to a registered sign-in alternative for that organisation.

    The user will perform their regular sign-in, and the user will be automatically created in Authway by that sign-in.

    Among the information from the sign-in, the user groups from their home directory will also be included, which will be mapped against the groups in Authway, resulting in a user with the correct permissions.

    Authway sign-in interface on top of a collage of people using a computer.
  • Second stage

    Maintenance of users

    Just as during the creation above, each new sign-in will include user information that will be used to keep the user up to date in Authway. For example, a name or e-mail address change will be automatically synchronized during the sign-in.

    Of course, the user groups from the home directory will be mapped at each sign-in, resulting in correct permissions for the user.

    Illustration of a maintenance worker servicing a user portrait.
  • Last stage

    Removal of users

    Since there are no integration needs, Authway will not be notified if the user is removed from their home directory. Still, if the user tries to sign in again, this will not be possible since a successful sign-in in their organisation directory is required.

    The user will eventually be removed automatically by Authway clean-up jobs.

    Illustration of users being removed.

Benefits of Auto Provisioning

We consider auto-provisioning of users to be THE way to cooperate digitally between organisations. Authway support moves beyond single-sign-on as it takes care of the complete life cycle.

 

  • Smoother user experience

Today, it is way too common that users are forced to create new accounts for the digital services they are supposed to use from suppliers or as customers. This will result in a cumbersome start, often with several required steps, and still, the only goal for the user to be able to consume the service. It is also prevalent that an existing user in their organisation has to add and invite the user before it is possible to create the account.

 

  • Better efficiency

By automating the complete user life-cycle, including access management, auto-provisioning significantly increases efficiency for your organisation and, more importantly, for the organisations that are supposed to use your services. Authway removes many manual moments, decreases support, and enables each organisation to manage its users in one place: their home directory, where they should be managed.

 

  • Improved security

Security is improved in many ways by using auto-provisioning, and one of the most important is that the user does not need to manage yet another password. Instead, they will use their existing business sign-in, which is typically better protected. When an organisation can manage access permission by ensuring a user belongs to groups in their directory, the risk of a user getting wrong permissions is heavily decreased.

  • Do I need SCIM to auto-provision users with Authway?

  • Can auto-provisioning my users help with auditing and compliance?

  • What tier of Authway do i need to get access to auto-provisioning?

  • Does Authway support deprovisioning of users?

Explore more topics