Shared identity

The Shared Identity page (route /shared-identity) enables Agilicus-managed upstream identity providers. These are public sign-in providers (Apple, Google, Linkedin, Yahoo, and Microsoft) that Agilicus operates for you, so you can offer single sign-on to your users with no third-party application registration.

Purpose

Shared identity is the simplest identity option in the portal. Agilicus runs the upstream provider integration for you, so enabling a provider is a single checkbox: your users then see that provider’s sign-in button on your organisation’s issuer page. The issuer URL shown at the top of the page (for example https://auth.dbt.agilicus.cloud) is the federation point your users sign in to.

The platform manages the following providers:

Sign in with Apple for Apple IDs
Sign in with Google for Google Workplace (corporate) or Gmail (personal) accounts
Sign in with Linkedin
Sign in with Yahoo
Sign in with Microsoft for Office 365, Azure, or personal Microsoft accounts

Why use it

Offer familiar single sign-on buttons on the sign-in page without registering applications with each provider.
Let users sign in with identities they already have, so there are no shadow accounts to manage (see Identity and authentication).
Get going quickly: this is the zero-configuration path compared with Custom Identity.

When to use it

During initial setup, when you want public or consumer identity providers rather than a corporate directory.
When you want to add or remove a sign-in option quickly.
When you use Microsoft and want to control the account-selection behaviour.

Prerequisite: permission to administer issuers (an owner or administrator role). The page shows a no permissions message otherwise. Enabling a provider here only makes the identifier available; you still grant authorisation to users in the Access section.

How to use it

Open Authentication > Shared Identity from the left navigation.
Tick the checkboxes for the providers you want to offer. Each change saves immediately and updates your issuer asynchronously.

For Microsoft, optionally tick For users with multiple microsoft accounts, force them to select a microsoft account explicitly so a user with more than one Microsoft account is always asked which one to use.
Confirm the change after a few seconds by reloading the page. The providers you enable appear on your organisation’s sign-in page.

Fields and controls reference

Control	Purpose	Required	Default	Notes
Issuer	The sign-in URL that federates the managed providers	Read-only	n/a	Your organisation’s issuer URI
Sign in with Apple	Toggles Apple ID as a sign-in provider	No	Off
Sign in with Google	Toggles Google (Workplace or Gmail) as a sign-in provider	No	On	Corporate or personal accounts
Sign in with Linkedin	Toggles Linkedin as a sign-in provider	No	Off
Sign in with Yahoo	Toggles Yahoo as a sign-in provider	No	Off
Sign in with Microsoft	Toggles Microsoft (Office 365, Azure, or personal) as a sign-in provider	No	On
Force Microsoft account selection	Requires users with multiple Microsoft accounts to choose one explicitly	No	Off	Only active when Microsoft is enabled

Dialogs and popups

There are no dialogs on this screen. Configuration is entirely checkbox-based. Upstream group mappings and user identity management belong to the other identity screens: see the row actions on Custom Identity and Onsite Identity, and user identity under Users.

Configuration versus diagnostics versus confirmation

Configuration: enabling and disabling the managed providers, and the Microsoft account-selection option.
Diagnostics: the issuer URL is informational; there are no live diagnostic counters on this screen. Provider health appears on the Authentication Overview.
Confirmation: there are no destructive actions. Disabling a provider takes effect immediately; users who only had that provider will not be able to sign in until you enable it again or give them another provider.

Pagination and async behaviour

There is no table on this screen, so no pagination applies.
Provider changes apply asynchronously: after toggling a checkbox, wait a few seconds and reload to confirm. Propagation to the live sign-in page can take a little longer.

Troubleshooting

The provider I enabled does not appear on the sign-in page: wait for propagation, reload, and confirm the checkbox is still ticked after the page reloads.
Users with multiple Microsoft accounts are not asked to choose: enable the force them to select a microsoft account explicitly option.
A user cannot sign in with a provider: confirm the provider is enabled here and check the sign-in attempts in the authentication audit.
I need more control than a shared provider offers: register your own provider under Custom Identity.