> 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/assessments.md). # Assessments Your prioritized worklist for everything Bsure Insights has found. One page, every current finding, always ranked by what matters most to you. It gives the same assessment engine used across Bsure in a compact, cross-domain view. Useful when you want the findings first, without starting from a dashboard card or a scoped owner view. It is designed to answer simple but important questions: * What needs my attention right now, and what can wait? * Where do I stand in Devices, Applications, Agents, Users, and Licenses? * What have I already reviewed and consciously decided to live with? Every assessment appears here, regardless of its setting in [Global Assessments](/user-guides/settings/configuration/global-assessments.md). That toggle controls notifications, not what shows up on this page. *** ## Overview At the top of the page, Bsure shows the latest calculation date. Every number on the page comes from that calculation cycle. Findings are grouped into three tabs: * **Needs attention**: open findings, ranked so the most urgent one is always first. * **Your list**: the same findings, ordered by the priorities you've set on the [Priorities](/user-guides/priorities.md) page. * **Going well**: areas that are currently clear or already under control. Below that, category tabs split the same findings by area: * **Devices** * **Applications** * **Agents** * **Users** * **Licenses** Use the tabs to move from a broad overview into the specific area you want to review. *** ## What each card gives you Each finding appears as a card with: * A priority cue, **Act now**, **Act soon**, or **Plan ahead**, so you always know where to start. * A plain-language description of what was found and why it matters. * A recommended next step, including the option to accept the risk instead of fixing it immediately. *** ## Opening a finding Select a card to open its drilldown, the exact list of accounts, applications, agents, or other objects behind the number. At the top of the drilldown you'll see: * How many still **need attention**. * How many have had their **risk accepted**. * Your **target** for this finding, configurable in [Global Assessments](/user-guides/settings/configuration/global-assessments.md). * A short trend, so you can see whether the picture is improving. From there you can search, filter, sort, show or hide columns, and export the current view. Everything you need to turn the headline number into a concrete action list. *** ## Accepting risk Not every finding needs to be fixed today. For any individual item in a drilldown, you can choose **Accept risk** (or **Accept cost**, for license-value findings) instead of remediating it right away. Accepting risk asks you for: * A **reason**, so the decision is documented, not just implied. * A date to **review again**, from a week out to a year out. The item stays visible in your totals, but drops out of what needs attention until that date. Every decision is kept in an **Accepted risk audit** trail, so you, or an auditor, can see exactly what was accepted, by whom, why, and when it's due for another look. When the review date passes, the item reopens automatically. This turns "we haven't gotten to it" into "we looked at it and made a call", the difference that matters when someone asks for evidence, not just a dashboard. *** ## Export Use **Export** in drilldown to download the current filtered result. That is useful when another team needs the list, when you want to work outside Bsure for a period, or when you need evidence for follow-up. *** ## Access Users need access to **Assessments** to open the page and use drilldown. An administrator manages access in **Settings → Configuration →** [**Users Management**](/user-guides/settings/configuration/users-management.md). --- # 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/assessments.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.