Skip to main content
Chevre uses role-based access control (RBAC) to manage what each team member can see and do in your workspace. Every member is assigned one of four roles, and each role comes with a fixed set of capabilities. By combining workspace-level roles with project-level visibility settings, you can give your team exactly the access they need — no more, no less.

​
Workspace Roles

The table below summarizes what each role can do across the workspace.
The workspace Owner always retains full access to every resource in the workspace, regardless of any project-level visibility settings. If you need to restrict a project from most of your team, use Private visibility — but know that the Owner will always be able to see it.

​
Inviting Members

Invite new members to your workspace from Settings → Members → Invite.
1

Open Member Settings

Navigate to Settings → Members in the left sidebar of your workspace dashboard.
2

Click Invite Members

Click the Invite Members button in the top-right corner of the Members page.
3

Enter email addresses

Type one or more email addresses separated by commas. Each address will receive a separate invitation email.
4

Assign a role

Choose the role you want to assign to the invitees: Admin, Editor, or Viewer. You can change a member’s role at any time after they accept the invitation.
5

Send invitations

Click Send Invitations. Each invitee receives an email with a link to accept the invitation and join the workspace. Pending invitations appear in the Pending tab of the Members page until accepted or revoked.
You can also invite members programmatically using the Chevre API. The following example sends an invitation to a new Editor:
A successful response returns the pending invitation object:
Invitations expire after 7 days. If an invitee misses the window, resend the invitation from Settings → Members → Pending.

​
Changing a Member’s Role

1

Open Member Settings

Navigate to Settings → Members in the workspace sidebar.
2

Find the member

Locate the member in the list. Use the search field to filter by name or email if the workspace has many members.
3

Open the role dropdown

Click the member’s current role label to open the role dropdown.
4

Select the new role

Choose the role you want to assign. The change takes effect immediately — the member does not need to log out and back in.
Only Owners and Admins can change member roles. An Admin cannot promote another member to Owner — only an existing Owner can do that.

​
Removing a Member

1

Open Member Settings

Navigate to Settings → Members in the workspace sidebar.
2

Find the member

Locate the member you want to remove.
3

Click Remove

Click the ⋯ menu next to the member’s name and select Remove from workspace. Confirm the action in the dialog that appears.
Removing a member immediately revokes their access to the workspace and all its projects. Any workflows or automations they created remain intact and continue to function — removing a member does not affect workspace data.
You cannot remove the last Owner of a workspace. Before removing the current Owner (including yourself), you must first promote at least one other member to the Owner role. If a workspace loses its only Owner due to account closure or other circumstances, contact support@chevre.io to resolve the situation.

​
Project-Level Permissions

Workspace roles define what a member can do across the entire workspace, but project visibility adds a second layer of access control at the project level.
Owners and Admins always have access to every project, regardless of visibility. Editors and Viewers only see Private projects they have been explicitly added to.
To add an Editor or Viewer to a specific private project, open the project, go to Settings → Access, and click Add Members. Select the workspace members you want to grant access to. Their workspace role determines what they can do once inside the project — you cannot grant a Viewer editing rights at the project level.
Use Private projects for sensitive or in-progress work that only a subset of your team should see, and Shared projects for stable, company-wide processes. This combination lets you take full advantage of RBAC without having to create separate workspaces for every team boundary.