Client portal

What's inside

Client overview: projects, what's waiting for review and what's to pay. Project pages with deliverables, files, invoices and a message thread. Reviews: approve or ask for changes, with a kept record of every decision. Files shared both ways, invoices with payment links and overdue flags. Agency pages for clients, client contacts, client access and the studio team.

How its workflows run

Each one is a server workflow in your project: it runs on its trigger, with retries, and its runs show in the builder's log.

1. Stamp a message and tell the other side

   When a row changes: message created. Then: Look up project, then Update message, then Notify, then Send email.

2. Ask the client to review a new deliverable

   When a row changes: deliverable created. Then: Look up project, then Update deliverable, then Create message.

3. Apply a client's review

   When a row changes: approval created. Then: Look up deliverable, then Update approval, then Create message.

4. Stamp a shared file

   When a row changes: shared_file created. Then: Look up project, then Notify, then Update shared_file.

5. Email a new invoice to the client

   When a row changes: invoice created. Then: Send email.

6. Flag overdue invoices and remind

   On a schedule: schedule daily 09:00 over invoice. Then: Look up invoice, then Update invoice, then Send email, then Notify.

7. Thank the client when an invoice is paid

   When a row changes: invoice updated, when status is paid. Then: Update invoice, then Send email.

8. Weekly review summary for the studio

   On a schedule: schedule weekly fri 16:00 over approval. Then: Send email.

Set it up

It starts a new project, with its data, roles and sign-in ready.

1. Start the project

   Use the button above, or ask your coding agent with the Appbricx MCP server connected (quickstart).

2. Sign in as each role

   The demo logins open each role's home. Change what you like in plain words or in the contract.

3. Deploy

   When dev looks right, deploy. Production gets a snapshot first, so you can roll back.

Use it with your coding agent

The agent creates the project, builds it and signs in as each role.

Start a new Appbricx project from the Client portal template (slug "client-portal") with use_template. Call it "My Client portal", then sign in as each role, verify it and tell me what to change first.

{
  "tool": "use_template",
  "arguments": {
    "slug": "client-portal",
    "name": "My Client portal"
  }
}

appbricx templates use client-portal --name "My Client portal"