> For the complete documentation index, see [llms.txt](https://doc.dastra.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.dastra.eu/en/features/compliance/scopes.md). # Scopes They are used to group **organizational units** together in order to apply a compliance approach to all or part of the organization. A scope answers a simple question: > *Which organizational entities does this compliance project apply to?* *** ### Role of scopes in Dastra In Dastra, scopes are used exclusively in **compliance projects**.\ They make it possible to: * precisely target the entities concerned, * adapt the requirements, controls and tests to the right level, * structure compliance according to the organizational reality. 👉 A scope does not modify the frameworks:\ it **determines where** compliance applies, not **what** applies. *** ### A flexible organizational breakdown A scope is defined from the **organizational units** that exist in the workspace. It can represent: * the entire company (e.g. *Global*) * a division or a department (e.g. *IT*, *HR*) * a site, a subsidiary or a specific activity Organizational units can be selected individually or in groups, respecting their hierarchy. *** ### Creating a scope When creating a scope, the user provides: * **the name of the scope** (e.g. *Global*, *IT & Security*) * an **optional description** * the **organizational units** included in the scope (mandatory)
👉 A scope must always contain **at least one organizational unit**. *** ### Example of a scope 📌 Example: * **Name**: Global * **Description**: The entire company * **Organizational units**: * Global * HR * IT * Factory * Sub / Service This scope can then be selected in a compliance project to indicate that it applies to the entire organization. *** ### Best practices * Create a **global scope** for cross-cutting approaches * Create **more restricted scopes** for targeted projects * Reuse scopes across projects to ensure consistency * Name scopes in an explicit and business-oriented way *** ### Link with compliance projects Scopes are selected **when creating a compliance project**. They make it possible to: * apply the same framework to several entities, * track compliance by scope, * compare results between different parts of the organization. *** ### Summary Scopes are an **organizational framing tool**.\ They make it possible to align compliance with the actual structure of the company, without adding complexity to the referentials. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://doc.dastra.eu/en/features/compliance/scopes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.