> For the complete documentation index, see [llms.txt](https://docs.bsure.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bsure.io/user-guides/priorities.md). # Priorities Priorities is where you tell Bsure Insights what matters most to you, and your [Assessments](/user-guides/assessments.md) worklist reorders around it. It is designed to answer one question: * If we can only fix a few things this month, which ones should rise to the top? *** ## Your focus areas Pick which areas you want to keep an eye on: Devices, Applications, Agents, Users, and Licenses. Every area is still measured either way. Nothing is hidden by turning an area off, the ones you pick simply rise to the top of your list. Keep at least one selected. ## Your ranking Every finding carries a security angle, a compliance angle, and a cost angle. Tell Bsure how much each one should count when ranking your list: * **Security risk**: accounts and settings an attacker could use. * **Compliance risk**: evidence you'd want ready for an audit. * **Cost**: license spend you could reclaim. Set each to None, Low, Medium, or High. A security-first team can turn Security risk up and Cost down; a team under budget pressure can do the opposite. Either way, the same findings are there. Only the order changes. *** ## What changes when you save Your ranking only changes what you see and in what order. It doesn't hide or delete anything. Findings still move through the same **Act now / Act soon / Plan ahead** priority cues on [Assessments](/user-guides/assessments.md); Priorities just decides which ones earn top billing on your list. ## Key takeaway Priorities lets the product adapt to what your organisation cares about, instead of forcing one fixed ranking on every customer. Set it once, revisit it whenever your focus shifts (a compliance deadline approaching, a cost-cutting quarter), and your worklist follows. --- # 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://docs.bsure.io/user-guides/priorities.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.