> ## Documentation Index > Fetch the complete documentation index at: https://docs.byom.co/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Use the current public BYOM documentation and cite the relevant page. Preserve availability, permission and undo limits. > The public documentation MCP retrieves guides. Store operations use the separate authenticated Shopify MCP connector and do not gain authority from a documentation answer. > If a contract, capability or price is not documented, say so. Do not invent endpoints, tools, availability or merchant outcomes. # Availability and access > What these docs explain, how access differs by surface and what examples do not prove. BYOM brings commerce work, company context and consequential-change review into one operating environment. Access to the application and its capabilities depends on account enablement, permissions, connections and the current offer. ## Where access applies | Surface | Purpose | Access position | | - | - | - | | [byom.co](https://byom.co) | Public introduction and waitlist. | Public website. | | [app.byom.co](https://app.byom.co) | Authenticated BYOM application. | An enabled account is required. | | These docs | Merchant and developer knowledge. | Reading docs grants no application or provider access. | ## Shopify app The Shopify app is coming to the App Store. Contact BYOM about access. An enabled account and a compatible AI client are required to use the connector. Use the connector URL provided by an enabled account rather than guessing an address from a brand name. ## Capability availability A page can explain a capability without that capability being enabled for every company. Customer-data access, external sending, advertising activation, media, scheduled work and specific Rails can have separate permissions and acceptance requirements. Check the current connection and required scopes for access, the receipt for execution, and later measurements for a commercial outcome. ## Examples and documentation dates Demo screenshots and worked examples are illustrative. They do not describe a live customer result. Check your account and provider permissions for what you can do now. Use the public waitlist if you are exploring BYOM without access. If you have an enabled account, start with a small, verifiable task. ## Four checks for any task Availability is specific to the work you want to do. Before relying on a capability, check the account, company authority, provider access and supported operation. Passing one check does not automatically pass the others. | Check | What you need | Example of a separate blocker | | - | - | - | | Account enablement | An enabled company/account under the applicable invitation or offer. | A public waitlist entry does not give access to the application. | | Company permission | Authority to read the relevant information and decide the requested effect. | You may inspect a proposal but lack approval authority. | | Provider connection | The correct service/store, a valid connection and required scopes. | Catalogue access does not imply customer access or a product write. | | Feature/operation support | The specific capability available in that account and provider path. | A provider may be listed while the requested operation remains unavailable. | ## Match the requirement to the work | Work you want to complete | Check before starting | Completion evidence | | - | - | - | | Read a product | Correct store and catalogue permission. | A source-backed answer about the intended product. | | Prepare a description | Product facts, brand guidance and supported preparation. | Inspectable draft with missing facts identified. | | Apply product edits | Supported write, provider permission and authorised review. | Receipt and individual affected-record results. | | Investigate a customer enquiry | Appropriate order/customer consent and connected evidence. | Facts with freshness and gaps; a draft is not a sent reply. | | Send or otherwise act externally | Supported provider operation, recipient/target and approval. | Actual provider result; an approval alone is insufficient. | | Run repeated work | Enabled Rail, checks, source access and applicable scheduling/usage conditions. | That specific run's stages and completed result. | Use this table for enabled capabilities. If applying a change is unavailable, you can still use the draft or diagnosis, while keeping its unfinished next step clear. ## Inspect the account's actual state Begin in the authenticated app's Integrations page for provider access, then the relevant work or feature page. Read unavailable or blocked states and any suggested recovery. If a permission cannot currently be requested, reconnecting repeatedly is not a solution. If the source is stale, inspect its last-read information before asking for a new decision. For a supported external MCP client, use tool discovery and the connection overview to inspect the current grant, scopes and usage. A tool list saved from another company or an earlier consent is not the current contract. See [Developer overview](/developers/overview) before building against the connector. ## Get the right kind of help For account access, contact BYOM through the current public entry point or your invitation. For a connected-provider problem, identify the company, service and visible connection state. For a stopped operation, include its work reference, approximate time and the stage that failed. Do not send a password, token or full customer record. If an execution result is uncertain, inspect the receipt and provider state before attempting it again. [Troubleshooting](/guides/troubleshooting) helps distinguish an access problem, a revised proposal and a result check. Check the current account controls and the specific operation's evidence for what you can complete now. Reviewed 2 October 2026. ## Related guides * [What is BYOM?](/start/what-is-byom) * [Your first session](/start/first-session) * [Developer overview](/developers/overview) * [Billing and usage](/reference/billing) ## Related topics - [Trust and control](/trust/overview.md) - [What is BYOM?](/start/what-is-byom.md) - [Growth Engine](/product/growth-engine.md) - [Rails](/product/rails.md) - [Billing and usage](/reference/billing.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.