The Customer portal exposes a branded, read-mostly view of the relationship — orders, invoices, documents, and open tickets — without granting access to internal CRM data.
Please note:
- Portal users see only records scoped to their company or contact — internal CRM permissions do not apply; configure access via Roles, permissions, and RBAC.
- Invite portal users through Add users and invite teammates with a least-privilege portal role.
What customers see
| Section | Typical content | Backend module |
|---|---|---|
| Orders | Status, line items, delivery | Orders / logistics |
| Invoices | PDF download, payment status | Finance |
| Tickets | Open requests and replies | Ticketing |
| Profile | Contact details, addresses | Companies / contacts |
| Documents | Statements, contracts | Document storage |
Visibility is record-scoped: each portal user links to a company or contact and sees only that party’s data.
Set up customer access
- Enable Customer portal under Settings → Modules
- Configure branding (logo, colors, support email) in portal settings
- Invite users from a company record or send self-registration links when allowed
- Assign a portal role with least privilege (read orders, read invoices, create ticket)
Verify invoice and order modules are enabled before exposing those sections — empty nav confuses customers.
Support handoff
When a customer opens a ticket, internal teams work it in Ticketing while the customer tracks status in the portal.
sequenceDiagram participant Customer participant Portal as Customer portal participant CRM as Internal CRM Customer->>Portal: View invoice or open ticket Portal->>CRM: Scoped API by company CRM-->>Portal: Authorized records only Portal-->>Customer: Status and documents CRM->>CRM: Agent responds in Ticketing CRM-->>Portal: Customer sees reply
Review portal permissions quarterly — especially after adding Finance or Ticketing modules. Field reps using the Salesmen portal follow a separate permission model scoped to territory.