Single sign-on
Because Gigadrive does not support SAML or SCIM today, team members sign in with individual Gigadrive accounts.
Gigadrive has no single sign-on. You cannot connect your organization's identity provider, enforce a provider for your team, or sync a directory.
Not available
There is no SAML, no SCIM, no OIDC federation from a customer identity provider, and no domain-based account capture. Nothing in the platform reads an external directory, and no organization setting exists to point at one.
How people sign in
Everyone signs in with their own Gigadrive account, from the Gigadrive account app. The sign-in flow is identifier first: you enter an email address, and the available factors follow from what that account has set up.
- A password, minimum 8 characters.
- A passkey, through WebAuthn.
- Two-step verification with an authenticator app or an emailed code.
See Sign-in for the flow itself and Two-step verification for the second factor.
Social sign-in is not SSO
An account can be linked to Google, Microsoft, Facebook, Apple ID, or GitHub, and any of the five can be used to sign in.
That is a convenience for one person, chosen by that person. It does not let you require Microsoft for everyone at your company, it does not create accounts from your tenant, and it does not remove access when someone leaves it. Connected accounts covers linking and unlinking.
What this means for a team
Plan on the basis that account lifecycle is the account holder's, not yours. There is no provisioning, no deprovisioning, and no way to force a factor on someone else's account.
Sessions last 30 days and are signed out one at a time. There is no list of active sessions and no sign-out-everywhere control, so revoking a person's access is not something you can do from the Gigadrive side. See Sessions.
Organization membership does not help here either: it is fixed at creation, and there is no remove-member flow. Invitations has the current state of that.
Machine access is separate, and revocable
The one credential you do control centrally is an API key. It belongs to an application rather than to a person, its reach is exactly its scopes, and DELETE /api-keys/{apiKeyId} cuts it off within five minutes. Prefer one per system over sharing a person's session. See API keys.