RabbinatixDocs
Sign inGet started

Manage your organization

Members and roles

Invite people to your organization, give them a role, build your own roles, group people into teams and handle access requests.

Open Members and teams in the app

Who can do what

Everyone in an organization is a member, and every member has one role. A role is a set of permissions. It decides what the member may change; every member can read the whole organization, apart from projects kept to the people added to them. Someone may have a different role in one project (see Projects).

Members and teams have their own page, Members and teams in the sidebar, with the Members and Teams tabs; roles are in Settings → Roles & permissions. Your Personal workspace has no members, roles or teams; turn it into an organization first (see Settings).

Invite someone

You need the Manage members permission. Owners and Admins have it.

  1. Open Members and teams in the sidebar (the Members tab).
  2. Click Invite people.
  3. Type one or more email addresses, separated by commas or spaces.
  4. Pick a role. Every role except Owner is on offer; you make someone an owner after they join.
  5. Click the send button. It counts the invites, for example Send 2 invites.

Each person gets an email from Rabbinatix: who invited them, to which organization and as which role, with links to sign up or sign in with that address, and until when the invite is open.

The invite shows in the members table as Invite pending, with the date it expires. An invite lasts 7 days. Resend sends the email again and opens the invite for another 7 days; on an expired invite the button reads Renew and resend. To take one back, click Revoke on its row and confirm; its link stops working. Only people who may manage members see Resend, Revoke and Remove.

The person accepts by signing in (or signing up) with the same email address. The invite shows under Invitations in the organization menu at the top of the sidebar, and on the setup page, with a Join button. Someone who signs up with an email address must verify it first (the link in the email Rabbinatix sends them); until then they can't use Rabbinatix at all, so nobody can take an invite by signing up with an address they don't own. Google accounts are verified already. An invite for a different email address can't be accepted, and an expired one says so; renew it with Renew and resend. If the role it names was deleted meanwhile, the person joins as a Viewer. If the organization has no room left when they join, they are told so and can join once a place is free.

NoteOn a plan with a member limit, open invites count toward it until they are accepted or expire. An expired invite is marked Invite expired and takes no place. The invite dialog tells you how much room is left. See Plans and billing.

If you can't invite, the button reads Request an invite…. It files an access request for someone who can (see below).

Change a role or remove a member

On the Members tab, pick a new role in the member's Role list and confirm with Change role (Cancel keeps the old one). The change applies at once and is written to the activity log. To remove someone, click Remove on their row; they lose access straight away. You can't change your own role or remove yourself here.

Leave an organization

To leave an organization yourself, open Settings → General and click Leave <organization name> under Leave this organization, then confirm. You lose access at once, and the app opens another workspace you're in, or the setup page if there's none. To come back, an owner or admin invites you again. The last owner can't leave: make someone else an owner first, or delete the organization. A Personal workspace can't be left, only deleted.

Owners

Owners have every permission, always, and they are the only ones who can delete the organization. Two rules keep an owner in place:

  • Only an owner can give or take the Owner role.
  • There is always at least one owner. Make someone else an owner before the last one steps down.

The built-in roles

RoleBuilt inWhat it can do by default
Owneryes, lockedEverything, including billing and deleting the organization
AdminyesEvery permission (you can tune it)
DeveloperyesSystems, endpoints, lifecycle, deprecations, releases, logic, test data and expected results, flows, test cases, runs, requirements, reveal secrets, tickets, chat, whiteboards
Project ownerno (suggested)Logic, test data and expected results, flows, test cases, runs, approve flows, requirements, tickets, chat, edit and publish whiteboards
QAno (suggested)Test data and expected results, test cases, runs, tickets, chat
VieweryesRead everything, do test runs, create tickets, post in chat
AuditoryesRead everything and view the activity log

Project owner and QA are custom roles you can rename or delete.

Permissions

The matrix on Roles & permissions lists every permission in groups:

GroupPermissions
OrganizationOrganization settings, Manage members, Manage roles, Manage teams, Integrations, View activity
ContractsEdit systems, Edit endpoints, Change lifecycle, Deprecate APIs, Releases & deployments, Public network, Contract policy
BehaviourEdit logic, Edit test data & expected results, Edit flows, Edit test cases, Run flows, Approve flows, Edit requirements, Reveal secrets
TicketsCreate tickets, Edit tickets, Manage the board
ChatPost in chat, Manage chat
PlanningEdit whiteboards, Publish whiteboards

Tick or clear a box to change a role. You need Manage roles. The Owner column can't be changed.

Custom roles

  1. On Roles & permissions, click New role.
  2. Give it a name, such as Release manager.
  3. Under Copy permissions from, pick a role to start from, or nothing.
  4. Click Create role, then tick permissions in the matrix.

The pencil on a role card renames it and edits its description. The bin deletes a custom role; its members become Viewers. Built-in roles can't be deleted. You can't take Manage roles away from your own role, so you can't lock yourself out.

Teams

A team is a named group of members. A system can name an Owner team, and the Teams tab shows which systems each team owns. A new owner team takes effect at once, even where changes wait as drafts: team issues and sign-off requests go to it straight away.

  1. Open Members and teams, then Teams.
  2. Type a name in New team name and click Add team.

The bin on a team card deletes it, after you confirm. Its members stay in the organization and just leave the team; systems, flows and tickets it owned are left without a team. Only people with Manage teams see the bin and the new-team card. Teams can't be renamed yet. People join a team through an approved access request that names it.

Access requests

An access request is a ticket that asks for a role, extra permissions or a team, for yourself or for someone not yet invited.

  • Use Request access in the account menu at the top right.
  • When the app refuses an action because your role lacks a permission, the message has a Request access button, filled in with what was missing.

Requests go to the board, assigned to people who manage members (or roles, when permissions are asked for). The ticket shows what would change, for example "Role: Viewer → Developer". The reviewer clicks Approve & apply to make the change, or Reject with a reason. Both notify the requester. You can't approve your own request, and only an owner can approve an Owner role change.

Only the requester, the person it's about and people who manage members can see an access request. The Members tab shows open requests per member.