> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/get-started/availability.md). # Feature availability Distro features become available to your workspace when they are enabled and your account has the right access. Seeing an editor does not necessarily mean live execution is active. ## Check what is available 1. Sign in to the correct workspace and review your role. 2. Open the feature from the app navigation. Ask an admin about access if it is missing. 3. For workflows, open the published version and confirm the workflow is **On**. 4. Check its trigger connection and the credentials used by its actions. 5. Run a sample first, then make a controlled live submission when your admin confirms live runs are enabled. A simulation uses samples for external operations. It helps you check branches and mappings; it does not send a real sequence, write a CRM record, or establish that a provider will accept the request. ## If a workflow does not start Check the source, publication, On/Off state and workspace activation before changing the canvas. If no run appears, the problem is at intake or activation. If a run appears and fails, inspect the step and its connection in **Logs**. Share the workflow name, time of the attempt and error with Distro support. Keep credentials and prospect data out of screenshots you share publicly. See [Test and publish](/workflows/test-and-publish.md) and [Integration availability](/data-and-integrations/availability.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.distro.so/get-started/availability.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.