> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/jet-bridge-deployment/share-and-embed/embed-an-app.md).

# Embed an app

Display an app inside another website or tool when your app's sharing mode and the host support embedding.

## Choose the appropriate workflow

The existing Classic builder provides documented workflows for [a generated sharing link](/classic-app-builder/preview-and-publish/embed-apps/embedding-app-using-a-generated-link.md) and [iFrame/HTML embed code](/classic-app-builder/preview-and-publish/embed-apps/embedding-app-using-iframe-html.md). Those tutorials use **Share → Public Share → Public Access Link**.

The current AI builder's inspected Share dialog contains membership invitations. Do not assume its invitation link is equivalent to Classic public sharing or generated embed code.

## Embed and verify

1. Publish and verify the app outside the host site first.
2. Confirm the supported sharing or embedding method for your app.
3. Obtain the appropriate app URL or generated embed code.
4. Add it through the host site's supported embed or HTML component.
5. Open the host page as an intended user.
6. Check sign-in, navigation, sizing, permitted actions, and restricted data access.

For a Classic embed, select the intended team before distributing public sharing access. Review the resulting access rather than assuming the host site's own login protects the embedded app.

## Troubleshoot an embedded app

If the app works directly but fails inside the host, capture the browser error and compare the sign-in and framing behavior. Check the host's embed support and the app's authentication requirements. Do not disable access controls just to remove an embedding error.

If a supported embedded flow is unavailable, provide a normal link to the published app. Continue with [published-app access troubleshooting](/jet-bridge-deployment/logs-and-troubleshooting/published-app-access-fails.md) for sign-in or permission failures.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.jetadmin.io/jet-bridge-deployment/share-and-embed/embed-an-app.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.