Policies

Policies state how your organisation works and what it commits to — this chapter walks through drafting one, setting its review cycle, routing it for approval and keeping it under review.

A policy is a written statement of intent: this is what we do, and what staff and auditors can hold us to. The module carries one through its whole life — draft, review, approval, re-review, retirement — and writes every status change to the audit log. It records that work; it does not make the organisation compliant on its own.

Who uses it

The screenshots were taken with three accounts. The register, the overview, the details form and the Evidences tab show a Contributor, so Approve and delete are absent there. The reviewers, approvers and required-readers screens show an Admin, and the blocked submission and the policy in review show a Manager.

What's on this screen

Open Policies from the Compliance group in the left sidebar; the register opens at /policies. The header carries the title and three controls: a List / Grouped view toggle, Review Triage (AI), and the navy Create Policy button. Below sit three dropdowns — All Statuses, All Levels and All AI analyses — then a Search policies… box with its Search button.

The table lists every policy — Title, Status (a coloured badge — grey Draft, amber In Review, green Approved), Level, Owner, Version, Controls mapped, Effective Date, Review Date, AI analysis and Updated. The Review Date column shows the scheduled review date where one is set, and otherwise the effective date plus the review cycle; with neither it shows a dash. AI analysis shows the state of the policy's latest AI Enhance run — Queued, Analysing, Ready or Failed — or a dash when none has run, as on every row of the captured screen. Each row begins with a tick-box and ends with a pencil and an eye under Actions; a Manager or above also sees a third icon there, Delete policy.

  1. Choose how the register is drawn: List is the flat table shown here; Grouped redraws it with one section per governance level.
  2. Select Review Triage (AI) to have Aegis rank policies and procedures by their next review date and narrate a plan — the ranking comes from the dates, not the model. Saved briefings collect below the table.
  3. Narrow the register with All Levels, marked here, or All Statuses beside it; the rows reload to matches only. The status list also offers Needs Review and Active (not retired), and approvers get Pending My Approval.
  4. Set All AI analyses to AI analysis: queued or running to show only policies with an AI Enhance run in progress. While any row's run is queued or running, the list refreshes itself every ten seconds until it finishes.
  5. Type part of a title into Search policies… and select Search. The table filters to matches.
  6. On any row, select the eye to open the policy on its Document information & details tab, or the pencil to open it straight on Content. The title is a link to the same Document information & details tab; a click elsewhere on the row opens Content.
The Policies register — /policies.
The Policies register — /policies.

With no policies yet, the table is replaced by "No policies yet. Create your first policy to get started."; when a filter or search matches nothing, it reads "No policies match your search criteria."

Creating a policy

Creating a policy now happens on a page of its own at /policies/new, not in a dialog over the register. Titles need not be unique, so check the register first.

  1. Type the title you have in mind into Search policies… and select Search. The table filters to policies with a matching title.
  2. If one already exists, open it by its title and work on that policy rather than starting a duplicate.
  3. Otherwise select Create Policy. The Create New Policy page opens, with a Policies / Create New Policy breadcrumb above its heading.
The register, from which Create Policy opens the create page — /policies.
The register, from which Create Policy opens the create page — /policies.

This capture shows the register at the moment before you select Create Policy; the create page itself is not captured. It is laid out in two cards side by side — Policy Details and Timeline & Review — with a Policy Content card beneath them, a What happens next? box, and Cancel and Create Policy at the bottom right.

  1. Enter a Policy Title. Required, as the red asterisk shows; leaving it empty returns "Title is required".
  2. Set the Level — the governance level the Grouped view groups by. It starts at Unclassified; the other choices are Strategic, Tactical and Operational, and the hint below explains each.
  3. Under Timeline & Review, set an optional Effective Date and an optional Review Date, and pick a Review Cycle preset. The cycle starts at Quarterly; the presets are described under Changing a policy's details.
  4. Write the Policy Content in the formatted editor; the Preview tab beside Edit shows how it will read. The grey # Purpose / # Scope / # Policy Statement outline is placeholder text that vanishes as you type. Where your organisation has a company document template, the box opens pre-filled from it with the note "Pre-filled from your company template — edit freely."; a template that loads late never overwrites what you have already typed. Also required: leaving it empty returns "Policy content is required".
  5. Select Create Policy. The policy is saved as a Draft, a "Policy created successfully" message appears and the new policy's own page opens. Cancel returns to the register and discards what you typed.
Only title and content are required

Level, dates and review cycle carry defaults — capture the draft while it is fresh and refine everything later through Edit details.

The policy's own page

A policy opens at /policies/[id], on its Content tab unless the link names another. A Policies breadcrumb leads back to the register. The header shows the title, status badge, version and last-updated date; a status line on the right reads Ready between AI jobs. Under it runs a single row of labelled buttons — Edit, the lifecycle action where your role allows it (Submit for Review on a draft, Approve on a policy in review for approvers), Export to Word and More — then the tab strip: Document information & details, Content, Required Readers, Audit, Translations, Version history, Controls and Evidences. An Improve Writing or AI Enhance tab joins the row after Content once that aid has been run on the policy.

The first tab is an overview. A summary band repeats the title, status, version, owner and level. The Next step banner says what the policy needs now — submit it, approve it, or review it by its next review date — and who acts. Three tiles follow: Reviewers (open review requests, raised under Collaboration), Approvers and Required readers (how many of the required readers have read the current version, with a progress bar). When your licence includes multi-approver chains and the policy's approval setting asks for more than one approver, the Approvers tile lists each step with its role or person and shows progress such as "1 of 2 approved", with a Partially approved badge after the first approval; otherwise it shows the single approval ("Not yet submitted for approval", "Awaiting approval" or who approved it). Below sit an Edit details button and three collapsible cards: Identity (owner, category, level and policy ID), Planning (effective date, the next review date — the effective date plus the review cycle, unless a review date was set — review cycle, created and updated) and Approval (approve or reject, and the Approval History; an account that may not approve sees "User lacks permission to approve this policy" there instead). Then come a collapsible Changes since last approved version panel and, for users who may read the audit log, Recent activity with the latest five audit entries on this policy, followed by any roadmap work and action items linked to the policy. On a phone the band, tiles and cards stack in one column, and each card folds shut when you tap its title.

The policy in this capture is In Review and the account is a Contributor, so Edit is greyed out, there is no lifecycle button, and the banner reads "Approve or reject this version" with the approvers in the approval chain as the ones to act.

  1. Select Edit to change the body on the Content tab — on a Draft only; otherwise the button is greyed out, as here, and its tooltip reads "Policy must be in Draft status to edit content."
  2. Select Export to Word to download the policy as a .docx.
  3. Open More for the remaining actions, each with its icon and full label: the writing aids Improve Writing (drafts only) and AI Enhance (a Draft or an In Review policy), the secondary lifecycle action (Return to Draft on a policy in review, Revise on an approved one), Retire without approval for approvers, Upload Word/PDF on a draft, which shows what an edited file would change before it replaces the draft, and Help, which explains every button.
  4. Read the Next step banner; its Required Readers and Audit shortcuts open those tabs directly.
  5. Check the three tiles. Each one is a link: Reviewers to the Collaboration panel below the tabs, Approvers to the Approval card and Required readers to the Audit tab.
  6. Select Edit details to change the title, level, dates and review cycle: the cards are replaced in place by a form — covered below. For the level alone, Classify in the Identity card sets it without opening the form.
A policy's Document information & details tab — /policies/[id].
A policy's Document information & details tab — /policies/[id].

Choosing reviewers and approvers

The top of the Required Readers tab, headed Reviewers and approvers, sets who reviews the policy and who approves it. Each card carries a label saying where its list comes from: From this document, From the category or Organisation default. The policy's own list wins; when it is empty, the category default from Settings → Documents applies. Changes apply from the next submission for review.

  1. Check the source label. It reads From this document once the policy has its own list; Use the category default, further down the card, hands the list back to the category.
  2. Read the current reviewers — each with its type (Role, Group or Person) — and remove one with its ×.
  3. Choose a group, role or person in Choose a group, role or person… and select Add. A group becomes one review request per member who may decide reviews. Set the Rule — Everyone must agree or At least a minimum number with its Minimum number (N) — and the Deadline (days).
  4. Select Ask reviewers now to start a review round. Each reviewer gets an e-mail and an in-app notification that opens the policy on its Content tab; a person without an e-mail address gets the notification only.
  5. Under Approvers, add the people, roles or groups who approve, in order; the arrows change the order. Only holders of the approve permission — Admin and Manager — are offered. On a policy in review, as here, the list is locked and the card reads "Approvers cannot change while the document is in review. Send it back to Draft first."
Reviewers and approvers of a policy, with their source — /policies/[id]?tab=required-readers.
Reviewers and approvers of a policy, with their source — /policies/[id]?tab=required-readers.

Changes to either list are not stored until you save them: a bar appears reading "Unsaved changes" with Discard and Save, and "Reviewers and approvers saved." confirms the save. Below the approvers sits Owner does not approve own document, ticked by default (it is visible at the top of the next capture). Leave it ticked: the owner then approves only when nobody else can and the organisation allows it under Settings → Documents; that approval is marked as the owner's own in the approval history.

The Reviewers tile on the details tab follows the round, for example 1 of 2 reviews approved, then Review passed, or Overdue once the deadline has gone by. When the policy is submitted, the approvers of the current step get an e-mail and an in-app notification; with a multi-approver chain, the next step's approvers are told once the step before them has approved.

When nobody can approve

Submitting a policy that nobody but its owner can approve is refused. The captured draft below is owned by the Manager who tried to submit it.

  1. A red notice appears above the toolbar: "This document cannot be submitted for review yet — Nobody can approve this policy yet. Add an approver to the policy or to its category, then submit it again." Close dismisses it.
  2. Select Set approvers. The Required Readers tab opens on the reviewers and approvers cards so you can add one.
  3. The Next step banner still reads "Submit this version for review", with the owner as the one to act — the policy stays a Draft.
  4. The Approvers tile keeps reading "Not yet submitted for approval" until a submission succeeds.
Submitting a policy without an approver — /policies/[id].
Submitting a policy without an approver — /policies/[id].

Choosing who must read a policy

The Required Readers section, further down the same tab, holds the audience that must read and acknowledge the policy; the Audit tab shows who has. Both tabs can be linked to directly — /policies/[id]?tab=required-readers and /policies/[id]?tab=audit. Without permission to edit the policy, the tab says so instead of showing the form.

  1. Who must read this lists the audience as chips — an Aegis group, an Entra ID group, an HR department, a role, a person or everyone. Remove one with its cross.
  2. Type in Add readers to search groups, departments, roles and people.
  3. Tick the ones to add. The matches are grouped — Whole organisation, Roles, People and so on — each with its member count. Groups and departments stay dynamic: every night Aegis adds people who joined and marks people who left as no longer required, keeping their acknowledgements.
  4. Read Preview before saving: the total, how many read via login, via a read link, and how many cannot be reached. People without an e-mail address are listed and skipped for invitations; they never block saving or publishing. On the captured screen, Everyone is selected and all fifteen people read via login.
  5. Select Save Required Readers.
Choosing a policy's required readers with the audience preview — /policies/[id]?tab=required-readers.
Choosing a policy's required readers with the audience preview — /policies/[id]?tab=required-readers.

The Must Read list on the Audit tab then shows each required reader and whether they have acknowledged the current version, and the Required readers tile counts them.

Following up on readers — the Audit tab

For anyone who may edit the policy, the Audit tab opens with a Required readers audit above the Must Read list; a Viewer sees the list only. Nobody appears there until a version is published — readers are assigned at approval. The audit shows:

Remind… prepares a reminder for a selection or the whole version and shows who will receive it and who is skipped (already read, exempt, no e-mail address, reminded recently) before you select Send reminders. From a reader's timeline you can Resend link to a read-link reader. Holders of the readers-management permission also get Exempt… (with a reason and an end date) and Export…, which downloads the reading evidence as CSV or PDF, optionally as it stood on an earlier date. The IP address and read-link reference appear in the timeline only for a Manager or Admin.

Reader view — confirming a read without a login

A required reader who has no Aegis account reads and confirms the policy through a single-use read link, not through the application. The link is issued automatically the moment the policy reaches Approved: Aegis writes the reader assignments for the approved version and e-mails each read-link reader invitation E1 with their own link. The link works once and, by default, for 24 hours; it opens the last approved version of the policy — never a working draft — and grants nothing else.

When the approved version carries an owner-accepted change note, E1 and the reader view both show it under the heading What changed in this version, so the reader sees what is new before they confirm. The reminder (E2) never repeats it. The note is absent on a first approval, or where it was left empty, and its absence never holds up the invitation.

The reader opens the link and lands on the document view. At the top sit the policy's type, status, owner, version and dates; the approved text follows; then, where present, the What changed in this version summary; and last, the Confirm you have read this document panel, which repeats the Version and, where one is set, the reader's Deadline.

Before the reader confirms, the panel states plainly how the confirmation is recorded: "When you confirm, your IP address is stored as evidence of your acknowledgment and kept for 24 months on the basis of our legitimate interest (proof of acknowledgment)." Twenty-four months is the fixed default retention term for the confirmation IP; it is not a self-service setting in the app. The IP address is corroborating evidence with its own term — once it lapses only the IP is cleared, while the confirmation itself (version, time, channel, reference and device category) is kept as lasting proof that the reader acknowledged the policy.

  1. Select Send code. Aegis e-mails a six-digit confirmation code to the same address the link was sent to. A reader without a login always confirms with the link and a code, never the link alone.
  2. Enter the six digits in Confirmation code. Confirm stays disabled until all six are typed; Send a new code issues a fresh one if the first did not arrive or has expired.
  3. Select Confirm. A wrong, expired, already-used or locked code (a code locks after several wrong guesses) is refused with a single, neutral message — "That code is not valid or has expired. Request a new code and try again." — and the reader can ask for another. Submitting codes too quickly is throttled separately and shows a distinct message — "Too many attempts. Please wait a few minutes and try again." — so the reader waits rather than requesting a new code.
  4. On success the panel is replaced by the confirmation page, headed "Reading confirmed", showing the Version, the Confirmed at time and a Reference; a receipt is e-mailed to the reader. A reader who returns to a version they have already confirmed sees this page straight away.

A link that has lapsed — already used once, or older than its lifetime — opens the Link expired or invalid page instead. From there the reader can ask for a fresh link through the Request a new link form without involving the owner; that page is covered in External access. Requesting a new link, or re-approving the policy while the reader still holds a live link, extends the reader's existing invitation and sends a fresh single-use link rather than creating a second one. Only once every link has been revoked or has lapsed does the owner need to re-invite from the Required Readers tab, or send a fresh link with Resend link on the Audit tab.

Linking to a policy

Every policy has a stable address you can put on an intranet page, in an e-mail or in another document: https://<your-domain>/policies/<id>. Copy it from the browser's address bar while the policy is open. The address stays the same across versions — after a new version is approved, the same link opens the current one.

Anyone who follows the link needs their own account and must sign in. A reader who is not signed in yet is taken to the sign-in page first and, once signed in — with a password, an authenticator code or single sign-on (SSO) — lands directly on the policy, not on the dashboard. The link grants no access by itself: the reader's role and the policy's access rules still decide what they can see and do.

Changing a policy's details

Edit details replaces the three cards with a form on the same page — there is no dialog. The heading reads Edit policy details, with the reminder "The policy text is edited on the Content tab" underneath. While the form is open the address bar reads /policies/[id]?tab=details&edit=1, so the editor can be linked to directly.

  1. The summary band, banner and tiles stay above the form and keep showing the saved values until you save.
  2. The form opens under the Edit policy details heading; its Content tab link takes you to the body instead.
  3. Change the Policy Title — the one field the form insists on: emptying it and saving returns "Title is required".
Editing a policy's details in place — /policies/[id]?tab=details&edit=1.
Editing a policy's details in place — /policies/[id]?tab=details&edit=1.

Further down the form, below the edge of this capture:

  1. Set the Level — Unclassified, Strategic, Tactical or Operational; the hint spells out what each means.
  2. Set the Effective Date — blank means the policy takes effect on approval.
  3. Set the Review Date — when the policy is next due for review. Where it is set, it is the date the register's Review Date column and Review Triage (AI) use; where it is blank, both use the effective date plus the review cycle.
  4. Pick a Review Cycle preset — Monthly (30 days), Quarterly (90, marked Recommended), Bi-annual (180), Annual (365) or Custom cycle. The create page offers the same presets.

Finish with Save changes at the foot of the form. A "Policy details updated" toast confirms it and the cards return with the new values; Cancel discards what you typed. Unlike the body, details can be edited at any status — an approved policy need not return to Draft for a new review date.

The approval lifecycle

A policy carries one status at a time, shown as a badge wherever it appears.

Status What it means What the toolbar offers
Draft Being written. Not binding. Submit for Review; under More, Retire without approval for approvers
In Review Waiting on an approver. Approve for Manager and above; under More, Return to Draft for editors and Retire without approval for approvers
Partially Approved Some, not all, steps of a multi-approver chain have signed off (only where that chain is switched on for your tenant). No lifecycle button: the remaining approvers act in the approval-chain panel; under More, Retire without approval for approvers
Approved The current binding version. Retire Policy; under More, Revise
Retired No longer in force, kept for the record. Reactivate

Retire without approval retires a policy that was never approved, for example a framework template your organisation will never adopt. It needs the approve permission and a reason of at least 10 characters, skips the approval chain and never counts as an approval. The reason and date show on the retired policy and in the audit log (POLICY_RETIRE). In the policy list, Change Status → Retired asks approvers for one shared reason for the whole selection.

In exports and audit-log entries these read as Draft, InReview, PartiallyApproved, Approved and Retired. Revise is the way to change an approved policy: it asks for a change summary, snapshots the text into Version history and returns the policy to Draft; each submission and approval lands in Approval History.

Reviewing and approving a policy in review

Open a policy whose badge reads In Review. On a Manager account the toolbar shows Edit greyed out — the body can no longer be typed into directly — then the navy Approve, Export to Word and More. The capture shows the Content tab, where the version under review is read.

  1. Note the version number under the title. Your approval covers this version only.
  2. Read the text on the Content tab, and use the other tabs — controls, evidence, changes since the last approved version — as you need.
  3. Open More when the text needs work. AI Enhance has Aegis propose improvements while the policy is still in review; the suggestions land on the AI Enhance tab, and applying one creates a new version, as described under Reviewing an AI Enhance result below. Return to Draft sends the policy back to Draft so the editor can change it by hand before submitting it again. Retire without approval retires a policy that should never come into force; it asks for a reason of at least 10 characters.
  4. Select Export to Word to take a copy of the version you are reviewing, for example to read it offline.
  5. Select Approve — the navy button immediately to the right of the greyed-out Edit — once you have read the version on screen. Where a multi-approver chain is switched on, approvers act in the approval-chain panel instead.
A policy In Review on a Manager account: Approve beside the greyed-out Edit, Export to Word and More — /policies/[id].
A policy In Review on a Manager account: Approve beside the greyed-out Edit, Export to Word and More — /policies/[id].
An approval covers only the version you read

Approval is tied to the version number shown on screen. If the policy changed after you opened it — for example because someone applied an AI suggestion, which creates a new version — Aegis refuses the approval with "This policy changed since you opened it (now version n). Review the new version before approving." and reloads the page. Read the new version, then approve again. The approval-chain panel and the approval dialog behave the same way, and an edit that races an approval is refused rather than saved under the approval.

Nothing moves the review date for you

Neither editing nor approval changes the Review Date or the Effective Date, and Review Triage (AI) ranks on the next review date derived from them. A policy whose review you have completed keeps reading as overdue until you open Edit details and set the next date yourself.

Linking evidence and discussing a policy

The Evidences tab ties a policy to evidence (documents that show a control works), held in Evidence. Below the tab strip — on whichever tab is open — sits a Collaboration section carrying the policy's comments and review requests.

  1. Select Evidences, the last tab. The panel header reads LINKED EVIDENCE with the count in brackets.
  2. Select AI search evidence to have Aegis propose items from your library that appear to support this policy — you review each suggestion and decide.
  3. Or select + Link Evidence to search the library and pick items yourself.
  4. Until something is linked, the panel reads "No evidence linked yet." with the hint "Link audit reports, security questionnaires, or other documents." — as below.
  5. Scroll to Collaboration. Under COMMENTS, read existing comments ("No comments yet." when there are none), type in the Write a comment… box and select Post comment. Under REVIEWS, Request review asks a colleague to review the policy.
The Evidences tab, with no evidence linked yet — /policies/[id].
The Evidences tab, with no evidence linked yet — /policies/[id].

The AI assist

Policies has five AI aids: Review Triage (AI) on the register, Improve Writing on a draft, AI Enhance on a draft or a policy in review, AI search evidence on the Evidences tab, and the upload preview's summary of what a file would change. Each output is a suggestion: a person reads it, edits it and decides — nothing is approved, published or linked without that decision. Where AI is switched off for your tenant, the buttons are absent and every task still works by hand.

Reviewing an AI Enhance result

The AI Enhance tab holds Suggested Improvements and Suggested Framework Mappings. While a run waits for a free slot, the status line reads "AI Enhance is queued for this policy and starts when an earlier analysis finishes…"; it changes to "AI Enhance is analysing this policy…" once the run starts. While the run is in flight the tab shows a pulsing marker, so you can tell from another tab, and the register's AI analysis column shows Queued or Analysing.

Tips and limits

Where this connects

A policy maps to controls through its Controls tab, feeding the coverage in Compliance frameworks and Control mapping. The step-by-step how belongs in Procedures; the proof it is followed lives in Evidence. A policy can treat a risk, comments work as in Collaboration, and every status change reaches the Audit log.