Organizations
Organizations and teams
A workspace keeps your Projects, team members, plan, and billing together. Everyone signs in with their own account, and nobody shares passwords or server access.
How it fits together
| Level | Holds | Managed from |
|---|---|---|
Account | Your sign-in, two-step sign-in, and profile | Account |
Workspace | Members, plan, billing, invoices, and every Project in it | The workspace switcher, Billing, and Audit |
Project | Database, application users, storage, functions, logs, backups, and settings | The Project page |
One account can belong to several workspaces. Switch between them from the top left of the console.
Create a workspace
- Sign in to the console. New accounts are guided through onboarding and get a first workspace.
- Open the workspace switcher and choose to create a new workspace.
- Give it a clear name, such as your company or client.
- Choose a plan. Free workspaces can upgrade at any time from Billing.
- Create your first Project inside it.
Invite your team
- Open the workspace and go to its members area.
- Invite each person by email.
- Give them only the access their job needs.
- The invitation stays pending until they accept it. You can cancel it before then.
- Remove access as soon as someone changes role or leaves.
The number of team members depends on your plan. The Billing page shows how many seats you have used.
Good practice
- Keep at least two owners, so billing and recovery never depend on one person.
- Ask every member to turn on two-step sign-in.
- Use separate workspaces for separate clients or companies. Billing and access never cross between them.
- Review the Audit page regularly to see who changed what, and when.
Team members and application users are different
Workspace members use the RustaBase console. The people who sign in to your app are application users, stored in each Project's Authentication area. Inviting someone to a workspace never gives them an account in your app, and the other way round.
Fix it yourself. The link below opens this file in GitHub's editor and forks the repository for you if you need one, and your change becomes a pull request without leaving the browser.