Teams, members, and permissions

Organization membership establishes who belongs to your organization. Access grants determine what they can use in its projects. Use teams to manage a shared set of permissions for people working on the same responsibility.

Invite a member

Open Members & roles, choose Invite member, enter the email address, and select Member or Admin. Review pending invitations and their delivery and expiry states. Revoke invitations that are no longer needed.

Organization admins manage organization-level resources. A member can receive narrower project and notification permissions without that broader role.

Create a project team

1. Open Project settings → Teams and create a team.
2. Open its Members tab and add organization members.
3. Open Access list and create grants for the team’s responsibilities.
4. Inspect Effective access to confirm the instruments implied by those grants.

Teams are project-scoped. For example, “Field reviewers” can receive access to one site, while “Integration operators” can receive pipeline and diagnostics capabilities for the project.

Choose a scope and capability

Instrument visibility can be scoped to a whole project, site, or instrument group. Project-level bundles provide additional capabilities such as anomaly management, anomaly history, parser management, connector pipeline management, connector diagnostics, connector data management, and instrument data writing.

Dashboard viewer grants support a focused dashboard audience. Access to a dashboard and access to browse instruments are distinct; verify the intended audience’s experience instead of assuming one implies the other.

Direct user grants are also available for supported scopes. A user’s effective access combines direct and inherited team grants. Removing a single grant may therefore leave access supplied through another team or scope.

Verify access

Use a member’s Access view to inspect direct grants, team memberships, inherited grants, and effective instruments. A project’s access inspector can also resolve a selected user or team. Individual users can check My access.

When a page or control is missing, check the user’s organization, selected project, granted capability, and scope. Avoid resolving a narrow access problem by assigning organization administrator access automatically.

Notification and integration boundaries

Notification viewer and manager bundles control contact groups and email templates. External connections are organization-owned; project pipeline access does not expose upstream credentials or allow changing organization grants.

Review grants when moving instruments between sites or changing group membership. Removing an organization member also removes their team memberships in that organization. API access uses separate scoped keys described in API authentication.