Team & Members
Access in Aptrics works on two levels: a workspace role that decides what someone can do to the organization, and per-project roles that decide which semantic layers they can read or change. Getting both right is what keeps a shared metric layer trustworthy.
This page covers inviting people, the roles available, and how permissions combine.
Managing Members
Invite Members
Invite people by email from Members in workspace settings. Choose their workspace role and, optionally, the projects they should land in. Invitations expire after a set period and can be resent or revoked while pending.
Workspace Roles
Owner has full control including billing and deletion. Admin manages members, projects, and connectors but not ownership transfer. Member works inside the projects they are assigned to. Viewer is read-only across everything they can see.
Project Roles
Within a project a member is an editor or a viewer. Editors create and change models, metrics, and dashboards; viewers explore metrics and read dashboards but cannot alter definitions. Restricting edit rights on production projects to a small group is the usual pattern.
How Permissions Combine
The effective permission is the narrower of the two levels. A workspace viewer granted the editor role on a project still cannot edit — the workspace role caps what any project role can grant. Owners and admins have access to every project regardless of project-level assignment.
Teams
Group Members into Teams
Teams are named groups — Analytics, Finance, Growth — that can be granted project roles as a unit. Adding someone to a team gives them everything that team has, which is far easier to audit than a long list of individual grants.
Review Access
The members list shows each person's workspace role, teams, project access, and last activity. Use it for periodic access reviews and to spot accounts that should be deactivated.
Remove a Member
Removing a member revokes their access immediately and ends active sessions. Content they created — models, dashboards, saved explorations — stays with the workspace. API keys they issued keep working until revoked separately, so review those as part of offboarding.