Accreditations

Feature flag

The whole Project management section is enabled with the project_management feature flag (Extra → Settings → Feature flags). It is off by default.

An accreditation records a formal authorisation granted to a system, a service or the organisation by an authority — the outcome of an audit-and-decision process rather than the audit itself. It captures who granted it, what was in scope, what evidence backed the decision, and when it lapses.

Where to find it

Project management → Accreditations in the sidebar. Start an accreditation opens the form.

The record

Field	Notes
ID	Short reference, e.g. ACC-2026-001
Domain	Scopes permissions
Author	The actor preparing the file
Category	From your accreditation terminology — Simplified, Elaborated, Advanced, Sensitive, Restricted or Other
Status	Draft, In progress, Accredited, Not accredited or Obsolete
Collection	The collection holding the dossier
Authority	The issuing body. Only entities flagged as an accreditation authority appear in the picker
Custom authority name	Free text when the authority is not registered as an entity

The More section adds the extended fields: Checklist, Commission date, Duration (months), Expiry date, Decision evidence, Labels and Observation.

Tip

Fill in Commission date and Duration and leave Expiry date blank — the platform computes the expiry for you on save. Set it by hand only when the authority granted a non-standard validity.

Category and status values come from Terminologies, so you can relabel them to match your authority’s vocabulary without changing how the record behaves.

The four moving parts

An accreditation is really four things you maintain in parallel:

1. The dossier — what is being accredited. It lives in the linked collection: the audits, evidences, exceptions and policies that make up the perimeter you are submitting. Add and remove objects there, not here.
2. The progress — how far the work is. Point Checklist at an audit and the accreditation’s progress bar follows that audit’s completion.
3. The decision — what was decided. Captured as Status, Commission date, Decision evidence and the granted duration or expiry date.
4. The approval — who signed off inside CyberGuard, when your process requires a recorded sign-off.

From draft to accredited

1. Create the accreditation in Draft, with the author, category and authority set.
2. Build the dossier in the linked collection and set the relevant audit as the Checklist.
3. Move to In progress while the commission reviews. The progress bar climbs as the audit does.
4. When the decision lands, set Commission date and Duration, attach the minutes as Decision evidence, and flip the status to Accredited or Not accredited.

The detail page shows the authority, status and category as chips, the checklist card with its percentage, and an Associated objects grid — one card per category present in the linked collection, each with item counts, status chips and links through to the underlying objects. If no collection is linked, that section is empty.

Renewal and retirement

As expiry approaches, renew by updating the commission date and duration and replacing the decision evidence with the renewal documents; blank the expiry date to have it recalculated. To retire an accreditation, move its status to Obsolete rather than deleting it — the record stays in history where an auditor can still find it.

Related

• Collections — the dossier behind every accreditation.
• Audits — the usual checklist.
• Evidences — where decision minutes live.