Docs / Get started
Projects and teams
6 minute read
An organisation holds projects, and projects hold resources. Teammates join the organisation with a role that decides what they can change.
1. How organisations and projects fit
Each organisation has its own wallet, invoices, team and API keys. Inside it, projects keep resources apart. Every organisation starts with Production and Staging.
Each project has its own private network. Resources in Staging can't reach resources in Production, and internal names include the project, like orders-db.staging.internal.
2. Switch projects
Use the project switcher at the top of the console sidebar. Lists, graphs and the create forms all follow the selected project.
From the CLI, pass --project or set a default:
simplicloud projects listsimplicloud config set project stagingsimplicloud servers list --project production
3. Invite teammates
Open Team → Invite by email, enter an address and pick a role. Invites expire in 7 days. Teammates are free.
simplicloud team invite [email protected] --role developersimplicloud team list
4. Pick the right role
Roles are fixed. Give people the smallest role that lets them do their job.
| Role | What it can do |
|---|---|
| Owner | Full control, including deleting the organisation. One per organisation. |
| Admin | Everything except deleting the organisation. Can invite people and change roles. |
| Developer | Creates and changes resources, opens consoles and makes API keys. No billing. |
| Billing | Tops up the wallet and downloads invoices. Can see resources, not change them. |
| Viewer | Read-only. Sees resources and graphs. Good for auditors and support. |
5. Keep an eye on changes
The Audit log records every change by a person or an API key: who, what, when and from where. Entries are kept for 12 months and can be exported as CSV.
- Change a role from Team → Change role. It applies on the person's next request.
- Removing someone signs them out everywhere. SSH keys they added to servers stay on those servers until you remove them.