Trello Guests vs Members: Plan Client Access and Billing

Digital Business / Client collaboration / Practical guide

For a client who needs one project board, consider a Trello guest rather than Workspace membership. A guest is still a normal board editor by default. If the client should review without editing, assess the observer permission available in Premium Workspaces, and check billing separately before inviting them.

The right setup depends on three decisions: what information the client should see, what actions they should perform, and how many boards they need. Treat those as separate questions. A label such as “guest” does not answer all three.

01 / Membership and permissions answer different questions

Atlassian defines a Workspace guest as someone who belongs to a board but not to the Workspace containing it. Invite the person to the board without adding them to that Workspace, and they are a guest there. This can suit an external collaborator with a specific project.

Workspace membership is a broader relationship to the collaboration space. Board permissions determine what someone can do on an individual board. Review both rather than treating “member” as one universal permission level.

For example, a long-term internal project coordinator and an occasional external reviewer may need different membership arrangements even when they look at the same deliverable. Document the business reason for access before choosing a role.

02 / Use the board as the client information boundary

Trello’s guest documentation states that people invited to a board can see its cards; there is no setting that hides selected cards from particular board members. Do not put several clients on one board and assume assigning each to a card separates their access.

Design the shared space around what everyone invited may see. Before reusing an internal board, inspect card descriptions, comments, checklists, attachments, and linked resources. A clean board made for client communication is often easier to review than an internal board with years of accumulated material.

Check visibility as well as membership. Atlassian’s visibility guidance says private boards are visible to their board members and, in paid Workspaces, Workspace admins. Workspace-visible boards have a wider internal audience; public boards are visible to anyone on the internet with the link.

For confidential client work, select an appropriate private setup and review the organization’s administration rules. “Private” should not be explained to the client as excluding the organization’s authorized administrators.

Links to external documents deserve their own permission review. For a broader handoff checklist, see our secure file-sharing guide. A board invitation should not be treated as proof that the linked file has the right audience.

03 / Choose between editing and reviewing

Use normal board participation when the client should maintain tasks directly. Examples include supplying a brief, updating a shared checklist, or moving work through an agreed process. Explain which actions belong to the client and which remain with your team.

For review-only participation, Trello Premium offers observers. They can view the board, download attachments, export it, and comment or vote when those functions are enabled. They cannot edit or move cards, upload attachments, complete checklist items, or change board settings.

Observer permission is not a ban on copying information. Review every attachment with that in mind. It is also not a separate guest category: both a guest and a Workspace member can have observer permission on a board.

If the client must upload new files or maintain checklist items, observer access will not meet that requirement. Choose an editing arrangement with suitable content boundaries, or agree a separate submission channel. Do not promise a review workflow that depends on actions the selected role cannot perform.

Write down the required actions before paying for an upgrade. A requirement such as “client can read and comment, but cannot rearrange tasks” is easier to evaluate than “we need professional collaboration.”

04 / Count boards and seats before sending invitations

For Standard and Premium, a guest on two or more boards in the same Workspace becomes a billable multi-board guest, charged at the Workspace-member rate. A one-board guest is non-billable. Enterprise has different guest licensing rules, so do not extend this comparison to that plan.

Trello’s billing guidance distinguishes membership from observer permissions. Review the Workspace’s Members and Guests lists alongside its billing record. Use the applicable centralized billing documentation if that is the billing system your account uses.

Consider a hypothetical client already participating on a delivery board. Inviting the same person to a second planning board in that Standard or Premium Workspace changes the seat calculation. Keeping them as an observer does not avoid that change. Record the second-board request as a business decision rather than an incidental invitation.

Free Workspaces have a different limit

Free Workspaces are limited to 10 collaborators, counting Workspace members, guests, and pending invitations. That is a Workspace-wide limit, not ten new people per board. A free guest is still part of that count.

Check the current subscription, seat availability, billing cycle, local price, and applicable taxes before approving an upgrade or additional seat. This guide does not quote a universal monthly total because the useful calculation depends on the actual Workspace and people involved.

05 / Prepare a small, deliberate first invitation

Start with one board and one confirmed client contact. Have an internal owner review the content before access is granted. Avoid using a live client invitation as the first experiment with your board structure.

1. Confirm the audience. Record the client’s agreed email address, project, and internal sponsor.
2. Inspect the board. Remove internal-only material from the client-facing space and check its visibility.
3. Choose the actions. Decide whether editing is needed or observer access fits the task and plan.
4. Review membership and cost. Check existing boards for that person in the Workspace and obtain any required seat approval.
5. Send the specific invitation. Use the board’s sharing controls, check the selected identity and role, and then confirm the resulting membership.
6. Verify the experience. Ask the invited contact to confirm the board opens and the agreed actions work. Use harmless sample content for the first check.

Atlassian documents board invitations through Share, including choosing the person and their board permission. Workspace restrictions or board settings may limit who can invite, so involve the responsible administrator if the controls differ.

Keep a simple access register: client, email, board, permission, internal owner, purpose, and review date. The register does not replace Trello’s membership lists, but it makes the next access review much easier to organize.

06 / Agree how client feedback becomes a decision

Access alone does not create a usable client process. Add a short welcome card explaining where to find deliverables, how to leave feedback, who answers questions, and what counts as approval. Keep the instructions specific to the service.

A practical review card can contain the deliverable’s version, a link to the approved file, the question requiring a decision, and a named reviewer. For example, “Confirm the headline for version 3” is clearer than “Please review.” This is an editorial workflow suggestion, not an automatic Trello approval feature.

Decide who updates the final status after feedback. If the client is an observer, your internal owner must handle actions that require editing. If the client is an editor, still agree who records the authoritative decision to avoid contradictory changes.

For documents held in Google Drive, establish who controls them and how the team retains access. Our shared drive vs shared folder comparison covers that separate ownership decision.

Do not combine unrelated client information just to reduce board count. If safe separation requires another board and a billable seat, compare that cost with an alternative workflow that still protects the information and supports the work.

07 / Close access and check the handoff

At completion, agree what the client should retain and how long collaboration should continue. Confirm final documents are available through the intended handoff process before removing temporary participation.

Removing someone from a board removes their card membership there while leaving actions such as comments and completed checklist items. Atlassian also notes that their automations are removed, so review any workflow dependencies before offboarding.

Check every relevant board, the Workspace membership record, and external file access. Review billing after the change; removal should not be described as an automatic immediate refund. Keep the final decision and ownership record with the project.

• The client-facing board contains only approved shared material.
• The person’s membership, board permission, and billing status are understood.
• A named internal owner manages feedback and final status.
• Access has a review date and an end-of-project handoff.

Frequently asked questions