Understand customer sign-in and private knowledge
An anonymous visitor can use public support content. Account-specific information requires verified customer identity and the required record access.
What customers do
Customers choose Sign in in the widget and follow the portal sign-in flow. The support session is then associated with a verified customer principal. A typed name or email address does not complete this verification.
Prepare private content
- Check the customer records and portal access managed by your organization.
- Set an article's audience to Authenticated customers or Selected customer accounts as appropriate.
- For selected accounts, assign the intended account scope and check the customer's active grants.
- Enable Customer AI only if the published content may be used for those customers.
- Test with the actual intended customer account and a separate account that should not have access.
Website origins authorize an installation location. They do not establish the identity of a person using that website. A KB writing API client is also not a customer identity.
Check ticket information
An anonymous ticket request can contain unverified contact information. Staff should treat that label as meaningful. A ticket number alone does not establish a customer's right to read private status or history.
If access fails
Check the active customer identity, account relationship, portal grants and article policy. Revoked identity or source access can invalidate earlier results. Do not broaden an article to Public just to work around a sign-in problem.