Sign-in errors

These errors happen before a person reaches their workspaces. For the desktop app on a restricted network, see Desktop app errors. For a person who signs in but cannot see a workspace or skill, see Workspace access errors.

​

Invitation cannot be sent or accepted

The invite dialog warns that nobody can join the organization, or an invited person cannot join.

​

Cause

The organization’s Who can join policy is Closed. While it is Closed, nobody joins the organization, including by invitation.

​

Solution

An organization admin changes the policy.

1. Open Settings → Security → Domains.
2. Change Who can join to a policy that admits the people you invite. See Manage company domains.
3. Resend the invitation from Pending invitations. See Invite members.

If the dialog says No free seats left instead, the organization has no seat for the invitation. See Manage billing.

---

​

Company SSO locks people out

After a change to company SSO, people cannot sign in, or the sign-in test fails.

​

Cause

The identity provider connection is inactive or misconfigured while the sign-in policy is Required. An inactive connection does not restore other sign-in methods automatically.

​

Solution

An organization admin who is still signed in repairs the provider.

1. Open Settings → Security → Authentication.
2. Select Manage provider, fix the configuration, then select Test again.
3. If the provider cannot be fixed yet, choose an available fallback policy.

If no administrator can sign in, contact Atlan support. See Configure company SSO.