> 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/projects/design.md).
# Project design
It allows you to define the **organizational scope**, select the **applicable frameworks** and automatically initialize the associated controls, tests and risks.
This step lays the foundations of the project and determines the quality of monitoring in the following phases.
***
### 1. Creating the project and defining the scope
When creating the project, an **organizational scope** must be selected.\
The scope groups together one or more organizational units and determines **the scope of application of the compliance project**.
{% columns %}
{% column %}
Once the project is created, the scope is displayed in the project header and used throughout the compliance cycle.
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
***
### 2. Assigning users to the project
{% columns %}
{% column %}
{% endcolumn %}
{% column %}
The design phase also allows you to **designate the users authorized to manage the project**.
* Each user can be assigned a role (e.g. owner).
* These users will be entitled to steer the project's controls, tests and audits.
{% endcolumn %}
{% endcolumns %}
***
### 3. Adding compliance frameworks
A compliance project is based on one or more **frameworks** (standards, internal or custom referentials).
Adding a framework allows you to import:
* the **requirements**,
* the **controls**,
* the **tests**,
* and the associated **risks**.
Several frameworks can be added successively to the same project.
***
### 4. Sharing controls across frameworks
When several frameworks are added to the project, Dastra automatically detects the **common controls**.
* A control shared between several frameworks **is imported only once**.
* Its implementation simultaneously covers all the associated requirements.
* This makes it possible to increase compliance coverage without multiplying actions.
***
### 5. Selecting the controls to import
When adding a framework, several options are offered:
* import **all the controls** of the framework,
* import **only certain controls**,
* or **not import any controls** in order to implement them manually.
This flexibility makes it possible to adapt the project to the organization's maturity.
***
### 6. Initializing controls and tests
{% columns %}
{% column %}
Once the frameworks are imported:
* The **selected controls** are automatically added to the project.
* They are considered **implemented by default**.
* The **associated tests** are also attached to the controls.
At this stage:
* the tests are set to the **"missing evidence"** status,
* no evidence has been collected yet.
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
***
### 7. Preparing the risk analysis
The **risks from the frameworks** can be selected during the import.
They constitute:
* the basis for the **initial risk assessment**,
* the reference point for calculating the **residual risk** after the controls are applied.
***
### Result of the Design phase
At the end of the design phase, the project has:
* a clearly defined scope,
* identified owners,
* the applicable frameworks imported,
* shared controls ready to be monitored,
* initialized tests,
* and a structured risk base.
The project is then ready to enter the next phase: **Implementation**.
---
# 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/projects/design.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.