Admin dashboard

Sign-in & domains

Prove the email domains your organization owns, and let its people sign in with your own identity provider, by SAML or OIDC.

Who can use itAdmins and owners
Your own sign-in needsA verified domain
OwnersCan always sign in another way
In the admin dashboard: Sign-in & domains Open the dashboard
On this page

Domains#

List the email domains your organization owns, and prove each one with a DNS TXT record. A verified domain is needed before you can set up your own sign-in.

FeatureDescriptionDefault
Add a domain

A domain your organization owns, like example.com. Public mail domains such as gmail.com can’t be added, and neither can a domain another organization has verified.

—
Add domain

Adds the domain, and shows the TXT record to add for it at your DNS provider.

—
Name

The TXT record’s name, to copy. Some DNS providers want only the part before your domain.

—
Value

The TXT record’s value, to copy.

—
Verify

Looks for the TXT record. Once it’s there, the domain is marked Verified, with the date; until then, it says the record isn’t there yet. DNS changes can take a while to show.

—
Remove

Removes the domain. Press it twice to confirm. People with an address there are no longer sent to your own sign-in. While your own sign-in is set up, its last verified domain can’t be removed: add another first, or remove the sign-in.

—

Organization sign-in#

Let your people sign in with your organization’s own identity provider, by SAML or OIDC. Until you set one up, they sign in with their Ambient Assist AI account.

For your identity provider#

Whoever sets up Ambient Assist AI in your identity provider needs these values. Each has a Copy button.

FeatureDescriptionDefault
SAML reply (ACS) URL

Where your identity provider sends people back after signing them in by SAML.

—
SAML entity ID (audience)

The audience your identity provider signs people in for, by SAML.

—
OIDC redirect URL

Where your identity provider sends people back after signing them in by OIDC. Add it as an allowed redirect.

—

Set up a sign-in#

Choose SAML or OIDC, give your identity provider’s details, and save. The form starts on SAML. If you have no verified domain yet, it asks you to verify one first. Once a sign-in is set up, this part is called Replace the sign-in.

FeatureDescriptionDefault
SAML

For an identity provider that signs people in by SAML. Give its metadata URL, or paste its metadata XML.

—
Metadata URL

SAML: the address of your identity provider’s metadata.

—
Or the metadata XML

SAML: the metadata itself, pasted, if you have no address for it. When you give both, the address is used.

—
Email attribute (optional)

SAML: the attribute that carries each person’s email address. Leave it empty for the usual email address claim.

The usual email claim
OIDC

For an identity provider that signs people in by OIDC. Give its issuer URL, client ID and client secret.

—
Issuer URL

OIDC: your identity provider’s issuer address.

—
Client ID

OIDC: the client ID your identity provider gave for Ambient Assist AI.

—
Client secret

OIDC: that client’s secret. It’s never shown again once saved, and every save of an OIDC sign-in needs it.

—
Email claim (optional)

OIDC: the claim that carries each person’s email address. Leave it empty for “email”.

email
Save sign-in

Saves your organization’s sign-in. From then on, people with an address at one of your verified domains are sent to it when they sign in.

—
Replace sign-in

Takes the place of Save sign-in once a sign-in is set up, and saves new details over it. If the new details change who signs people in (its kind, metadata, issuer, client ID or email setting), members who connected their account to the old sign-in are disconnected, and connect again from their account page.

—

Current sign-in#

Once a sign-in is set up, this shows its kind, its issuer and client ID or its metadata, and when it was set up.

FeatureDescriptionDefault
Remove sign-in

Removes your organization’s own sign-in. Press it twice to confirm. Nobody can sign in with it any more, members who connected their account to it are disconnected, and Require this sign-in for everyone but owners turns off.

—

Require this sign-in#

You choose whether people may still sign in other ways once your own sign-in is set up.

FeatureDescriptionDefault
Require this sign-in for everyone but owners

When Require this sign-in for everyone but owners is enabled, everyone but your owners has to use your organization’s sign-in, on the web and to enroll a device. Anyone signed in another way, admins included, is asked to sign in with it first. Owners can always sign in another way, so a broken setup can’t lock everyone out. You can turn it on once a sign-in is set up.

Off

Who signs in with it#

Once your organization’s sign-in is set up:

  • People with an address at one of your verified domains are sent to it when they sign in to Ambient Assist AI.
  • Anyone it signs in who isn’t in your organization yet joins as a Member, while there’s a free seat. The audit log says they joined through the organization’s own sign-in.
  • Members who already have an Ambient Assist AI account can connect it to your sign-in from their account page, with Connect organization sign-in.
  • Someone you removed, or who left, isn’t let back in through it, however they first joined: invite them back instead. Their account page says their membership ended, and to ask you for an invitation. Taken through your sign-in, the invitation brings back the same membership, with its data, and connects their sign-in to it. Removing someone here doesn’t remove them from your identity provider.
  • It knows someone you removed by the sign-in they joined with or connected, or by their email address. Someone at another address, even at one of your domains, is someone else, and joins as a new member.
  • Members: inviting people, and removing them.
  • Overview: how your people sign in, at a glance.
  • Audit log: domains, sign-in changes, and people joining through it.
  • Your account: where members connect their account to your sign-in.
  • Roles and permissions: why owners can always sign in another way.
Esc
↑ ↓ to moveEnter to open