Project Teams
A project team lists the people who have been invited to a project from outside the organization that owns it. Members of the organization don’t need to be on the team – they automatically have Manager access to every project the organization owns.
For the complete access model, see Access and Permissions.
Who Belongs on a Team
Invite people to a project team when they need access but aren’t part of your organization:
- Consultants and commissioning agents working on a specific building.
- Vendors and contractors who maintain particular systems.
- Customers and stakeholders who need visibility into project data.
Organization members cannot be invited to the organization’s projects, since they already have access. To give a colleague access to every project, add them to the organization instead.
Project Roles
Each team member is invited with a role that controls what they can do:
| Role | Manage Team | Control Equipment | Modify Project | View Project |
|---|---|---|---|---|
| Manager | Yes | Yes | Yes | Yes |
| Operator | No | Yes | Yes | Yes |
| Editor | No | No | Yes | Yes |
| Viewer | No | No | No | Yes |
Manager – Full control of the project, including settings, credentials, API keys, and inviting or removing other external users.
Operator – Everything an Editor can do, plus control the building: write points, apply scenes, and modify scenes and schedules. Cannot change settings or the team.
Editor – Can modify project data – sources, assets, spaces, zones, and Drive files – and use Explorer, but can never write to equipment. A good fit for analytics, commissioning, and modeling work.
Viewer – Read-only access to project data, including scenes and schedules.
New invites default to Viewer.
Viewing Access
The Team page in project settings lists who has access to the project, with an Access column showing how they got it:
| Access | Meaning |
|---|---|
| External | A user invited to the project from outside the organization. |
| Provider | A provider connected to the organization or project, listed as one row. |
| Organization | The organization that owns the project, listed as one row (always Manager). |
External users are listed individually. If a provider’s users have different roles, the Role column shows Mixed.
Only external users can be managed from this page. Organization access is managed from the organization’s members, and provider access from Providers.
Leaving a Project
External users can leave a project from their Shared Projects page. Organization members can’t leave individual projects; their access ends when they’re removed from the organization.
Best Practices
- Add colleagues to the organization rather than inviting them to each project.
- Invite external users with the lowest role they need – Viewer for stakeholders, Editor for people who model or configure data, and Operator only for those who need to control equipment.
- Assign the Manager role to external users sparingly, since Managers can invite others and create API keys.
- Review external access periodically and remove people who no longer need it.