Roles

In each BaseHub team, accounts can assume one of four specific roles. These roles prioritize simplicity and ease of use in both UI design and functionality for every scenario. They aim to avoid a needlessly complex user interface for non-technical individuals and, at the same time, ensure that editors don't alter the schema.

Role	Capabilities
Owner	Has full control over the repository and team settings. This role is capable of inviting new members, assigning roles, and managing all aspects of blocks and properties. Essentially, the Owner can execute any available operation within BaseHub's platform.
Member	Can edit, create, remove blocks and their properties. Can create and delete repositories. The highest role apart from the Owner, is the most versatile, without incurring in team management nor billing settings.
Editor	Can edit blocks and content; can add new collection instances. Think of it as a copywriter / marketer, they can add a post entry, or update a subtitle, or change an image, but they won’t be able to delete documents, or create new blocks that would change the API schema.
Viewer	Can view all the content, including hidden values and members settings. This is a less crucial role, but think of it as a guest that could check everything looks good, without needing to worry about modifying anything by accident.

Members Settings Page

In order to manage the members present in a team, two conditions must be true:

It can’t be a personal team.
You should have the “Owner” role.

You get the owner role when you’re the creator of that team or another owner gives you that role.

Inviting a member

You can invite someone to the team via email or sharing an invite link. In both cases you can select which role will be assigned to them beforehand. Note that the invite link can be reused, so it should be kept secure.

Update a member role

By clicking the Gear button, a dialog for member permissions appears. Here, you can adjust the user's role. If the role assigned is different from “Owner”, you can limit access to specific repositories within the team. This is useful for example, if your organization needs to give access to an external individual that will work in a specific project and don’t want to share everything with them.

Remove from team

To remove a user from the team, simply click the "Remove from team" button in the same permissions dialog.