Team & Roles
Invite members, manage roles, and collaborate.
Inviting Team Members
- Open your project
- Click the Team icon in the sidebar
- Enter the email address of the person to invite
- They receive an invitation email and can join immediately
Who can open the project
An invitation goes out to anyone with an Airbuild account, whatever plan they are on. Being in the team and being able to open the project are two different things, and the Team panel says which is which: after you invite someone whose plan is not enough, the confirmation names the plan they need, and the member keeps a marker in the list until they have it.
Two things set that bar, and the higher one wins:
- The project type. A web app needs Web App Builder or higher; a website needs Website Builder Pro or higher.
- The team. The highest plan in the project is the minimum for joining it. If someone in the project works on Suite Builder, Suite Builder is what it takes to open it — otherwise a member would sit in a project where half of what is built is out of their reach.
The project owner always opens their own project, whatever their plan. Members who were already in a project before this rule keep their access.
Roles
| Role | Edit Code | Use AI Chat | Publish | Manage Team | Delete Project |
|---|---|---|---|---|---|
| Owner | Yes | Yes | Yes | Yes | Yes |
| Admin | Yes | Yes | Yes | Yes | No |
| Editor | Yes | Yes | No | No | No |
| Viewer | No | No | No | No | No |
Changing Roles
Admins and Owners can change team member roles in the Team panel. Click on a member to toggle their role.
Removing Members
Admins and Owners can remove team members from the Team panel.
Transferring Ownership
The project owner can transfer ownership:
- Go to Project Settings
- Click Change next to the Owner
- Select the new owner from your team members
- Confirm the transfer
How Collaboration Works
- Each team member works in their own workspace, with its own file tree and dev server
- Changes are synced via Git branches
- The AI chat history belongs to the project, not to the person who typed it, so context does not stay locked in one developer's session. Each message is stored with its sender, which is how the agent knows who asked for what — see Shared Context & Standards.
- The live preview shows the latest committed code
- Use Pull Requests to merge each other's work
Notifications
Team events trigger notifications:
- New member joined
- Member removed
- Role changed
- Ownership transferred
Configure notification channels in Settings > Notifications.