> For the complete documentation index, see [llms.txt](https://docs.taptap3d.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.taptap3d.com/concepts/publication-boundaries.md). # Publication boundaries How tenant access, field visibility and publication approval should separate private records from public embeds. Having access to an inventory record does not mean that record is approved for publication. Public embedding needs an explicit publication decision in addition to the application's existing membership checks. ## Existing field visibility The current catalogue engine supports three audiences: | Audience | Intended reader | | ---------- | -------------------------------------------------------------- | | `public` | A reader of a public catalogue or other outward-facing output. | | `internal` | The organisation's staff and people involved in that business. | | `house` | The organisation alone. | The organisation defines the field policy; the output defines its audience. An unclassified field currently defaults to public. Before any online publication is enabled, the publisher must review the field policy and explicitly classify private fields. Reserve prices, acquisition costs, consignor details and internal notes must not be published by accident. ## Proposed embed boundary The embedding feature should serve an approved public listing, not an authenticated editor or raw inventory endpoint. The publication design must cover: * A reviewed set of public fields and images. * Permission to reproduce each published image. * A revocable publication URL independent of the internal record URL. * Removal of public access when a listing is withdrawn. * A clear cache invalidation policy for withdrawn content and assets. * No organisation credentials or private API keys in a browser embed. These are release requirements, not claims about an existing publication service. ## Host application responsibilities Treat published descriptions as untrusted content when rendering them yourself. Escape text and validate image and action URLs. Keep private credentials on your server. For the proposed iframe, the host should validate the sender origin and source window of any message before using it. See [Host website integration](/proposed-reference/host-integration.md). --- # 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 dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.taptap3d.com/concepts/publication-boundaries.md?ask=&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 `build a script that syncs our docs to a CMS` 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.