Portals
Set up portals for customers, vendors, partners, or employees.
Portals give an audience a place to read published Knowledge and submit cases. Manage them under Administration → Portal Settings.
Availability
The hosting workspace needs Pro, Team, or Enterprise. Administrators also need portals:manage. Invited people use separate portal credentials; they do not need to join the staff workspace.
Create a portal
- Open Portal Settings and add a portal from the list.
- Set its name, portal address, and welcome message.
- Upload a logo and choose an accent color.
- Choose the allowed People types: Customer, Vendor, Partner, and/or Employee.
- Select the Knowledge bases this audience should use.
- Decide whether Knowledge requires login, then enable the portal when ready.
You can create multiple portals with separate audiences, branding, and Knowledge bases. Each uses a unique Coherence-hosted address. Custom domains and subdomains are not yet supported.
Invite people
Select an existing Person whose Type includes an allowed audience and send an invitation. The email contains a link to set a password. Portal credentials are stored separately from the Person record, while the portal identity stays linked to that Person.
Creating a Person or linking an Account does not itself send an invitation. Staff can suspend portal access without deleting the underlying CRM record.
Public and signed-in Knowledge
With login optional, visitors can read published public articles in the selected bases. With login required, visitors must sign in before browsing. Article audience rules still apply after login, including organization-specific access. Draft and internal content is not exposed to visitors.
Cases
Signed-in people can submit a case, see their permitted cases, and reply. Staff handles these requests in Cases. Internal notes stay in the workspace. Organization-wide case access is an explicit setting, not a consequence of sharing an email domain.
Plan changes
If the hosting workspace moves to Free or Starter, these paid features become unavailable, including portal access. Existing records and settings are retained; upgrading to an eligible plan restores plan access without reinstalling modules. Staff permissions and portal enablement still apply.