Portal console
The one page your team runs the client portal from — the review queue, portal users, and the form template inspector, with the tiles doubling as filters.
CRM → Client portal is where your team runs the portal: who has access, what you have asked for, and what has come back. Anyone with CRM access can open it and read the state of the portal; the actions that change something — inviting, suspending, removing, sending requests — require the portal-manage permission, and appear disabled without it.
The page is built around one idea: the portal has a single job queue — submissions waiting for a human — and everything else is setup around it. So the queue is what you land on.
The tiles are the filters
The four tiles state a number and then hand you the view that number came from:
- Active portal users — of everyone invited → the users list.
- Awaiting review — submitted by clients → the review queue.
- Pending requests — waiting on the client → the request tracker.
- Form templates — available to send → the template inspector.
The three views
Form requests
The landing view, sorted by what is actually blocking someone: submitted first, then changes requested, then pending, with approved last. Each row carries the request title and template, the portal user, its status, its due date (in red and marked overdue when it has passed), and when it was created.
Status chips above the table filter it further and carry their own counts, and the search box matches request title, portal user, and template. Click any row to open the review page.
Portal users
Every contact with portal access: name, sign-in email, status (Active, Invited, Suspended), and last sign-in. Row actions follow the status — Send form request for active users, Copy invite link for invited ones, Reactivate for suspended ones — with resend, suspend and remove in the overflow menu.
Form templates
A read-only inspector. Pick a template on the left to see its Fields — every field with its type and whether it is required, grouped by section — and a Client preview showing the form exactly as the client will see it. Search matches template names and field labels, which is the quickest way to answer "which form asks for the VAT number?"
The two header actions
- Invite contact — search a CRM contact, confirm the email they will sign in with, and send an activation link. They set their own password; nothing internal is exposed by the invitation.
- Send form request — pick an active portal user and a template, then optionally set a title, a due date, and a message.
Tips
- Suspend rather than remove for staff turnover at a customer. Suspending keeps their submission history and can be undone; removing cannot.
- If Copy invite link says no token is available, use Resend invitation first, then copy.
- Open a template's Client preview before sending it for the first time.
Related
Learn more about the client portal →