Team

An organization is shared by a team. Everyone in it sees its projects; their role decides what else they can do. Open Team in the dashboard to see who’s in it, change roles and invite more people.

​

Roles

From least to most:

​

What each role can do

An organization always has at least one owner: the last owner can’t be removed or demoted. Make a second owner first.

​

Invite someone

1. Team → Invite someone.
2. Enter their email address and choose a role. Only an owner can invite another owner.
3. They get an email with a link to join. If they don’t have a Pawabase Cloud account yet, they create one from the link.

Invitations expire after 7 days. Until accepted they’re listed under Pending invitations, where you can cancel them. To re-invite after expiry, invite them again.

​

Change a role or remove someone

On Team, change a person’s role, or remove them. Removing someone takes away their access to the organization and its projects immediately. It doesn’t affect any accounts they have in your app.

​

Team size limits

Each plan includes a number of team members. When you reach it, Invite someone tells you so and suggests an upgrade. See Plans and limits.

​

Who can do what inside a project

The organization role decides who can open Studio. Inside a project, what an integration can do is decided by API keys and their scopes, and what your app’s users can do by your access rules. Give automated tools and CI their own scoped keys rather than a person’s login.

​

Good practice

• Two owners, so you’re never locked out.
• Admin for people who run projects, member for people who only create them, viewer for everyone else.
• One login per person. Never share an account; the audit log and the organization’s activity then show who did what.
• Remove people promptly when they leave, and rotate any secret keys they knew.