> For the complete documentation index, see [llms.txt](https://guides.noloco.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.noloco.io/solutions/agency-os/client-portal.md). # Client Portal > The Client Portal gives your clients a professional, real-time window into their projects and invoices — without exposing a single piece of your internal data. ## What clients see When a client logs in, they see four pages — and nothing else: | Page | What it shows | | ------------------- | ----------------------------------------------- | | **Portal Home** | Welcome page with action cards | | **Projects** | Their projects and tasks | | **Tasks** | Their tasks across all projects | | **Client Invoices** | Their invoices — filtered to their company only | Everything else in Agency OS — CRM, Team, Team Workload, Revenue Dashboard, Team Billables, Team Expenses, other clients' data, hourly rates, budget health figures — is completely hidden. Not just restricted. Not visible at all. {% hint style="info" %} **Use the portal in sales demos.** Before a prospect signs, show them what their client experience will look like. Seeing a branded, real-time project view is often what closes the deal. It signals that your agency is organised, transparent, and professional — before the work has even started. {% endhint %} *** ## Portal Home The Portal Home is the client's welcome page. It greets them by name and gives them three action cards to navigate from: 1. **View Projects** — "See the latest updates on the projects we're working with you" 2. **Pay Your Bills** — "View your past and upcoming invoices" 3. A third card for quick actions (configurable in Build Mode) Below the action cards, clients see their ongoing tasks — a live snapshot of what your team is currently working on for them. *** ## Projects Clients see a list of their projects — active, planned, and completed. Each project shows its name, status, timeline, and team. Clicking into a project opens the project record, showing: * Project details and description * All tasks for this project, with status, assignee, priority, and due date * **Reply comments** from your team (client-visible) * **Not Notes** — internal comments are completely hidden Clients can click into individual tasks to read full descriptions, see current status, and add their own Reply comments — questions, feedback, approvals. **What clients can do:** * View projects and tasks * Add Reply comments on tasks * See deliverables attached to tasks (File field) **What clients cannot do:** * Create or edit projects or tasks * Change task status or assignments * See internal Notes * See any other client's data * See team workload, rates, or budget health *** ## Client Invoices Clients see their invoices in the Client Invoices page — filtered automatically to their company. They can view: * Invoice status (Pending / Overdue / Paid) * Full line item breakdown * Due dates and amounts If Stripe is connected, clients can pay directly from the portal. Set up in Settings → Integrations → Stripe. *** ## Granting portal access ### Step 1: Make sure the company is a Client The client's Company record must have Status = "Client". If they came through CRM, this is already done when you won the deal. ### Step 2: Add the contact On the Client record → Details tab → Contacts section, add the person who should have portal access. Their email address is required. ### Step 3: Invite them as a user From the Contact record, invite them to Agency OS and assign the **Client** role. They'll receive an email with a login link. The Client role is pre-configured — it restricts access to the portal pages only and filters all data to their company automatically. ### Step 4: Enable Google Sign In (recommended) Clients can log in with their Google account — no separate password to manage. This reduces friction at onboarding and means clients don't abandon the portal because they forgot their password. Set up in Settings → Integrations → Google Sign In. ### Step 5: Test before you send Use **"View as \[Client Name]"** (click your profile icon → View as) to see Agency OS exactly as that client sees it. Check: * Only their projects visible? * Only their invoices visible? * No internal Notes showing? * No team cost data visible? Only invite the client once you've confirmed everything looks right. *** ## Reply vs Note — the most important rule Every comment in Agency OS is either a **Reply** (client-visible) or a **Note** (internal only). This distinction is what makes the portal safe to use. **Use Reply for:** * Progress updates ("The homepage design is ready for your review") * Questions for the client ("Could you confirm the copy by Friday?") * Deliverable notifications * Responses to client questions **Use Note for:** * Internal team coordination * Budget concerns * Technical blockers * Anything you wouldn't say directly to the client {% hint style="warning" %} **Always check before posting.** A Reply posted by mistake is visible to the client immediately. If it happens, edit or delete the comment as quickly as possible and switch to Note. {% endhint %} *** ## Key concepts | Concept | How it works | | ------------------ | --------------------------------------------------------------------------------------------- | | **Data filtering** | Clients only see data linked to their company — automatic, no manual configuration per client | | **Client role** | Pre-configured permissions — view only, no editing, portal pages only | | **Reply** | Client-visible comment on a task or project | | **Note** | Internal-only comment — never visible to clients | | **Google Sign In** | Native integration — clients log in with their Google account | *** ## Make it yours The portal works securely out of the box. When you're ready to enhance it: * **Add your branding:** Upload your agency logo, set brand colours, and add a custom domain (your-portal.youragency.com) in Settings → General. * **Enable Google Sign In:** Reduce login friction for clients — Settings → Integrations → Google Sign In. * **Customise the Portal Home:** In Build Mode, edit the welcome message, adjust the action cards, or add a meeting booking link. * **Automate client notifications:** Use Noloco's Slack integration or Zapier/Make to email clients when a task is marked Done, or when a new invoice is available. See [Customising Your Agency OS](/solutions/agency-os/customizing-your-agency-os.md) for the full guide. *** ## Tips **Set up the portal before the project kicks off, not after.** Sending a client their portal login on Day 1 sets the tone — it signals that your agency is organised and that they'll always know what's happening. **Walk new clients through the portal in your kickoff call.** A 5-minute screen share ("here's where you'll see your tasks, here's where invoices live") means they'll actually use it. Clients who never log in don't get the benefit. **Keep task statuses current.** The portal is only as useful as the data in it. A client who logs in and sees all tasks as "To Do" will go back to emailing for status updates. **Test "View as" regularly.** Do a quick "View as" check before any client meeting or check-in — it takes 30 seconds and ensures you're not surprised by what they've been seeing. *** ## What's next? With your client portal configured, explore how to tailor Agency OS to your agency's specific workflows. Head to [Customising Your Agency OS](/solutions/agency-os/customizing-your-agency-os.md) for the full guide on Build Mode, integrations, and optional extensions. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://guides.noloco.io/solutions/agency-os/client-portal.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.