No shell: you are not in an org yet.

Acme Labs uses company sign-in

The org turned on SAML and switched the other routes off. That is Acme Labs' setting rather than ours, and it applies to everybody in Acme Labs — including the people who set it up.

▤
Continue with Okta
Acme Labs' identity provider. You may already be signed in to it, in which case this is one click and no typing.
What this changed for you. The password you had here stops working, and getting back in when something goes wrong is your IT desk's job rather than ours — they hold the account now. Nothing you built moved, and nothing about the other orgs you are in changed.
You are on auth.kordin.io and you are about to leave it for your own provider. Coming back here is what completes the sign-in. Wrong org? Pick a different one in October each person is in one organization (30.5) — each sets its own policy.
Kordin Neo

Okta does not have you

Acme Labs' identity provider signed you in and then told us its directory does not place you in this org. That is a directory question rather than a Kordin one — we asked, and were told no.

Nothing was created and nothing was removed. Retrying will produce the same answer until somebody at Acme Labs changes what the directory says; that person is your IT desk, not an Owner here.

Try againSign in to another orgin October each person is in one organization (30.5)
you can fix this

Your provider signed you in and the org has no role for the directory memberships you have. The mapping is set by the org, so an owner has to add one — nothing here can be retried.

Reference f842b91f6fceGet help ›
Show the code FEDERATION_GROUP_NOT_MAPPED proposed code
Kordin Neo