Approvals and the client portal
Request formal decisions and give clients a clean, limited view of deliverables.
An approval turns a conversation into a record. Instead of inferring agreement from silence or a reply in a thread, you get a named decision attached to the work.
Request a named approval
Ask a specific person for a decision rather than posting for general comment. The approver can be a teammate for internal quality control or a client for external sign-off, and both use the same mechanism. Naming the approver removes the common failure where several people comment and none of them actually decides.
Keep the decision auditable
Every outcome is either Approved or Changes requested, and it carries a note, the person who decided, and a timestamp. That record sits on the task and is written to the audit log, so a scope discussion later starts from evidence rather than from memory or a screenshot.
Share only what clients need
Guests are invited to specific projects, not to your workspace. They open a branded portal showing the work you shared and nothing else. Internal boards, other clients, team queues, and your custom fields do not render for them, so there is nothing to expose by accident.
Set the right access level per guest
Each share carries View, Comment, or Approve. Give Approve only to the person who genuinely holds sign-off authority, and Comment to stakeholders who should be heard but not decide. The server enforces this, so a client without Approve cannot approve even if they find the page.
Automate the request, not the decision
A rule can request approval automatically the moment work reaches your client review stage, which removes the delay caused by someone forgetting to ask. The decision itself stays human. Automating the request is what shortens cycles, and automating a decision would defeat the point of having a record.
Worth remembering
- Ask for approval on the deliverable task, so the decision and the work stay together.
- Changes requested should always carry a note. A rejection without a reason costs another round.
- Approvals, guest Approve access, and the branded portal are available on Studio and above.
Common questions
No. Access is scoped to the specific projects shared with that guest.
The task returns with the note explaining what to change, so the next round starts from a written requirement rather than a recollection.
Related guides
Ready to apply this?
Bring a real project into Trellis with guided onboarding, or ask us anything about your setup.