Signing in: identity, and nothing else
Signing in with a provider proves who you are — that is all. Sarcio reads your email and name to match you to a workspace, never a password, and never any access to your code, files, or repositories. The token used to read your identity is discarded on the spot; only a first-party session cookie remains.
Sign in with your Google account.
| Scope requested | What it grants, and why | Access |
|---|---|---|
email | Read your email address to identify you and match it to an existing workspace invite. | Read |
profile | Read your name, used as your display name if you sign up with Google. | Read |
The login token is used once to read your identity, then discarded — Sarcio stores no Google access or refresh token for sign-in. Only a first-party session cookie is issued.
GitHub
Sign in with your GitHub account.
| Scope requested | What it grants, and why | Access |
|---|---|---|
user:email | Read your GitHub account's verified email address to identify you and link to an existing invite. | Read |
Sign-in and repository access are separate GitHub apps: the sign-in app requests only your email and grants no code access. The login token is read once and discarded; only a session cookie is issued.
Microsoft Entra
Sign in with a Microsoft work, school, or personal account.
| Scope requested | What it grants, and why | Access |
|---|---|---|
user.read | Read your basic profile and email from Microsoft Entra to identify you and link to an existing invite. | Read |
Built and supported in code, but not enabled in the live product today. When enabled, it behaves like the other sign-in providers: identity only, no token stored.
First-time sign-in links your social identity to a user whose verified provider email matches an existing invite — OAuth never provisions a workspace on its own outside the self-serve sign-up wizard. An account with two-factor authentication gets the same TOTP challenge whether it signs in with a password or a provider.
A sign-in method is Sign-in only. Signing in with GitHub doesn't connect GitHub to your workspace, and doesn't link your account for attribution: workspace connections are set up separately by admins, and you link your own accounts yourself, in Account → Linked accounts.
See it from the inside.
Spin up a workspace and every one of these connections is a click away — with the exact scopes shown before you approve them.
Create a workspace