Teams
A team owns ledgers, and the people and systems that reach those ledgers hold credentials belonging to it. Every credential names exactly one team, and the core refuses any request whose credential names a different team than the ledger it is addressing, so the team is the boundary nothing crosses.
On this page
Create a teamLink to this section
Sign up with an email address, a team name, and a password. The console emails a single-use code; entering it confirms the address, claims the team name, and makes you the team's first administrator.
A team name is a URL path segment: 2 to 64 characters, lowercase letters, digits and hyphens, beginning with a letter or a digit. It appears in the console's addresses (/acme/login) and in the path the SDKs use to reach a ledger. A name is claimed once and is not reassigned, so pick one you can keep.
Sign-up also provisions a development ledger called main, so a new team has something to open immediately.
Adding peopleLink to this section
Each person on a team signs in with their own email address and password, and holds their own API credential for the Ledger API. Addresses are unique within a team rather than globally, so one person can hold an account on two customers' teams with the same address — which is why the sign-in page asks which team you mean.
An administrator adds everyone after the first from the Team page in the console, by inviting an address and choosing a role. The credential goes with the invitation rather than being a second errand. See Access Control for what accepting an invitation does and what each role permits.
Credentials for the Ledger API are created and revoked on the API keys page beside it. Anybody may create their own; an administrator sees and can revoke the team's.