Client Portal — administrator hub

This page is for root administrators and integrators who enable Client Portal for end users: portal URL, self-registration, portal-only role, and registration form fields.

End users work in the separate Support Portal app — their guide: end-user hub.

Contents

• Enable the portal on your instance
• Self-registration
• Ticket creation in the portal
• Operator name in conversations
• Organizations and ticket visibility
• Staff access (staff-view)
• Quick links

Enable the portal on your instance

Goal — allow the portal to call your ConnectiveOne instance API.

1. Enable Client Portal settings (Constructor) under feature flags.
2. Open Settings → Client Portal → Instance & access and set Client Portal URL (https://…).
3. Deploy Client Portal on that domain (separate web app; coordinate with your ConnectiveOne technical team).
4. Verify sign-in with a test user that has the Client Portal role.

→ Root alternative: client_portal_url in instance settings

Self-registration

Goal — let new users create an account on the portal registration page.

Setup order:

1. Role — Client Portal + minimal Operator Panel (View: themes, statuses, dialogue statuses, priorities, metrics; under Additional Operator Panel settings — View CSAT and Remove CSAT with access enabled). → Configure roles, enable-self-registration step 1
2. Instance & access (Client Portal) — enable self-registration and pick the role for new users. → enable-self-registration
3. Client fields — for fields that should appear on the registration form, enable Show on Client Portal registration. → Configure client fields

Step-by-step: How to enable self-registration.

Ticket creation in the portal

Goal — control which departments and topics clients see in Create ticket, and the text on selection cards.

1. Enable Client Portal settings (Constructor) (feature flags).
2. Confirm Instance & access has the portal URL.
3. Open Directions and topics, select bots and topics; in UA / EN / DE tabs set descriptions (and topic names in portal if needed) and icons.
4. Click Save and verify the wizard in the Support Portal.

→ How to configure ticket creation in Client Portal

Priorities and statuses follow Operator Line settings separately.

Operator name in conversations

Goal — clients in the Support Portal see a branded operator name (for example, "Support" or "Manager: Anna"), not only the operator profile full name.

1. Open Settings → Setting up for all operators.
2. Enable Display operator name in messages and set the Name of the operator in the chat message template.
3. Save and verify an operator comment on a portal ticket.

→ How to configure operators in chats

The same template applies in messengers and Operator Line; there is no separate portal-only field.

Organizations and ticket visibility

Goal — group portal client cards (for example, portal users from the same customer company) and optionally allow shared ticket visibility in the Support Portal.

1. Enable Client Portal settings (Constructor) and Client Portal organizations (Constructor) in feature flags.
2. Ensure the administrator role has Client Portal organizations permission.
3. Open Settings → Client Portal → Organizations — create an organization, assign clients, review Visibility preview.
4. Enable organization ticket access (a separate instance flag) only after agreement: portal users on My tickets may then see colleagues’ requests in the same organization.

→ How to manage organizations
→ Organization and ticket scope

Support Portal end users do not configure organizations.

Staff access (staff-view)

Goal — let operators and supervisors of your organization (not portal reporters) open the same ticket links as portal end users in read-only mode: public thread, internal notes inline, tracker link and client context. When needed — a read-only ticket list with Organization / Client filters.

1. In Roles, enable Client Portal (staff) together with Operator Panel and ticket rights — do not confuse with the Client Portal reporter marker.
2. In instance settings, set trusted URLs for the tracker and Operator Line (details in the how-to below).
3. After the Client Portal app update, verify a direct ticket link and the Show ticket list button as a staff user.

→ Configure staff access

→ Staff view

Quick links

• Configure departments and topics for ticket creation
• Configure operator name in chat and portal
• Enable self-registration
• Manage Client Portal organizations
• Organization and ticket scope
• Configure instance settings
• Configure roles
• Configure client fields
• What is Client Portal
• Configure staff access (staff-view)
• Staff view in Client Portal
• End-user hub