Step 6 · 4 min read
Collaborate
Six Sigma is a team sport. LeanProjax has a two-level permissions model — workspace membership for who's in the org, and per-assignment roles for who can do what on a given project. This chapter walks through both, plus how to invite, share, and audit.
At a glance
Three concepts to keep separate.
Workspace members
People who belong to your org. Owners/admins set the policy.
Assignment members
People granted Lead, Contributor, or Viewer on a specific project.
Activity log
Every meaningful action is recorded — invites, role changes, edits.
The role model
Three roles, one bypass.
Within an assignment, every person has exactly one role. Higher roles include everything lower roles can do.
- Lead — edit everything, invite and remove members, archive or delete the assignment. Usually one or two per project.
- Contributor — edit data and toolkit runs, comment, but can't change membership or delete.
- Viewer — read-only access plus the ability to leave comments. Good for stakeholders who need visibility without write access.
The one exception: anyone with workspace role Owner or Admin is automatically treated as Lead on every assignment in the org — no per-assignment invite needed. That's how leadership and platform admins keep oversight without manual maintenance.
Who can do what on an assignment
Inviting people
From the assignment, or from settings.
From inside an assignment
Open the assignment's Members tab and click + Invite. Add one or many email addresses, pick a role, and send. The invitee gets an email with a one-click accept link. If they don't have an account yet, the link drops them on the signup page and routes them back to the assignment after they're in.
From the workspace
Owners and admins can invite people to the workspace from Settings → Team → Members. These people show up in the assignment-invite autocomplete immediately, so it's faster than emailing them individually for every project.
- 1Members tab — every project has one. The number on the badge is just the count of members.
- 2+ Share opens the invite dialog where you pick role and add emails.
- 3Transfer ownership hands the project to a teammate; you keep Lead access by default.
- 4Role picker on the right — click to promote or demote. The last Lead is protected from removal.
Sharing projects
Read-only links and stakeholder reviews.
If you want someone outside the project (a sponsor, a reviewer, a finance partner) to see the work without becoming a member, share them in as a Viewer. They get the same live access the team has, but can't change anything. When the project closes, revoke from the same tab.
For a one-time share — say emailing the report to leadership — use the Export PDF flow instead. That's covered in the last chapter.
Activity log
Who did what, when, and on which assignment.
The Activity tab on every assignment records every meaningful event — invites, role changes, charter edits, toolkit runs, PDF exports. Use it as an audit trail when quality leadership reviews the project, or to onboard a new team member by skimming what happened so far.
The workspace-level activity view (Settings → Team → Activity) shows the same stream across every assignment in the org.