Team Management
Invite team members, assign roles with appropriate permissions, manage invitations, and control who has access to what within your organization.
Roles & Permissions
A91I uses a role-based access control system with four roles. Each role inherits the permissions of the roles below it.
| Role | Workflows | Connections | Team | Billing | Organization |
|---|---|---|---|---|---|
| Viewer | View only | View own | View list | No | No |
| Member | Create & edit own | Manage own | View list | No | No |
| Admin | Manage all | Manage all | Invite & manage | View | Edit settings |
| Owner | Manage all | Manage all | Full control | Full control | Full control |
- Viewer
- Read-only access. Can view workflows, execution history, and the team list. Cannot create, edit, or execute anything. Ideal for stakeholders who need visibility without the ability to make changes.
- Member
- The standard working role. Can create and edit their own workflows, manage their own connections, run test executions, and act on approval requests. Cannot modify other users' workflows (unless explicitly shared).
- Admin
- Organizational management. Can manage all workflows and connections regardless of ownership, invite and remove team members, change user roles, and edit organization settings.
- Owner
- Full control over everything, including billing, plan changes, and the ability to delete the organization. There must always be at least one Owner.
Inviting Team Members
Go to Settings → Team
Click "Invite Member"
Enter the email and choose a role
Send the invitation
Invitation states
Managing Members
Changing a Role
Click the three-dot menu next to a team member and select Change Role. Choose the new role from the dropdown and confirm. Role changes take effect immediately.
Role hierarchy
Removing a Member
Click the three-dot menu and select Remove from Organization. The user loses access immediately. Their workflows and connections remain in the organization but become unassigned.
- Shared workflows created by the removed user are still accessible to other team members.
- Private workflows become inaccessible until reassigned by an Admin.
- Connections created by the removed user are deactivated. Reassign them to maintain workflow functionality.
Plan Limits
The number of team members depends on your plan:
| Plan | Team Members |
|---|---|
| Free | 1 (single user) |
| Pro | 5 members included. Additional members available as add-ons. |
| Enterprise | Unlimited members. |
If you hit the member limit, you will need to upgrade your plan or remove an existing member before inviting new ones.
Best Practices
- Use the least privilege principle — assign Viewer to stakeholders, Member to workflow builders, and Admin only to those who need to manage the team.
- Review the team list periodically and remove departed employees promptly.
- Use the audit log to monitor who is making changes and when.
- Avoid creating multiple Owner accounts unless necessary for business continuity.
- Share workflows with specific permissions rather than making them Team-visible when only a few people need access.