> ## Documentation Index
> Fetch the complete documentation index at: https://www.docusnap.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Objectives

> Assess an objective on its detail page, complete its review, and link controls, documents, and assets.

Every objective of an active regulation has a detail page of its own. There
you decide on applicability, set the implementation status, complete reviews,
and link the objective to controls, documents, and assets.

## Open the detail page

An objective's detail page opens as a tab of its own, next to the tabs of
the regulations—from a regulation's list as well as from the *Objectives* tab
of a control or a risk. It has three tabs: *Overview*, *Relations*, and
*Journal*.

You edit *Applicability*, *Implementation Status*, and *Next Review* together
with the pencil and save them in one step. The regulation's list and its KPIs
then reflect the change.

<Note>
  Without write permission in the module, the pencil, the notes field with
  *Complete Review*, and the *Link* and *Control* buttons in the *Relations* tab
  are missing. You set permissions per module under
  [Users](/docs/en/settings/users).
</Note>

## Applicability

*Applicability* is set to *Applicable* or *Not applicable*. The
*Justification* field applies to both decisions: with *Applicable* it records
what makes the objective apply; with *Not applicable* it is required.

<Warning>
  As long as no decision has been made on an objective, the toggle also shows
  the state *Not Assessed*. It disappears for good with the first saved
  decision—as with protection need on an asset, a decision once made can only
  be changed, not reverted. See
  [Determine Protection Needs](/docs/en/isms/protection-needs).
</Warning>

A *Justification* requires a decision: while an objective is still *Not
Assessed*, an entered *Justification* can only be saved together with a
decision. Clearing an existing *Justification* works without a decision.

## Implementation Status

An applicable objective is *Pending*, *Not implemented*, *Partial*, or
*Complete*. With *Not applicable*, the *Implementation Status* section does
not appear; with *Not Assessed*, it stays locked until you decide on
applicability. Which values count as a gap is explained in
[Understanding Compliance](/docs/en/isms/understanding-compliance).

## Review

*Complete Review* requires a note and is locked while you edit. The note is
not part of editing with the pencil: it is saved only with the completion.
Docusnap365 sets the review dates itself when you complete a review. Past
reviews are listed with *Reviewed On*, *Reviewed By*, and *Result* in the
table below.

## Description

The *Description* section shows the full text of the objective, preceded by
the source with the regulation's publisher, key, and version. If an objective
has no text, the section does not appear.

## Relations

The *Relations* tab lists the linked controls, documents, and assets, and the
objective's cross-references. *Link* links existing controls, documents, and
assets, including for *Not applicable* objectives. *Control* creates a new
control and links it to the objective.

Cross-references (type *Cross-ref*) cannot be opened. A row whose type is
switched off in the data model, or for which you lack permission, shows a hint
with the reason and cannot be opened; the relation can still be removed.

<Note>
  Deleting a relation removes only the relation—the control, document, or
  asset itself stays. With multiple rows selected, this runs in a batch:
  successful rows disappear even if some fail; a summary message names the
  ones that failed.
</Note>

## Journal

The *Journal* tab shows the change history of the objective's assessment.

## Related

[Activate and Assess Regulations](/docs/en/isms/regulations) covers activation and
bulk-editing several objectives.
[Understanding Compliance](/docs/en/isms/understanding-compliance) explains when an
objective counts as complete, applicable, or as a gap.
[Documenting Evidence for Controls](/docs/en/isms/control-evidence) covers the
evidence of a linked control.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.