Esta página aún no está traducida.

Company sign-in (single sign-on)

This page is for an organization's owners and admins, and for anyone deciding on a plan. It explains what company sign-in does for your people, how you prove your email domains, and what requiring it means.

What single sign-on changes for your people

Plans On Enterprise

Single sign-on means your people sign in to instruction.md with the account they already use for work. That account lives in your company's identity provider: the service your IT team uses for work sign-ins, such as Okta, Microsoft Entra ID or Google Workspace.

With it on, this is what your people see:

  • They type their work address. On the sign-in page, someone at your company types their work email address. instruction.md sends them to your company's sign-in page.
  • They need no passkey. Your company's sign-in vouches for them. They don't need a passkey for instruction.md.
  • Their account is made for them. The first time someone with no instruction.md account signs in through your company, their account is made. Someone who already has an account at that address signs in to it once, their usual way, to link the two.
  • Joining your organization is separate. Signing in doesn't make someone a member of your organization. Invite them, or bring them in from your company's directory. See Bring in your company's people.
  • People outside your domains are not affected. A guest or a partner with another address signs in as before, with a passkey. See Signing in.

Company sign-in changes how people sign in. It doesn't change what they may do. Their role in your organization and in each workspace stays the same. See Invite people and choose their roles.

Who does what

  • Owners connect your company's identity provider, change it or remove it, and turn sign-in through it on or off. Only owners can require it.
  • Admins see these settings, and add and prove your email domains.
  • Every owner is told when the identity provider or its switches change, and when a domain is verified or removed, whoever did it. Each change also shows in your organization's activity log.

When it is available, it will be in Developer ▸ Single sign-on. Developer shows in the side bar only when Developer mode is on, in Settings ▸ General. On a plan without single sign-on, the page shows Sign in with your company's account with an Enterprise badge.

If instruction.md's team set up your company's sign-in for you, the page says Your people sign in through your provider's name, and that you write to us to change it.

What connecting takes

An owner picks how your identity provider signs people in, under How it signs people in: OpenID Connect or SAML. Your IT team knows which one yours uses. The page then shows an address to copy into your identity provider, under First, in your identity provider. Your IT team adds instruction.md there as an app and gives back the details the page asks for, under Then, what it gave you. Test and save checks that your identity provider answers before anything is saved.

Proving a domain, in plain words

A domain is the part of an email address after the @, such as acme.com. Before anyone is sent to your company's sign-in, you prove that the domain is yours. This stops anyone else from sending your people to a sign-in page they don't control.

You prove it by adding one line to your domain's settings, at the company where you bought or manage the domain. That line is called a TXT record. Your IT team usually adds it.

How it goes:

  1. An owner or admin adds the domain in Developer ▸ Domains, under Add a domain. Developer shows once Developer mode is on, as above.
  2. The page shows a TXT record, with a Name (host) and a Value to copy. The domain shows Waiting.
  3. Someone adds that record at your domain's provider. It can take a few minutes to appear.
  4. Press Check now. When the record is found, the domain shows Verified.

Some things to know:

  • A proven domain is yours alone here. No other organization can prove it while you hold it.
  • Public mail services can't be added. Addresses such as gmail.com belong to everyone, so they can't route anyone's sign-in.
  • Keep the record. instruction.md checks it about every hour. If it is missing three checks in a row, the domain is no longer verified. Your people at that domain are then no longer sent to your company's sign-in, and your owners are told why.
  • A domain does more than sign-in. Apps your organization registers on a proven domain show as verified. The domain's row says what uses it, such as Used by single sign-on.

Removing a domain that your people sign in through is for owners only. They are asked first, because those people stop being sent to your company's sign-in at once.

Turning it on

Once your identity provider is connected and at least one domain is verified, an owner turns on the switch named after it, such as Sign in through Okta. The row then says which domains it covers, such as "People at acme.com sign in with their company account".

Until both are in place, the switch can't be turned on. The row says what is missing: Connect your identity provider first, or Verify an email domain first.

Turning it off again means people sign in as before. Removing your identity provider keeps everyone's account and keeps your domains verified. AI apps stop connecting through it.

Requiring it

Turning it on sends your people to your company's sign-in. Requiring it goes one step further: people at your verified domains can sign in only through your company. Once sign-in through your provider is on, a Require it row shows under it, and owners decide with its Require single sign-on switch. Admins see the row, with Owners decide this.

When an owner requires it:

  • People at your domains who are signed in some other way are signed out at once. They sign in again through your company.
  • From then on, a passkey doesn't sign them in here. Your company's sign-in does.

Keep one owner outside your domains

If your identity provider is down, nobody at your domains can sign in. So instruction.md asks you to keep at least one owner whose address is not at those domains. That owner can still sign in with a passkey and undo the change.

Without such an owner, requiring single sign-on is refused with "keep one owner whose address isn't at these domains, so someone can still sign in if your identity provider fails". Invite a second owner with another address first. See Change a role.

If your company's sign-in stops answering

For an identity provider connected with OpenID Connect, instruction.md checks once a day that its sign-in address can still be found. If it can't be found three days in a row, sign-in through it is turned off, and every owner is told. Your people then sign in as they did before. If someone has no other way in, see Lost your passkey?.

AI apps and your company's sign-in

Plans On Enterprise

With company sign-in on, an owner can also turn on Let Claude connect your people automatically. Someone at your company who uses Claude is then connected to instruction.md as themselves, with no extra sign-in screen. Who may do this is decided in your identity provider, not in instruction.md.

Sign-in through your identity provider must be on first. It also needs a provider connected with OpenID Connect, such as Okta. One connected with SAML can't vouch for your people to Claude, and the page says so. Your IT team then enters a few values from the page in your identity provider, under What your Okta admin enters (the page uses your provider's name). This is not available yet either. How you connect an AI app yourself today is on Connect Claude or ChatGPT.

Questions

Which plan has company sign-in?

Plans On Enterprise

On other plans, Developer ▸ Single sign-on shows Sign in with your company's account with an Enterprise badge instead of the settings. See Plans, limits and billing.

Do my people lose their work when we turn it on?

No. Their accounts, instructions and roles stay. Only the way they sign in changes. Removing the identity provider later keeps their accounts too.

Can a guest from another company still sign in?

Yes. Company sign-in covers only addresses at your verified domains. Everyone else signs in with a passkey, as before. See Signing in.

What if our identity provider is down?

People at your domains can't sign in until it is back. An owner whose address is outside those domains can still sign in and turn the requirement off. That is why instruction.md asks you to keep one.

Can I prove a domain now?

Yes. Developer ▸ Domains works today, and a verified domain stays verified while you keep its record. When company sign-in arrives, your verified domains are ready for it.

For IT

The technical setup, the record's exact format and how domains are checked are in Domains, for developers.

Last checked against the product:

Was this page helpful? Report a problem