Managing users' sign-in methods

As an administrator, you stay in control of how each member of your organization signs in to Anghello: password, Microsoft (Azure AD / Entra ID), or Google Workspace. At any time, you can review a member's active sign-in methods and remove one — for example, to align an account with your sign-in policy (corporate SSO) or revoke password access.

Audience: Administrators
Application: Admin (app.anghello.co)
Estimated time: 5 minutes

How a member ends up with several sign-in methods

A single account can have several ways to sign in. These methods are added automatically, with no action on your part:

1. The member activated their account with an email and password → they have the "Email / Password" method.
2. Later, they sign in via Microsoft (SSO) using the same email address → that SSO method is automatically linked to their existing account.

As a result, the account holds several methods (for example "Email / Password" + "Microsoft"). This is exactly what you see and can manage on the Members page.

This is standard identity federation behavior: when a member signs in through your SSO provider (Microsoft Entra / Azure AD, Google Workspace) with their work email address, that identity is linked to their existing account instead of creating a new one. It guarantees one account per employee, with no duplicates — simpler access governance and traceability for IT.

Linking only happens when the email address is identical. It is the same account with several ways to sign in — not separate accounts.

Viewing active sign-in methods

1. Open the Members page.
2. The Sign-in column shows, for each member, the methods they can use to sign in:

This column is only visible to organization administrators.

Removing a sign-in method

1. On the member's row, click the ⋮ menu, then Manage sign-in methods.
2. The dialog lists the member's active methods.
3. Click the delete icon 🗑️ next to the method you want to remove.
4. To confirm (the action is irreversible), type the member's email address, then validate.

The method disappears from the list, and the member can no longer use it to sign in.

You can't remove the last method. A member must always keep at least one way to sign in: the delete button is disabled when only one method remains.

Managing your own sign-in methods

If you're an administrator, you can also manage your own methods: open the ⋮ menu on your own row, then Manage sign-in methods. Here too, you can't remove your last method (so you don't lock yourself out).

Frequently asked questions

Which sign-in methods exist?
Email / Password, Google, and Microsoft (Azure).

Does the member lose access if I remove a method?
No — as long as at least one other method remains. For example, removing "Email / Password" from a member who also has Azure SSO still lets them sign in via Azure SSO.

Who can view and manage sign-in methods?
Only organization administrators. Site Managers don't see this information.

Can I change another administrator's methods?
Yes. An administrator can manage any member's methods, including another administrator's. The only exception is the organization owner ("Owner" badge): their sign-in methods can only be changed by themselves.

What happens when I remove the "Email / Password" method?
The member can no longer sign in with a password; they use their other methods (Google, Microsoft). If they need a password again later, they can set a new one themselves via "Forgot password".

Why do I have to retype the email address to confirm removing a method?
Removing a sign-in method is irreversible. Retyping the email address ensures you're acting on the right account.

Updated on: 23/07/2026