Skip to main content

Roles and access levels

The four access levels in Leanmote — Owner, Admin, Leader, Collaborator — and what each can do.

Leanmote uses a four-tier access model. Two tiers are directly assignable (Owner, Admin); one is derived automatically from team membership (Leader); one is the default for everyone else (Collaborator). This article explains each level and exactly what it can and can't do today.

The four access levels

  • Owner — one per workspace. Has every Admin capability plus the ability to change other users' access levels and edit organization-wide settings. The first user in a workspace becomes Owner.

  • Admin — full operational access. Manages integrations, users, teams, and status mappings. Can view every dashboard. Can be promoted/demoted by the Owner.

  • Leader (Team Manager) — auto-detected. A user becomes a Leader when they're listed as a manager on a team in your team configuration. Leaders can view dashboards for the teams they manage and create Views, but can't connect integrations or manage users outside their teams. Leader is not a directly assignable role — it follows team-manager assignments.

  • Collaborator — the default for new users. Collaborators land on the Productivity Tools page as their home and don't see Performance Delivery, Strategic Overview, Project Financials, or AI Governance dashboards. They can connect their personal integrations.

Capability matrix

A condensed view of what each level can do today:

  • Connect / disconnect organization integrations — Owner ✓, Admin ✓, Leader ✗, Collaborator ✗.

  • Connect personal integrations — Owner ✓, Admin ✓, Leader ✓, Collaborator ✓.

  • Add / edit / delete users — Owner ✓, Admin ✓, Leader ✗, Collaborator ✗.

  • Manage teams — Owner ✓, Admin ✓, Leader ✗, Collaborator ✗.

  • Change another user's access level — Owner only.

  • Change organization-wide settings — Owner only.

  • Configure status mapping — Owner ✓, Admin ✓, others ✗.

  • View Performance Delivery — Owner ✓, Admin ✓, Leader ✓ (their teams), Collaborator ✗.

  • View Strategic Overview — Owner ✓, Admin ✓, Leader ✓, Collaborator ✗.

  • View Project Financials (including cost) — Owner ✓, Admin ✓, Leader ✓ (their teams' shared subset), Collaborator ✗.

  • Create and save Views — Owner ✓, Admin ✓, Leader ✓, Collaborator ✗.

  • View financial data (cost rates, salary) — Owner ✓, Admin ✓, Leader ✗, Collaborator ✗.

How role assignment works

  • Owner is the first user in the workspace. Ownership transfer happens by the current Owner promoting another user; contact your account team if you need a transfer.

  • Admins are assigned by the Owner from the Users page (Administration → Users).

  • Leader is automatic — assign a user as a manager on a team (in the Teams page) and they pick up Leader privileges for that team's data.

  • Collaborator is the default for any new user invited to the workspace.

Recommended access policy

  • Two Admins per workspace — primary and backup. Avoid single-person dependencies.

  • Engineering managers as Leaders via team-manager assignment. They get the dashboards they need automatically.

  • Engineers as Collaborators by default. Promote case-by-case if someone needs analytics access.

  • Executives — promote to Admin if they need cross-team visibility, otherwise add them to a leadership team and they'll pick up Leader access for it.

Related articles

  • Users management

  • Teams management

  • SSO and SCIM

Did this answer your question?