What are client portal forms?
A definition of client portal forms for MSPs, IT teams, and automation teams using portals for structured request intake and approvals.
Client portal forms are forms available inside a customer or client portal. They let a client submit structured requests, choose from assigned forms, provide approvals, and send context-rich payloads into a service or automation workflow without relying on email threads or scattered public links.
Why client portal forms matters
A public form link often lacks customer identity, organization membership, and submission history. Client portal forms keep the request tied to the right client and can attach the mappings a workflow needs before it runs.
The term points to a real workflow requirement.
- A client should choose from assigned request forms instead of receiving separate public links.
- The form needs organization membership, tenant context, or customer-specific integration mappings.
- Submissions should create tickets, trigger onboarding, request access, route approvals, or update workflow systems.
- The same form pattern should work across many clients while preserving client isolation.
Frequently asked questions
What are client portal forms used for?
Client portal forms are used for ticket intake, onboarding, offboarding, access requests, license requests, service requests, approval decisions, and other customer-facing workflows.
How are client portal forms different from public forms?
Client portal forms are scoped to a client or organization. They can use portal membership, assigned forms, submission history, tenant mappings, and approval visibility that public links usually do not provide.
Can client portal forms use live dropdowns?
Yes. FormNode client portal forms can use dynamic dropdowns backed by n8n webhooks, PSA/RMM APIs, Microsoft 365 data, or other HTTPS endpoints.