> For the complete documentation index, see [llms.txt](https://learn.mechanic.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.mechanic.dev/faq/can-non-owners-install-mechanic.md). # Can non-owners install Mechanic? Usually! A fresh install of Mechanic requires permission for reading online store content, like pages and blog posts. Any staff users who have access to that content in the Shopify admin will be able to install Mechanic. The operative subject here is the granting of permissions to Mechanic. Staff users can only grant Mechanic the permissions that they themselves have been granted. If a staff user has full permissions for the Shopify store, for example, then they'd be able to install Mechanic *and* configure whatever tasks they like, granting Mechanic whatever permissions are necessary. Or, if a staff user only has access to the store's products, they *will* be able to install product-related tasks, but they *won't* be able to install customer-related tasks. Note that this only applies to situations in which Mechanic needs *new* permissions. If another user has already installed a customer-related task, and has granted Mechanic those permissions, then *any other* user – even if they do not have customer permissions for the store – will be able to install additional customer-related tasks, because Mechanic will re-use its existing customer access. --- # 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://learn.mechanic.dev/faq/can-non-owners-install-mechanic.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.