Colors and logos
Apply business colors and logos across client-facing details and workspace presentation.
Branding & Public Workflows
Brandable client-facing workflows
Use client-facing surfaces for requests, proposals, shared records, and public workflows that should feel connected to your business.
- 01
- Support public intake and request workflows.
- 02
- Share client-facing materials without exposing internal operations.
- 03
- Keep brand context close to proposals, forms, and shared links.
client portal branding
What is client portal branding?
Client portal branding applies a business identity to the forms, documents, links, and shared experiences customers use. Workspace369 keeps those presentation choices connected to proposals, requests, public workflows, invoices, portals, and workspace settings.
Product reference
Reviewed July 17, 2026 by the Workspace369 Product Team. Availability can vary by plan, region, and workspace configuration.
What it covers
Your brand on every client-facing surface.
Branding in Workspace369 keeps colors, logos, and presentation choices connected to the proposals, forms, and links clients actually see.
Branded public forms
Support public intake and request workflows that feel connected to your business.
Proposal and invoice presentation
Carry business identity into proposals, estimates, invoices, and PDF output.
Shared links and portals
Share client-facing materials through links and portal surfaces without exposing internal operations.
Internal operations stay private
Present intended work while internal notes, unrelated accounts, and team controls remain private.
Built into the operating flow
Move from first signal to completed work with context intact.
Branding connects with public forms, proposals, client portals, shared links, and workspace settings.
- 01
Start with the right record
Support public intake and request workflows.
- 02
Move the work forward
Share client-facing materials without exposing internal operations.
- 03
Keep the result visible
Keep brand context close to proposals, forms, and shared links.
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
Support public intake and request workflows.
Use client-facing surfaces for requests, proposals, shared records, and public workflows that should feel connected to your business.
Product view 02
Share client-facing materials without exposing internal operations.
Branding connects with public forms, proposals, client portals, shared links, and workspace settings.
1TriggerClient activityAutomated
2ConditionMatch the right recordChecked
3ActionContinue the workflowNext
Product view 03
Keep brand context close to proposals, forms, and shared links.
Make client-facing workflows feel intentional.
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
Examples
Branded workflows teams repeat.
These examples show how branding moves through connected client-facing work. They are product workflows, not promised business outcomes.
Branded Client Intake
- 1Publish a branded public request form
- 2Apply business colors and logo
- 3Collect client information outside the workspace
- 4Review the request against the client record
- 5Start the workflow from a branded intake
Branded Proposal Delivery
- 1Prepare the proposal for the client
- 2Apply brand styling and presentation
- 3Share it through a client-facing link
- 4Confirm internal records stay hidden
- 5Move the client toward approval and payment
Common operating scenarios
Make the client experience feel connected to the business.
These examples describe how the feature fits into connected client work. They are product workflows, not promised business outcomes.
Create a recognizable intake experience
Use branded public forms and request workflows so a new client can provide information without entering the internal workspace.
Present proposals and documents consistently
Carry business identity into the proposal, estimate, invoice, or PDF output that moves the client toward approval and payment.
Share records without exposing operations
Use client-facing links and portal surfaces to present the intended work while internal notes, unrelated accounts, and team controls remain private.
Where it connects
One record can carry the work forward.
Branding connects with public forms, proposals, client portals, shared links, and workspace settings.
Common questions
Branding & Public Workflows questions
Which Workspace369 experiences can use branding?
Branding can apply to relevant proposals, documents, public forms, request workflows, shared links, client-facing details, and workspace presentation controls.
Can a branded link hide internal workspace records?
Yes. Public and client-facing workflows are designed to share the intended record or action without granting access to unrelated internal workspace content.
Does branding stay connected to the client workflow?
Yes. Workspace369 treats branding as part of proposals, forms, portals, documents, requests, invoices, and shared client records rather than as a separate website builder.
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.