Client portal

A portal your clients actually open

A separate login, tied to a contact, that starts with no access at all. Switch on tickets, replies, project tasks and file uploads one at a time — and nothing else is reachable.

app.aspirepro.io/portal
The AspirePro client portal dashboard showing a client's open tickets and visible project tasks

Client portal software gives your customers a place to sign in and work with their own records — requests, projects, files — without access to your internal system. The security model is the whole product: a portal that leaks another client's ticket, or your internal notes, is worse than no portal at all. AspirePro portal users are a separate kind of account that can do nothing until you allow it, limited to their own companies.

Nothing by default

Off until you switch it on

A portal user starts with no abilities. Viewing, creating, replying, changing status and each project action are granted one by one.

Walled off

Not a staff account with less access

Portal logins are a separate kind of sign-in. Staff logins cannot reach portal pages and portal logins cannot reach yours.

Real work

More than a status page

Clients can open tickets, reply, tick off tasks, comment and upload files — wherever you have allowed it.

Tickets

Their tickets, and only theirs

A client sees the tickets belonging to their own companies, on the boards you allowed — and nothing else. They can search, filter open and closed, open a ticket to read the customer-facing conversation, and reply into the same thread your team is working.

  • Limited to the client's companies, and to the boards you list
  • Internal notes never appear — only the customer-facing conversation
  • Optionally limit a client to tickets they personally raised
  • Their reply lands on the same ticket, in the same thread, in your queue
app.aspirepro.io/portal
The client portal ticket list showing the client their own tickets with status and last activity
New requests

Let them raise a request properly

A short form — category, subject, description — creates a real ticket on the right board with the client already attached. No shared inbox, no "did anyone see this email?", no request that exists only in someone's sent items.

  • Creates a real ticket on the board you route that category to
  • The client and their company are set automatically
  • Creating tickets is its own permission — allow viewing without creating if you prefer
The client portal new ticket form with category, subject and description fields
Let them raise the request properly
Projects

A project view, not a progress bar

Where you allow it, the client gets a simplified board of the project tasks you marked visible: completion, due dates, open work and the columns. Depending on what you switch on, they can add tasks, tick them off, comment, run a checklist and upload files — and it all lands on the same task your team is working.

  • Each task, comment and file is invisible until you mark it
  • Separate permissions for creating, editing, completing and moving tasks
  • Their comments and uploads appear on your side of the same record
app.aspirepro.io/portal
The client portal project view with To Do, In Progress and Done buckets of client-visible tasks
Access

Managed from the contact record you already keep

Your team grants portal access from the contact it belongs to: invite them, choose exactly what they can do, pick their boards and projects, and switch them off the moment they leave. It is a card on a record your team already maintains, not a separate admin chore.

  • Invite by email with a one-time activation link — you never handle their password
  • Abilities, boards and projects all set here
  • Optionally show a client the hours used and left on a prepaid block
  • Deactivate instantly; the company itself must also be portal-enabled
app.aspirepro.io/portal
A contact record in AspirePro showing the client portal access card with a manage action
Branding

Your name on the door, and a wall between the two

The portal signs in at its own address under your organization's AspirePro address, carrying your logo and name. There is no route from a portal session into your internal pages — the separation is enforced by a different kind of sign-in rather than by hiding menu items.

  • Your logo and organization name on the sign-in page and throughout
  • Self-service password reset that never touches your staff accounts
  • A separate sign-in: portal sessions simply cannot reach staff pages
The client portal sign-in page branded with the organisation logo
Branded, and separate by design
How it works

Standing a portal up

1

Switch the company on

Portal access is opt-in per client company, so turning the module on exposes nothing by itself.

2

Invite the contact

From their contact record, send an invitation. They set their own password through a one-time link.

3

Choose what they can do

Tick exactly what they may do — view tickets, reply, create, change status, and each project action.

4

Choose what they can see

Pick the boards and projects they can see, and mark the tasks, comments and files you want visible.

Questions

Frequently asked questions

What is client portal software?
A client portal is a secure area where your customers sign in to see and act on their own records — support tickets, project work, files — without any access to your internal system. For a services business it removes the "can you send me an update?" email loop while keeping a hard boundary around everything else.
How is the portal kept separate from our internal system?
Portal users are a different kind of account with a different sign-in, tied to a contact rather than to a staff user. Staff sessions cannot reach portal pages and portal sessions cannot reach staff pages. That separation is built into the sign-in itself, not a matter of hiding navigation.
What exactly can a client see?
Only what has been granted, limited to the companies their contact belongs to. Tickets are further limited to the boards you list, and can be narrowed to tickets they raised themselves. Internal notes never appear. In projects, individual tasks, comments and files must each be marked visible.
Can clients do more than look?
Yes, where you allow it. Each action is a separate permission: opening tickets, replying, closing or reopening their own ticket, and — in projects — creating, editing, completing and moving tasks, managing columns, running checklists, commenting and uploading files.
How do clients get access?
Your team invites them from the contact record. The invitation carries a one-time link the client uses to set their own password, so nobody on your side ever handles their credentials. Access can be switched off instantly from the same card.
Is the portal branded?
It carries your organization name and logo on the sign-in page and throughout, and lives under your organization's address, so it reads as your portal rather than a third-party tool.
Do I have to give every client a portal?
No. The module is a toggle, each client company must be opted in individually, and each contact needs their own invitation. Most firms start with a handful of clients who ask for it.
Documentation

Read the documentation

The full how-to for this module, written for the people who use it every day.

Bring your whole services business together

Stop stitching together five tools. Run sales, delivery, support, and billing from one organization — with an AI assistant on every page.