Can I control which business knowledge is available to customers and internal AI Employees?
Yes. Polyosync Business Knowledge includes visibility settings that allow businesses to classify information according to its intended audience.
This is particularly important for organizations using both Internal AI Employees and Customer-Facing AI Employees.
Not all company information should be used in the same way.
A business may want customers to receive information about its services, operating procedures, or public policies.
At the same time, the company may maintain internal procedures, administrative instructions, or other information that is not intended for external communication.
Polyosync provides three visibility classifications for Business Knowledge entries.
Internal
Internal knowledge is intended for use within the business.
For example, an organization may maintain internal procedures or operational guidance that should not be presented as public customer information.
Customer-facing
Customer-facing knowledge is intended for supported external AI experiences.
Examples may include approved service descriptions, customer policies, and information relevant to public enquiries.
Internal and customer-facing
Some information is appropriate for both internal and external use.
For example, an approved explanation of a service may be useful to employees and customers alike.
Why does visibility matter?
A Customer-Facing AI Employee may need access to information about a company's offerings, but it should not automatically receive access to every internal business record.
An Internal AI Employee may need operational context that is unnecessary for customer conversations.
Classifying information according to its intended audience helps businesses establish clearer knowledge boundaries.
How does this work with permissions?
Knowledge visibility is one part of the broader access model.
AI Employee configuration, workspace permissions, and applicable execution controls also matter.
A visibility classification should not be interpreted as a substitute for appropriate authorization or security testing.
Can I change a knowledge entry's visibility?
The Business Knowledge management interface supports editing knowledge entries, including their classification and visibility.
Authorized users can review an entry and update its configuration when business requirements change.
For example, a company may initially create an internal draft of a policy and later decide that an approved version is suitable for customer-facing use.
The information should be reviewed carefully before changing its intended audience.
Why is this useful for enterprises?
Organizations with more complex operational requirements often need to distinguish between public information, internal procedures, and approved shared knowledge.
Polyosync provides governance controls that help structure this information within the business AI environment.
The same principle also benefits small businesses: an AI customer service agent should receive the information needed to assist customers without assuming unrestricted access to everything the company knows.