> For the complete documentation index, see [llms.txt](https://boza.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://boza.gitbook.io/docs/browser-extension/manual-install.md). # Install Manually This guide walks through installing the Boza extension directly from a browser store. For automated deployment across your organization, see the [Deployment Guides](/docs/browser-extension/deployment.md). ## Compatible Browsers The Boza extension works with all major browsers: * Google Chrome * Microsoft Edge * Arc * Brave * Mozilla Firefox * Apple Safari (macOS) ## Installation Steps ### Chrome, Edge, Arc, and Brave 1. Open the [Boza listing in the Chrome Web Store](https://chromewebstore.google.com/detail/boza/lgdogpphmkjofjogicpokolmlmcfilja). 2. If Microsoft Edge asks whether to allow extensions from other stores, follow your organization's browser policy. 3. Click **Add to Chrome** or the equivalent button shown by your browser. 4. In the confirmation dialog, click **Add extension**. 5. Click the **Boza icon** in your browser toolbar and select **Sign In**. 6. Authenticate with your corporate Google or Microsoft account. 7. Wait for the **"Boza is now active"** confirmation message. Boza extension page on the Chrome Web Store ### Firefox 1. Open the [Boza listing on Firefox Add-ons](https://addons.mozilla.org/en-US/firefox/addon/boza/). 2. Confirm that the add-on is published by **Boza**. 3. Click **Add to Firefox**. 4. In the permissions dialog, click **Add**. 5. Click the **Boza icon** in the toolbar and select **Sign In**. 6. Authenticate with your corporate credentials. 7. Wait for the **"Boza is now active"** confirmation message. Boza extension sign-in page with SSO options ### Safari (macOS) 1. Open [Boza - Extension in the Mac App Store](https://apps.apple.com/app/boza-extension/id6756876185). 2. Confirm that you are installing the Boza application. 3. Click **Get**, then **Install**. 4. Open **Safari** and navigate to **Safari > Settings > Extensions**. 5. Enable the **Boza** extension by checking the box. 6. Click the **Boza icon** in the Safari toolbar and select **Sign In**. 7. Authenticate with your corporate credentials. 8. Wait for the **"Boza is now active"** confirmation message. Boza extension installed and active in the browser toolbar ## Troubleshooting ### The extension does not appear after installation * Confirm your browser version is up to date. Boza requires recent versions of all supported browsers. * Check that the extension is enabled in your browser's extension management page (`chrome://extensions`, `edge://extensions`, `about:addons`, or Safari Settings > Extensions). * Restart the browser and try again. ### Sign-in fails or loads indefinitely * Verify you have a working internet connection. * Clear your browser cache and cookies, then attempt sign-in again. * Confirm with your IT administrator that your account is provisioned in the Boza platform. * Confirm that your identity-provider administrator has [authorized Boza](/docs/getting-started/whitelist-boza.md). ### The extension icon is missing from the toolbar * In Chrome/Edge, click the **puzzle piece** icon in the toolbar and pin the Boza extension. * In Firefox, right-click the toolbar and select **Customize Toolbar**, then drag the Boza icon into place. * In Safari, ensure the extension is enabled under **Safari > Settings > Extensions**. --- # 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://boza.gitbook.io/docs/browser-extension/manual-install.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.