---
summary: "ScaiKey is the source of truth \u2014 accounts, organisations and teams\
  \ follow your ScaiKey groups."
title: Access and identity
path: concepts/access
status: published
---

# Access and identity

ScaiKey decides who you are and what you belong to; ScaiGit follows. You
never create ScaiGit accounts, organisation memberships or team memberships
by hand: they are derived from ScaiKey and kept in step with it.

## Accounts

Every person in a ScaiKey organisation that has a ScaiGit instance gets an
account on that instance, and signs in with **Sign in with ScaiKey**. There
are no local passwords. Someone removed or suspended in ScaiKey is suspended
in ScaiGit within a minute, and their access tokens stop working. Accounts are
suspended, never deleted, so their commits, reviews and history stay intact.

## Organisations and teams from groups

Two kinds of ScaiKey group shape ScaiGit:

| ScaiKey group | Effect in ScaiGit |
|---|---|
| `scaigit:org:<org>:owners` | Creates the organisation `<org>`; members are its owners. |
| `scaigit:org:<org>:team:<team>` | Creates the team `<team>` in `<org>`; members are the team. |

Organisation owners then decide which repositories each team can reach, in
the organisation's settings. Teams created from ScaiKey groups have write
access to the repositories they are given.

ScaiGit corrects drift: a member added to a ScaiKey-managed team by hand is
removed again, because ScaiKey is where membership changes. Organisations and
teams you create yourself in ScaiGit, without a ScaiKey group behind them,
are left alone.

## Administering an instance

Who may administer an instance in the console, and who may approve agent
actions, is set in the instance's policy, usually by mapping a ScaiKey group
(such as the owners group) to an administrator or reviewer role.

## Credentials for git

- **SSH:** publish your public key once in the console under **My SSH keys**.
  See [SSH keys](/docs/scaigit/guides/ssh-keys).
- **HTTPS:** create an access token in the web interface under
  **Settings → Applications** and use it as the password.
- **Deploy keys:** for a machine that needs one repository only, a repository
  administrator can add a deploy key under the repository's **Settings →
  Deploy keys**.
