Embed & share

In one line. Put a Botminds experience where your users already are: share links for instant access, anonymous access for public-facing surfaces, and embedding for your own portals. You’ll be able to. Choose the right exposure level for an experience, and know what each level does and doesn’t protect.

The exposure ladder

Every experience starts private: sign-in required, access governed by roles. From there you open it up deliberately, one rung at a time:

Rung	What it is	Right for
Signed-in access	The default — users log in, roles apply	Internal operations
Share link	A link that opens a specific page or experience directly — recipients skip the navigation, not the rules	Sending a colleague straight to a dashboard, a document, a chat
Anonymous access	An experience opened to users without accounts	Public assistants, customer-facing lookups
Embed	The experience rendered inside another site or portal	Your intranet, your product, a customer portal

Share links

The Share Link control in the top navigation (available when enabled for the experience) captures where you are and hands it to someone else. What they can see when they arrive is still decided by their access — a share link is a pointer, not a permission.

Anonymous access

Some experiences are built to face the world — a policy assistant on your intranet’s front page, a public document lookup. The experience is configured for anonymous users; the platform serves it without a sign-in, and everything else stays locked. Two disciplines:

• Attach only public-safe knowledge. The agent behind an anonymous experience should be grounded exclusively in content you would hand to a stranger — that is the attachment boundary doing its job.
• Watch the audit surfaces. Anonymous chat still lands in the chat audit, so you can see what the world is asking.

Embedding

Rendered pages and chat experiences can live inside your own web properties, carrying your branding so the seam doesn’t show. Pair an embedded experience with either signed-in access (your portal handles identity) or anonymous access (public surface), per the ladder above.

For deeper integration — your system calling the platform rather than framing it — step up to the Runtime API.

Choosing, quickly

The sentence in your head	Rung
“Look at this”	Share link
“Our customers should be able to ask this”	Anonymous experience
“It should feel like part of our portal”	Embed
“Our system needs the data, not the screen”	Runtime API

Where to go next

• Making it look like yours first: E7 · Shaping the experience.
• The pages you’d embed: E6 · Pages & cards.
• Who can see what, underneath it all: G1 · Access & roles.