Client records
Track client history, contact details, job context, and related files in one place.
CRM & Requests
Clients, requests, portals, and public forms
Keep the client record at the center of every request, project, message, file, invoice, and payment.
- 01
- Capture leads and requests through forms and public workflows.
- 02
- Track client history, contact details, job context, and related files.
- 03
- Share the right information with clients without exposing the whole workspace.
client portal software
What is client portal software?
Client portal software gives customers a secure place to view and act on shared work. Workspace369 connects that experience to client records, requests, projects, files, approvals, invoices, payments, and communication instead of treating the portal as a separate destination.
Product reference
Reviewed July 17, 2026 by the Workspace369 Product Team. Availability can vary by plan, region, and workspace configuration.
Read the client and CRM documentationWhat it covers
One record from first contact to payment.
The client portal keeps people, companies, requests, and shared information connected to the work around them.
Requests and follow-up
Capture and manage client requests from first message to resolution.
Public forms
Capture leads and requests through forms and public workflows.
Client portal
Share invoices, payments, files, and project status without exposing the whole workspace.
Connected handoff
Turn requests into projects, calendar events, estimates, proposals, and invoices.
Built into the operating flow
Move from first signal to completed work with context intact.
Requests can become projects, calendar events, tasks, estimates, proposals, invoices, and inbox conversations.
- 01
Start with the right record
Capture leads and requests through forms and public workflows.
- 02
Move the work forward
Track client history, contact details, job context, and related files.
- 03
Keep the result visible
Share the right information with clients without exposing the whole workspace.
Inside Workspace369
See how the feature fits into day-to-day work.
Follow the record through the views teams use to act, review progress, and keep the next step clear.Product view 01
Capture leads and requests through forms and public workflows.
Keep the client record at the center of every request, project, message, file, invoice, and payment.
Product view 02
Track client history, contact details, job context, and related files.
Requests can become projects, calendar events, tasks, estimates, proposals, invoices, and inbox conversations.
1Record updatedContext stays attached to the work.Now
2Team follow-upContext stays attached to the work.3m
3Client notifiedContext stays attached to the work.4m
Product view 03
Share the right information with clients without exposing the whole workspace.
Use Workspace369 as the source of truth for people, companies, and jobs.
1TriggerClient activityAutomated
2ConditionMatch the right recordChecked
3ActionContinue the workflowNext
Examples
How client work moves through the portal.
These examples show how requests become connected client work. They are product workflows, not promised business outcomes.
Lead Intake to Project
- 1Lead submits a public form
- 2Request appears on the client record
- 3Team reviews and qualifies
- 4Send an estimate or proposal
- 5Convert to a project on acceptance
Portal Approval Flow
- 1Share a proposal with the client
- 2Client reviews it in the portal
- 3Approval is recorded on the record
- 4Collect the deposit where configured
- 5Delivery starts from the same record
Common operating scenarios
Use a client portal without separating it from delivery.
These examples describe how the feature fits into connected client work. They are product workflows, not promised business outcomes.
Turn intake into organized work
Capture a request through a public form, match it to the correct client, and carry the same details into a project, estimate, task, or conversation without starting over.
Share progress with the right client
Give clients access to the records and actions intended for them while internal notes, unrelated accounts, and operating details stay inside the workspace.
Keep billing close to the relationship
Place proposals, invoices, payment activity, files, and request history beside the client record so the next financial or operational step is easier to understand.
Where it connects
One record can carry the work forward.
Requests can become projects, calendar events, tasks, estimates, proposals, invoices, and inbox conversations.
Common questions
CRM & Requests questions
What can clients access through Workspace369?
Workspace369 can support client-facing access to requests, shared records, files, proposals, invoices, payments, projects, and communication based on the workflow and access configuration in use.
Does the client portal connect to CRM records?
Yes. Portal activity is designed to stay connected to the relevant client, company, request, project, file, invoice, payment, and conversation context.
Can teams limit what each client sees?
Yes. Workspace369 separates client-facing access from internal workspace access so teams can share the intended records without exposing unrelated clients or internal operating details.
What can clients see in the portal?
Teams can share invoices, payments, files, requests, projects, communication, approvals, and account history without exposing the whole workspace.
Work from one connected system
Bring this workflow into the rest of Workspace369.
Start free and bring this workflow into the rest of your workspace.