Client Portal
The Client Portal is the customer-facing account experience for support issues
and requests. Operators can preview it from Clients → Portal Preview and
configure it from Clients → Portal Settings.
Current Status
Portal Settings
Portal settings are stored on workspace settings and require customers.write to save.
Settings include:
- Enablement.
- Portal name.
- Logo URL.
- Accent color.
- Header links.
- Footer link sections.
- Default access behavior.
- Visible and editable issue fields.
- Customer-facing issue status labels.
- Customer-facing task status labels.
- Customer-facing forms.
- Custom domain and DNS record display.
- OTP or custom-auth URL mode.
Experience Settings
Use portal experience settings to control:
- Enablement.
- Portal name.
- Horizontal logo URL.
- Accent color.
- Header links.
- Footer link sections.
Client Portal is plan-gated. When the selected plan does not include it, Woes
shows the lock state in the settings panel.
Data Settings
Use data settings to choose the customer-facing portal shape:
- Which issue fields customers can see.
- Whether each non-system field is view-only or editable.
- Customer-facing labels and colors for issue statuses.
- Customer-facing labels and colors for task statuses.
- Which request forms are enabled.
Access Levels
Portal Issues
Portal-visible issues use the same issue model as Woes support issues. Portal routes return customer-safe issue fields and customer/support message roles.
Public portal access depends on a valid portal session. In non-production environments, a development session header may be used for testing.
Customers with access can create portal issues. Portal-created issues enter the
workspace issue queue with source_channel = client_portal and customer-safe
metadata.
Public portal access still depends on production routing, email delivery, and
workspace configuration. Do not promise a custom-domain launch until the DNS
and deployment setup are verified for that workspace.
