Project members
A project is the workspace for one campaign or client: data tables, spinners, jobs, and records. Project members are the people allowed to work inside that project. Membership is how you keep Client A’s data away from people who only work on Client B.
Organization roles vs project members
Section titled “Organization roles vs project members”These are related but not the same idea:
| Layer | What it controls |
|---|---|
| Organization role (Admin, Agent, Supervisor, custom) | What you can do in the product overall — billing, dialler, user management, creating projects |
| Project membership | Whether you are part of a specific project’s team and what you can do inside that project |
Someone might be an Agent for live calls organization-wide, but only a member of two outreach projects. An Admin typically can reach every project for support and setup.
Think of org roles as “job title in the company,” and project members as “which campaigns you are staffed on.”
Where members live
Section titled “Where members live”Open a project → Settings. The Members section lists people on that project with a project-level access label (for example Admin, Editor, Viewer, or Guest on the project).
src/assets/screenshots/33-project-members.pngFrom here you can:
- See who already has access
- Invite another organization user onto the project
- Adjust their project role when editing is available
Invite flows require the person to already exist in the organization (see Users and seats). Project invite does not create a brand-new company account by itself.
Typical project roles (concept)
Section titled “Typical project roles (concept)”Exact labels may vary as the product evolves, but the intent is:
| Project role | Intent |
|---|---|
| Admin (on project) | Full control of this project’s settings and membership |
| Editor | Build tables, spinners, and run work |
| Viewer | Read outcomes and analytics without changing setup |
| Guest | Limited access for a narrow task |
Organization Admin can usually manage membership even when they are not listed day-to-day as an operator.
Why this matters for operators
Section titled “Why this matters for operators”- Privacy — contractors only see projects they are staffed on
- Clarity — Records and Jobs stay scoped to the project you opened
- Safety — fewer people can publish or delete automation by accident
If someone “cannot see the project,” check both:
- Are they an active user in the organization?
- Are they a member of that project (or an org Admin)?
Success looks like
Section titled “Success looks like”- The right teammates appear under project Settings → Members
- Non-members do not find the project in their list (unless they are org-wide admins)
- Editors can build and run; viewers can review outcomes without changing pipelines
Common problems
Section titled “Common problems”| Symptom | Likely cause | What to do |
|---|---|---|
| User missing from project list | Not invited to the project | Invite member from Settings |
| User cannot open Settings | Project role is view-only | Elevate project role or use an org Admin |
| Invite does nothing useful | Person not in the organization yet | Invite them under Manage users first |
| Too many people see sensitive data | Broad membership | Remove members who no longer need access |