This article describes what your client sees and can do in the portal — useful for setting expectations before you send the link, or for walking a client through it on a call.
What your client receives
Your client gets an email notification with a magic link. No account creation or login is required. The link opens directly into the review view for your project.
The link is unique to the specific client contact, so Glossa can track who approves or makes comments.
The magic link is valid for 7 days. If it expires, you can resend it from your Glossa workspace.
What the portal looks like
The client portal is a clean, minimal view — it shows only what they need to review. Requirements are organized by category (e.g., "Donor Management," "Reporting") so clients can work through them section by section.
For each requirement, the client sees:
The requirement title
The requirement description
Any user stories ("As a [role], I want to [action] so that [outcome]") associated with that requirement (note that checklist acceptance criteria associated with user stories are not displayed in the portal)
The status
Any existing external comments
What clients can do
Approve — The client can mark a requirement as Approved. This is recorded in Glossa with a timestamp and the client's name.
Flag — If the client has a concern, question, or disagreement, they can flag the requirement. You'll be notified immediately.
Discuss — Clients can comment on individual requirements. You'll be notified and can respond. Comments appear in the external comment thread on the requirement.
What clients cannot do
Edit requirement text directly
See internal comments between your team members
Access any other part of your Glossa workspace
Approve or modify requirements in bulk (each requirement is reviewed individually)