Teams & Collaboration
Robonito supports multi-user workspaces where team members can collaborate on test suites, share environments, and jointly manage integrations.
Roles
Every workspace member has one of three roles. Roles control what actions a member can take.
| Role | Who It's For | Key Permissions |
|---|---|---|
| Owner | The workspace creator or an assigned successor | Full access — manage billing, delete org, transfer ownership, manage all members and roles |
| Admin | Team leads and QA managers | Create/delete workspaces, manage members, configure integrations, manage reporting thresholds and ROI assumptions |
| Member | Individual contributors | Create and run test cases, view reports, use integrations configured by Admin/Owner |
Roles are shown with colored badges: Owner (grape), Admin (blue), Member (gray).
Permission Reference
| Feature | Member | Admin | Owner |
|---|---|---|---|
| Create / run test cases | ✅ | ✅ | ✅ |
| Create / delete suites | ✅ | ✅ | ✅ |
| Create / edit tags | ✅ | ✅ | ✅ |
| Create / edit schedules | ✅ | ✅ | ✅ |
| Upload / delete data sources | ✅ | ✅ | ✅ |
| Create / edit environments | ✅ | ✅ | ✅ |
| Invite team members | ❌ | ✅ | ✅ |
| Remove team members | ❌ | ✅ | ✅ |
| Configure integrations | ❌ | ✅ | ✅ |
| Manage billing / subscription | ❌ | ❌ | ✅ |
| Delete organization | ❌ | ❌ | ✅ |
| Transfer ownership | ❌ | ❌ | ✅ |
Workspace Access Scope
When inviting a member, you choose their access scope:
- All Workspaces — the member can access every workspace in the organization, with a default role applied uniformly.
- Specific Workspaces — the member can only access the workspaces you explicitly assign, and can have a different role per workspace.
This lets you give a contractor access to a single Staging workspace without exposing Production.
Inviting a Team Member
Requires: Admin or Owner role
- Navigate to Teams in the left sidebar.
- Click Invite Member.
- Enter the team member's email address.
- Choose access scope:
- All Workspaces: select a default role (Owner / Admin / Member)
- Specific Workspaces: add one or more workspace + role pairs
- Click Send Invite.
The invited member receives an email with an acceptance link. Their status shows as Pending until they accept.
Screenshot placeholder: [Screenshot of the Invite Member panel showing email input, scope selector (All Workspaces / Specific Workspaces), and workspace + role pair selector]
Managing Existing Members
The Teams table shows all current members with:
| Column | Description |
|---|---|
| Name / Email | Member identity and avatar |
| Role | Current role badge |
| Workspace Access | Shows "All Workspaces" or up to 2 workspace names with overflow tooltip |
| Status | Active or Pending |
| Actions | Edit access, Change role, Remove member |
Changing a Member's Role
Click Edit next to a member to open the access panel. Change their role or workspace assignments and save.
Note: Promoting a member to Owner or demoting an existing Owner requires Owner-level access.
Removing a Member
Click Remove next to a member. The member loses access to all workspaces immediately. Their previously executed test runs and reports are preserved.
Accepting an Invitation
When you receive a Robonito team invitation by email:
- Click the Accept Invitation link in the email.
- Sign in or create a Robonito account.
- You are automatically added to the workspace(s) with the assigned role.
If the invitation link has expired, ask the Admin or Owner to resend it.
Organization vs. Workspace
Robonito has two levels of access control:
- Organization — the top-level account. Owns billing and all workspaces.
- Workspace — a project environment (e.g.,
Staging,Production, orMobile QA). Each workspace has its own test suites, integrations, environments, and member access.
A member with Admin access to Organization A may have Member access in one of its workspaces, or no access to another workspace entirely — depending on how their access was scoped.