Skip to main content

​
Public and private access

An AI Experience can serve a broad audience or a specific group of invited visitors. Choose the access approach that fits the purpose of your experience, the information it shares, and the people you want to reach.
Access controls and visitor registration are different. Access controls determine who may enter an experience. Registration determines what information a visitor provides before chatting. A registered visitor is not necessarily an invited visitor.

​
Understand your access options

​
Public experiences

A public AI Experience is designed to be discoverable and shared. You can link to it from your website, social profiles, newsletters, or campaigns. Public access does not mean that every visitor can necessarily start chatting without registration. Your experience may still ask visitors to register before a conversation begins, depending on its configuration.
Treat content in a public experience as potentially visible to anyone who receives its link. Do not upload confidential material simply because your assistant has instructions not to disclose it.

​
Private and invite-only experiences

An invite-only experience is intended for a defined audience. This can be useful when you’re testing with a small group or providing an experience to specific clients or members. Before inviting visitors, decide:
  • Who should be allowed to access the experience?
  • How will you add or invite them?
  • What should happen when someone without access opens the link?
  • What knowledge is appropriate for that audience?
  • Who will review and remove access when it is no longer needed?
Invite-only access is an audience restriction, not a guarantee that every uploaded document is appropriate to share. Apply data-minimization principles and avoid adding secrets, sensitive personal information, or confidential client data unless you have confirmed the necessary permissions and safeguards.

​
Choose the right access model

Choose public access when:
  • Your goal is to help new prospects experience your expertise.
  • The knowledge is suitable for broad distribution.
  • You want to share the experience through marketing channels.
  • You are comfortable with visitors discovering and using the experience.
Choose invite-only access when:
  • You are conducting a controlled pilot or beta test.
  • The experience is intended for a specific client or member group.
  • You want to limit participation while refining the assistant.
  • The subject matter requires tighter control over who can interact.
Example: A consultant might publish a public AI Experience that introduces their methodology, while using a separate invite-only experience for a small group participating in a structured workshop.

​
Configure access in Agentsy

  1. Sign in to your Agentsy account and open the AI Experience you want to configure.
  2. Find the experience’s access or visibility settings. The exact label may vary by workspace or product version.
  3. Select the appropriate access mode, such as Public or Invite-only, if available for your experience.
  4. If you select invite-only, configure the permitted visitors using the invitation or access-management options shown in your dashboard.
  5. Save your changes.
  6. Test the published link using both an authorized visitor and someone who has not been invited.
If you do not see an expected access option, confirm that you’re editing the correct experience and check which controls are available in your account. Do not assume an experience is private until you’ve tested access from an unauthorized session.

​
Understand registration and guest access

An experience’s visibility is only one part of the visitor journey. Depending on how your experience is configured, a visitor may:
  • See the landing page before starting a conversation.
  • Be asked to register or sign in before chatting.
  • Be offered a limited guest interaction before registration, if that flow is enabled.
  • Need an invitation or other authorization to access a private experience.
Guest chat and registration are separate configuration topics. See Guest chat and registration for details.

​
Test access before sharing

Use a private browsing window or a separate test account to verify the actual visitor experience.
  • A public visitor can reach the intended landing page.
  • Registration appears at the intended stage of the journey.
  • An unauthorized visitor cannot enter an invite-only experience.
  • An authorized visitor can access the experience successfully.
  • Invitation and sign-in links lead to the correct destination.
  • The assistant does not disclose information beyond its intended scope.
  • Your booking or contact option is available when human follow-up is needed.
Testing a private experience while signed in as its owner can hide access problems. Always repeat the test from a session without administrator permissions.

​
Common questions

You can distribute the link to intended participants, but possessing a link should not be treated as proof of authorization. Verify the experience’s access restrictions using an uninvited test visitor.

​
Does requiring registration make an experience private?

No. A public experience may require registration before chatting. Privacy depends on who is authorized to access it, not simply whether visitors provide their names or email addresses.

​
Can I change access after publishing?

Check the visibility controls available in your Agentsy dashboard. If you change access settings, test the live experience again and review any existing invitations or shared links.

​
Should I use an invite-only experience for sensitive information?

Restricted access can reduce exposure, but it is not a substitute for appropriate data handling, contractual protections, or security controls. Avoid uploading sensitive information unless your use case and safeguards have been specifically reviewed.