Public review states
Resources in the review queue can appear as:- Private / Unreviewed
- Needs review
- Approved
- Blocked by readiness issues
Resources reviewed here
The current review surface includes:- Procedures
- AI Guidelines
- Documents & Websites
- Gallery assets
- Connections
- MCP Servers
- Updates
Admin approval
Creators can author and revise content, but public availability is an administrative decision. Administrators can:- mark resources for review;
- resolve readiness problems;
- target resources through Collections;
- target Procedures/Guidelines to specific widgets;
- set procedure public-policy requirements; and
- approve resources for Chatbot.
Collections
Collections group approved public resources and can be assigned to widgets. In a widget’s Experience & CSAT tab, selecting collections narrows the widget to those collections. If no collections are selected, the widget can use all Chatbot-approved resources applicable to it. Collections are useful for:- separate brands;
- product lines;
- country/market deployments;
- customer portals;
- different public policy sets; or
- test versus production widgets.
Procedure public policy
A Procedure can have additional Chatbot publication controls:- required visitor identity level:
- Anonymous
- Verified email
- Signed-in customer
- require customer confirmation;
- whether it may suggest approved public actions;
- specific allowed widgets; and
- Collection membership.
Guideline targeting
Public AI Guidelines can be limited by:- Collections;
- specific widgets; and
- allowed domains.
Authored knowledge articles
Shared Knowledge separates RAUM-authored articles from Zendesk-synchronized Assistant articles. An authored article can carry:- translations;
- product availability;
- Collections; and
- public approval state.
Zendesk-synchronized content
Zendesk-synchronized Help Center Articles remain managed from the Assistant/Zendesk side. Synchronizing a Zendesk article does not automatically make it public Chatbot knowledge. If the same information should be public, publish it through a Chatbot-supported resource path rather than treating Zendesk synchronization as consent to expose internal material.Connections require two gates
A public Connection is not available simply because its connection editor says website chat may use it. It also needs Chatbot approval here. That means the effective public path is: Connection public policy + matching widget/identity/input rules + Shared Knowledge approval If either gate is missing, the connection remains unavailable to the public Chatbot.What is never copied into public context
The public review interface explicitly excludes internal Zendesk resources such as:- Ticket Fields;
- Macros;
- Zendesk groups; and
- Zendesk organizations.
Knowledge & AI
Understand which shared resources Chatbot can use.
Public connections
Configure live customer-safe data access and public action boundaries.
