Cleared by IT, workable for agencies
Giving a client access to one project and nothing else
A guest sees one project, read-only, and cannot reach anything else by link, search or notification. The role is free on every plan, and here is exactly what it can and cannot do.
What a guest sees
One project: its issues, comment threads, attachments, status and due dates. The project reads the same way it does for the team, without an exported summary or a duplicate board maintained alongside the real one.
- Open issues and their full comment history.
- Attachments on the issues they can see.
- Status and due dates, updated as the team updates them.
- The project's own activity feed.
What a guest cannot do or reach
- Comment, or be assigned work. Those require a seat.
- See any other project, including by direct link. A URL to another project returns not found rather than a permission prompt, so the existence of other work is not disclosed.
- Appear in search results, mention autocomplete, or notification recipients for any other project.
- See the portfolio rollup, team membership, or time entries.
- See internal comments. A comment marked internal is invisible to guests on the issue they are reading.
The internal comment
Any comment can be marked internal at the moment it is written. It stays on the issue, in thread order, visible to seats and absent for guests. There is no separate internal issue to keep in sync.
This is the mechanism that makes a single shared project workable for client-facing work. The alternative, a client-facing copy of each project maintained by hand, is the thing the guest role exists to remove.
How an agency usually sets it up
One project per client engagement, the client's contacts as guests on that project, and the agency's own team as seats across all of them with the portfolio rollup spanning every engagement.
Contractors working on a subset of engagements take contractor seats, scoped to named projects, at half rate on Business and above.
| Who | Access | Count | Monthly |
|---|---|---|---|
| Agency team | full seats, portfolio rollup | 10 | $190 |
| Freelancers | contractor seats, named projects | 6 | $57 |
| Client contacts | guests, one project each | 24 | $0 |
| Total | 40 people | $247 |
Changing someone's access
A guest promoted to a seat keeps their comment history visibility and gains the ability to post. A seat demoted to guest loses posting immediately, and their past comments stay in place attributed to them.
Access changes take effect on the next page load, not on the next session, so removing a guest ends their access immediately.
Frequently asked questions
Can a client log in and see only their own project?
How do we discuss a client's project without the client reading it?
What does a twelve-client agency actually pay?
More in Cleared by IT, workable for agencies
- What Cadenta's SOC 2 report covers, and where our data livesThe scope of the report, the regions you can choose, and what happens to your data when you leave.
- Cadenta vs Momentro when the team includes contractorsMomentro prices per workspace and Cadenta prices per seat, so the comparison turns on how many occasional people you carry.