A framework is the standard or regulation you're working against — ISO 9001 (quality), ISO 14001 (environment), ISO 27001 (information security), GDPR, and more in the catalogue. Regnora maintains each one centrally as its full set of requirements, so you don't import the standard text or keep it up to date yourself. This guide covers how a framework is structured inside Regnora, how to enable one in a project, and how to request one that isn't catalogued yet.

## How a framework is structured

Open a framework and you see its requirements laid out as a tree that mirrors the published standard — **chapters**, **sections**, **articles**, **paragraphs**, **annexes**, **clauses**, **controls**, and so on, nested the way the document itself is. A table of contents alongside the tree lets you jump around a large standard quickly.

This structure is what everything else hangs off: gap analyses assess against these requirements, and the [project profile](/guides/project-profile-and-context/) attributes a framework asks for are tied to the same requirements.

**Manage:** [Library frameworks](https://app.regnora.com/library/frameworks) · [Enabled in this project](https://app.regnora.com/frameworks)

## Enabling a framework in a project

To bring a framework into a project, you **enable** it. On the project's **Frameworks** page, select **Add framework**, pick the one you want from the list, and select **Enable**. That creates an *adoption* — your project's own instance of that framework, against which you'll evidence requirements and run gap analyses.

Enabling is reversible. You can **disable** an adoption at any time without losing data, and re-enable it later. Because each adoption is project-scoped, the same framework enabled in two projects stays completely independent — an ISO 27001 adoption for your own ISMS doesn't get mixed up with one you're running for a client.

## Layering multiple frameworks

A project can have several frameworks enabled at once — common when one engagement spans, say, ISO 27001 and GDPR. They all assess against the same evidence base in the project. Overlapping requirements aren't deduplicated; each framework is evaluated on its own terms.

## The framework library

The **Framework library** is the central catalogue of everything Regnora supports. You enable frameworks for a project from that project's Frameworks page, but you browse the full set here. It has two tabs:

- **Catalogue** — every supported framework, which you can filter (for example, **EU**, **ISO**, or **Other**) and which is grouped into categories like EU regulations and ISO standards.
- **Your submissions** — frameworks you've requested that aren't in the catalogue yet, with their current status.

## Requesting a framework that isn't catalogued

If the standard you need isn't listed, you can **submit** it from the library. A submission captures the framework's name, publisher, version, and a description, with optional notes and a file. Submitted frameworks are processed by Regnora before they become enableable — you'll see them under **Your submissions** with a processing status until they're ready.

**Manage:** [Library frameworks](https://app.regnora.com/library/frameworks) · [Enabled in this project](https://app.regnora.com/frameworks)