Signing in

The tools you'll write in ask you to sign in with SSO, the same sign-in you use for your other work. Signing in proves who you are. It doesn't, by itself, let you do anything in content-sdk.

content-sdk only knows people an administrator has invited, by their email address. The first time you sign in, content-sdk finds your invitation under your email address, as long as SSO has confirmed that address, and connects your SSO sign-in to it. From then on it knows you by your SSO sign-in, so it still finds you if your email address changes. What you can do comes from the roles the administrator gave you, never from SSO.

You can sign in from the top of any page; this step shows what happens when you do. Signing in changes no content, and every other example still shows what every visitor sees.

Try it: sign in with SSO, then look at the roles content-sdk has for you. If nobody invited you, you'll see what you would be told in your tools.

Your first sign-in is recorded: content-sdk notes the day, and adds an entry to its audit log, made by you. Signing in again adds nothing, unless SSO now gives a different name or email address for you, which content-sdk takes and records. If SSO has no name for you, or gives your email address as your name, content-sdk keeps the name you have. A sign-in content-sdk refuses records nothing. The invited staff hold one role, Guest, which allows nothing yet; an administrator can also invite someone with no roles at all. In your tools, an administrator gives you the roles your work needs.