> 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/resources/faq.md). # FAQ Quick answers to the questions we hear most. For anything not covered here, contact ****. *** ## Getting started **I see a "Restricted Access" screen and no workspace — why?** Your organization isn't set up in Boza yet, or your account isn't linked to a workspace. Contact your IT administrator, or reach out to **** to get started. **What's the difference between demo mode and going live?** A new workspace opens in **demo mode** with realistic sample data so you can explore freely. Going live connects your identity provider and **clears the demo data**, then fills your workspace with your real users and applications. See [Exploring the Demo Workspace](/docs/getting-started/demo-workspace.md). **Which identity providers does Boza support?** Google Workspace and Microsoft Entra ID. Sign-in is **SSO-only** — there are no standalone Boza passwords. *** ## Privacy & the browser extension **Does the browser extension track my personal browsing?** The extension uses browser URL and tab access to match visited domains against Boza's professional-application catalog. A recognized domain can produce an application signal even when the extension cannot determine whether that visit was professional or personal. Boza can associate the match and activity time with the corporate user, but it does not collect page content, form values, keystrokes, emails, or documents. Scope the deployment to approved managed browsers and devices. See [What is the Browser Extension?](/docs/browser-extension/browser-extension.md). **Where is my data stored?** In **France**, on Scalingo (3DS Outscale data centers). See [Data Privacy & GDPR](/docs/settings-and-security/data-privacy-gdpr.md). **Which browsers does the extension support?** Chrome, Edge, Arc, Brave, Firefox, and Safari. See [Install Manually](/docs/browser-extension/manual-install.md). *** ## Using the platform **Why can't I create or edit teams?** Team management requires a connected identity provider. Connect Google Workspace or Microsoft Entra ID under [Integrations](/docs/integrations/integrations.md), then use the **Sync my Workspace** button. See [Organization](/docs/user-management/organization.md). **How does Boza detect subscriptions from invoices?** Upload invoices (or sync Pennylane) and Boza's AI reads them — extracting the vendor, application, amounts, and billing period — then puts them in a review queue for you to confirm. See [Upload Invoices](/docs/inventory/subscriptions-and-vendors/upload-invoices.md). **Can I disconnect an integration?** Yes. Open **Integrations** from the main navigation, open the connector's panel from the **Connected** tab, and click **Revoke**. Jamf uses **Disconnect** instead. **How often does Boza sync data?** There is no single refresh interval for every source. Identity-provider and direct integrations synchronize according to their supported schedule, browser-extension signals arrive after device activity, and some connectors provide a manual sync action. See [Metrics & Data Freshness](/docs/resources/metrics-and-data-freshness.md). **How do approvals reach the right person?** When IT accepts an access request, Boza creates a task for the app's Super Admin and notifies them through Slack or Microsoft Teams. See [Access Requests](/docs/user-management/requests.md). **What is the difference between a workspace Admin and an application Super Admin?** A workspace **Admin** can administer Boza. An application **Super Admin** owns one application and receives its operational actions; the role does not grant workspace administration. See [Roles & Permissions](/docs/settings-and-security/settings/roles-and-permissions.md). **Where did newly discovered applications go?** They are on the dedicated [Shadow IT](/docs/inventory/shadow-it.md) page. The Applications page now contains **My Apps** and **Unapproved Apps**. **Can Boza AI change my data?** No. The AI Assistant is read-only. Its answers can still be incomplete or incorrect, so verify important figures in the source page or export. See [Boza AI Assistant](/docs/platform/ai-assistant.md). **Who can use Boza AI, and what does it retain?** In the current release, every authenticated platform user who can see the assistant can ask organization-wide questions; application and Access Reviewer roles do not filter the results. Successful questions and generated SQL are stored as tenant-scoped examples and can be reused for similar questions from the same organization. See [Boza AI Assistant](/docs/platform/ai-assistant.md) and [Data Privacy & GDPR](/docs/settings-and-security/data-privacy-gdpr.md#boza-ai-assistant). **Can I use Boza in French?** Yes. A workspace Admin chooses the language under **Settings → General → Language**: the whole interface and every email Boza sends switch to French or English, for everyone in the workspace. See [Switch your workspace to French or English](/docs/tutorials/switch-workspace-language.md). **Can Boza's emails come from our own address instead of ?** Yes, for access-review emails. Connect a Google Workspace or Microsoft 365 mailbox under **Settings → General → Email sending**; invitations, reminders, and test reviews then come from that address. Boza only gets permission to send; it never reads the mailbox. See [Send Boza emails from your own mailbox](/docs/tutorials/send-emails-from-your-own-mailbox.md). **Can I merge more than two duplicate applications at once?** Yes. Select every entry in **Applications**, click **Merge** in the selection bar, choose the one that survives, and everything from the others moves onto it. Boza also flags likely duplicates itself in a banner at the top of the list. See [Merge duplicate applications](/docs/tutorials/merge-duplicate-applications.md). **How do I run an access certification?** Assign Access Reviewers to approved applications, test the reviewer flow, then configure or launch a campaign from **Access Review**. See [Access Reviews](/docs/user-management/access-reviews.md). *** ## Browser extension deployment **Will users see a notification when the extension installs?** Managed installation normally does not require each user to visit a browser store. Browser behavior and whether an extension is pinned depend on the policy you deploy. **What happens if a user uninstalls the extension?** With the force-install policy, the extension reinstalls automatically the next time the browser launches. **How does the extension update?** Store-managed browser extensions update through the browser's normal managed-extension mechanism. Safari app updates follow your Apple and device-management policy. **Can I deploy to only some users?** Yes. Target specific device or user groups (for example, Smart Groups in Jamf, or groups in Intune and Google Admin). **Does the extension work on Windows?** Yes — deploy it via [Microsoft Intune](/docs/browser-extension/deployment/microsoft-intune.md) or [PowerShell](/docs/browser-extension/deployment/powershell.md). **Does Safari deployment require Apple Business Manager?** Yes. Deploying the Boza Safari app via MDM requires **Apple Business Manager (ABM)**. ABM is free, but you'll need your company's **DUNS number** for verification (about 1–3 days if you already have an Apple Developer account, longer otherwise). The Boza Safari app is free on the Mac App Store, but it must be added to your **VPP** (Apps and Books) catalog to deploy it through Jamf or Intune. See the [Jamf](/docs/browser-extension/deployment/jamf.md) and [Safari via Intune](/docs/browser-extension/deployment/safari-intune.md) guides. *** ## Need Help? Still stuck? Email **** and we'll help. --- # 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/resources/faq.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.