> 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/library/frameworks.md).

# Frameworks

Build your compliance framework or import a framework built by Dastra

The **Frameworks** page of the Library is the entry point to the compliance approach in Dastra.\
A framework represents a **structured compliance framework** (e.g. GDPR, E-Privacy, AI Act), bringing together requirements, controls, risks and threats.\
These frameworks serve as a **common foundation** for building your compliance projects, harmonizing your practices and ensuring full traceability between regulatory obligations, operational controls and risk management.

***

## 1. Side navigation of the compliance library

<div align="center"><figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-98156a5bb202fac1a2f9d6e4a56fe22820217eda%2Fcompliance-library-frameworks-1.png?alt=media" alt="List of the library frameworks with the side menu and the used frameworks gauge"><figcaption></figcaption></figure></div>

The side menu groups the objects of the library in two groups, with the number of items of each entry:

* **Compliance** group:
  * **Frameworks**: compliance frameworks (central library). The chapters and requirements that structure a framework are viewed in the framework page
  * **Controls**: the central element linking requirements, tests and risks
  * **Tests**: verifications that demonstrate the effectiveness of a control
* **Risks** group:
  * **Risks**: supports for risk assessment and monitoring
  * **Threats**: events or scenarios that may materialize a risk

At the bottom of the menu, the **used frameworks** gauge shows your consumption of framework credits.

***

## 2. List of frameworks

The central area displays the list of frameworks available in your environment:

* Frameworks created by your organization
* Frameworks imported from the Dastra library
* Number of frameworks in your quota (note that the quota is shared at the account level, not the workspace level)
* Filters by status (draft, published, etc.)
* Number of the current version of each framework and, for a framework created from a template, the **Update available** badge when a newer version of the source referential exists (see [Framework versions](https://doc.dastra.eu/en/features/compliance/library/frameworks/versions.md))

When no framework is present, Dastra directly offers:

* [**Import a framework**](https://doc.dastra.eu/en/features/compliance/library/frameworks/import.md)
* [**Create a framework**](https://doc.dastra.eu/en/features/compliance/library/frameworks/custom.md)

{% hint style="info" %}
Remember that the quota is shared across the entire organization, not per workspace. Keep an eye on your usage to avoid hitting the limits. The versions of a framework are not counted separately: creating or importing a version does not consume a framework credit.
{% endhint %}


---

# 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://doc.dastra.eu/en/features/compliance/library/frameworks.md?ask=<question>&goal=<user_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.
