> 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/communication-kit/communication-kit.md). # Announce Boza to Your Teams Tell employees what is changing before deploying the Boza browser extension. A useful announcement explains the purpose, the data flow, the limits, and where questions should go. ## Prepare the Message Confirm these points with your IT and privacy teams before sending anything: * Why your organization is using Boza. * Which managed browsers, devices, and employee groups are in scope. * When deployment starts. * Which matched application signals are available in Boza and who is authorized to use them. * Your organization's legal basis, retention policy, employee notice, and escalation contact. * Whether users must sign in once or will be identified through managed configuration. {% hint style="warning" %} Do not promise privacy behavior that differs from your deployed configuration or internal policy. Have your privacy or legal owner review the final employee notice. {% endhint %} ## Explain the Browser Signal Accurately The extension needs browser URL and tab access to compare visited domains with Boza's professional-application catalog. For a supported match, Boza can associate the application domain or URL and activity time with the employee's corporate identity. This supplies the application inventory and usage evidence used in Boza. The extension does not determine whether a recognized domain was visited for a professional or personal purpose. Your notice should therefore name the managed browsers, devices, and employee groups included in the rollout. The extension does not collect: * Page content or documents. * Form values, passwords, or keystrokes. * Screenshots. * Email or chat contents. See [What is the Browser Extension?](/docs/browser-extension/browser-extension.md) and [Security & Privacy](/docs/settings-and-security/security-and-privacy.md) before answering detailed questions. ## Employee Announcement Template Replace every bracketed field and have the message approved internally. > **Boza browser extension deployment — \[DATE]** > > We are introducing Boza to help \[PURPOSE, such as “IT maintain our application inventory and manage software licenses”]. Starting on \[DATE], IT will deploy the Boza extension to \[BROWSERS / DEVICES / EMPLOYEE GROUP]. > > The extension compares browser domains with a catalog of professional applications. When it recognizes a supported application, Boza records the matched application signal, activity time, and your corporate identity so authorized \[TEAM OR ROLE] can manage application usage and access. > > The extension does not collect page content, form values, passwords, keystrokes, screenshots, emails, chats, or documents. \[ADD YOUR ORGANIZATION'S RETENTION, ACCESS, AND EMPLOYEE-RIGHTS INFORMATION.] > > \[SIGN-IN INSTRUCTION, if required.] For questions or privacy requests, contact \[IT / PRIVACY CONTACT]. ## Rollout Message Checklist * Send the notice before the pilot begins. * Name the exact date, device scope, and support contact. * Link to your organization's acceptable-use and employee-privacy policies. * Explain the pilot and how employees report a false application match. * Tell users whether they need to sign in once. * Keep the approved notice with the rollout change record. * Update the notice if collection, access, or retention changes. ## Common Employee Questions | Question | Suggested answer to adapt | | -------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What does the extension observe?** | It uses browser URL and tab access to match domains against Boza's professional-application catalog. Supported matches can be associated with your corporate identity and activity time. | | **Does it read the page?** | No. It does not collect page content, form values, keystrokes, screenshots, emails, chats, or documents. | | **Why is my work identity included?** | The identity lets authorized teams connect a supported application signal to access, license, and security workflows. | | **Who can see the data?** | \[NAME THE ACTUAL AUTHORIZED ROLES OR TEAMS IN YOUR ORGANIZATION.] | | **How long is it retained?** | \[INSERT YOUR APPROVED RETENTION STATEMENT.] | | **Can I remove it?** | It is managed under \[NAME THE RELEVANT DEVICE OR IT POLICY]. Contact \[IT CONTACT] with a technical or privacy concern. | | **How do I exercise a privacy right?** | Contact \[PRIVACY OR HR CONTACT] using \[APPROVED PROCESS]. | ## Need Help? For product questions, contact ****. Your organization remains responsible for its employee notice, access policy, legal basis, and retention statement. --- # 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/communication-kit/communication-kit.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.