> For the complete documentation index, see [llms.txt](https://guardian.hedera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guardian.hedera.com/docs/develop/guardian/platform.md). # Platform Capabilities that support asset creation, governance, and operations. The Guardian Platform provides account, operational, discovery, and governance capabilities that support asset creation in Guardian. These capabilities help users create, find, manage, observe, and secure assets. They are not the policy assets themselves. Visit the **Workspace** section to learn about assets used for authoring include policies, schemas, artifacts, tools, modules, and formulas. This section includes the services and features to support authoring and operations. ### What Platform includes * **Identity and access** — profile settings, users, roles, and permissions. * **Operations and visibility** — notifications, asynchronous task status, usage statistics, TrustChain, and logs. * **Discovery and organization** — guided methodology search, AI Search, project comparison, and tagging. * **Configuration and delivery** — external-service credentials, mobile data entry, demo experiences, live project data migration, and themes. Platform features within the Guardian support the assets in Workspace throughout their lifecycle. They help teams control access, track work, find relevant content, review activity, and adapt the experience to their needs and workflows. ### Related * [Workspace](/docs/develop/guardian/workspace.md) * [Roles & Permissions](/docs/develop/guardian/platform/roles-and-permissions.md) * [Profile Reference](/docs/develop/guardian/platform/profile.md) * [Notifications](/docs/develop/guardian/platform/notifications.md) * [Usage Statistics](/docs/develop/guardian/platform/usage-statistics.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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://guardian.hedera.com/docs/develop/guardian/platform.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 `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.