العربية

Getting Started Guide

From a fresh company account to a working oversight programme — a step-by-step tour, written for someone who has never worked in compliance before.

Every screenshot in this manual is real and unedited. No mockups. For every step, you’ll find why it matters to the business, exactly how to do it, how it connects to everything else, and what the AI actually did — and, just as importantly, what it did not.

Zemam is a platform that helps a company keep track of three things it is legally and practically expected to manage well: the rules it must follow, the safeguards it has in place to follow them, and the risks that could still go wrong anyway. It uses AI to produce a fast first draft of that work, and it enforces a simple rule throughout: nothing an AI drafts for the company’s records — a rule, a safeguard, or a match between them — becomes official until a person has looked at it and agreed, and the company can require that person to be someone other than whoever asked for it. When an AI tests a safeguard against its evidence, its verdict is recorded with the model that reached it, and a person can overrule it with a recorded determination of their own.

This manual follows one fictional company, Meridian Gulf Holding, from the moment its account exists to a working, multi-person routine. Every screenshot was captured against the real, running application. Where this manual says an AI drafted something, an AI actually drafted it, seconds before the screenshot was taken; where it says a person approved something, that click actually happened.

How a company’s account actually gets created

A new customer never has to file a request or wait for someone else to set anything up. They sign in with an existing work account (Google or Microsoft/LinkedIn), and the system builds their private company space automatically, in the same moment — one sample company record, one person with full access (the person who just signed in), and a handful of realistic starter examples, so the very first screen is never a blank, empty one. That starter content is not a special demo — it is the same small example every real, brand-new customer gets, meant to be replaced with the real company’s own information within the first hour or two of use.

Meridian Gulf Holding’s account was created exactly this way, under Rania Al-Fahad. The chapters below show, step by step, exactly what she — and five colleagues she then adds — did next, and why each step matters to the business.

The cast

NameJobEmailWhat they do
Rania Al-FahadHolding adminrania@meridian-gulf.testSets up the company structure, the applicable rules, and the team
Layla HassanGovernance officerlayla@meridian-gulf.testThe board, committees, policies and spending-authority limits
Omar Al-SabtiAuditoromar@meridian-gulf.testIndependent, read-only assurance across every record
Maha Al-ZahraniReviewermaha@meridian-gulf.testMakes the final human call on every AI-drafted item
Sara Al-QahtaniLibrary stewardsara@meridian-gulf.testReviews as Maha does, and approves shared-library promotions
Youssef NasserNo roleyoussef@meridian-gulf.testDoes everyday work inside one part of the business

Every account above signs in with the same shared starting password — the ordinary way a small team works together before each person is given their own, individual sign-in.

Chapter 1 — Holding Admin: Standing Up Meridian Gulf

Rania Al-Fahad is the person opening the front door on day one. Think of her as the owner of the company’s account: everything in this chapter turns a brand-new, empty account into a working, accurate picture of the real company — its structure, the rules it has to follow, its people, and its first safeguards. Nobody else can do any of the later chapters until this one is done.

1Signing in and seeing where you’re starting from

Why we do this

A company only starts being able to show a regulator, a bank, or its own board that it manages risk properly once its account actually holds real information — every day spent on setup before that is a day without a documented control record to point to. Signing in with a work account the company already uses, and finding a small working example rather than a blank screen, means there is already something to edit rather than something to build from nothing, and the progress rings make it possible to see, without asking anyone, exactly how much of the initial setup is still open.

How to do it
  1. Sign in with a Google or Microsoft/LinkedIn work account — no separate password to invent or remember.
  2. The system automatically creates a private, secure space for the company that only its own people will ever be able to see.
  3. That space already contains a handful of realistic examples — four sample safeguards, four sample rules and one sample risk, with sample test results marked as samples — so nothing looks empty or intimidating.
  4. The home screen shows five areas of work, each with a small progress ring, so it is obvious at a glance what is already done and what is still open.
  5. Ask Zemam, open from any screen, lists for whoever administers the workspace up to three setup steps not yet done, from the same checklists behind those rings, each a link straight to the screen that does it. Its Guide me button asks the same AI that answers every question in Ask what to set up next, and why, from this workspace’s own data.
How it connects to the rest of the system

Everything that happens for the rest of this manual — every chapter, every person, every screen — happens inside this one private space. Nothing typed here is ever visible to another company, and nothing from another company is ever visible here.

What the AI does here

No AI runs at sign-in, and none writes the setup steps in Ask: they are read straight from the checklists behind the progress rings. An AI answers only when Guide me is pressed, and the screenshot shows the steps before it is.

The very first screen. Setup is 3 of 7 steps done and Internal Controls 1 of 5 — the sample examples that ship with a new workspace already tick a few boxes.
The very first screen. Setup is 3 of 7 steps done and Internal Controls 1 of 5 — the sample examples that ship with a new workspace already tick a few boxes.
Ask Zemam opened at the gateway: the next setup steps not yet done, each a link to the screen that does it, and the Guide me button. The steps are read from the checklists, not written by an AI.
Ask Zemam opened at the gateway: the next setup steps not yet done, each a link to the screen that does it, and the Guide me button. The steps are read from the checklists, not written by an AI.

2Giving the company its real name and details

Why we do this

Every rule, safeguard and template the system later suggests is driven by three facts recorded here: which country the company is legally registered in, what industry it operates in, and whether it is publicly listed. The sample company is deliberately called "Sample Entity — rename me" so it cannot be mistaken for real information; leaving it in place, or getting the country or industry wrong, means every later suggestion is built on the wrong foundation — a mistake that often is not caught until an auditor or a regulator asks a question the system cannot answer correctly.

How to do it
  1. Open the Organisation screen and click Edit on the sample company.
  2. Replace the placeholder name with the company’s real, legal name.
  3. Give it a short internal code (used later when importing spreadsheets, so the system can match rows to the right company without any guesswork).
  4. Pick its country — this decides whose laws apply — and its industry, which narrows down which rules are even relevant.
  5. Save. The change appears everywhere instantly, including the small company-picker at the top of every screen.
How it connects to the rest of the system

This is arguably the single most important step in the whole setup, because the country and industry recorded here quietly drive several later decisions: which regulations get suggested, which safeguards make sense, and later, which board and committee rules apply.

What the AI does here

No AI runs in this step — it is a direct human action.

Before: the Setup workspace itself, with the entity picker at the top still reading "Sample Entity — rename me" — the placeholder the next screenshot replaces.
Before: the Setup workspace itself, with the entity picker at the top still reading "Sample Entity — rename me" — the placeholder the next screenshot replaces.
The edit screen: name, internal code, type, ownership percentage, country, industry, and whether the company is publicly listed on a stock market — all on one card.
The edit screen: name, internal code, type, ownership percentage, country, industry, and whether the company is publicly listed on a stock market — all on one card.
Renamed to Meridian Gulf Holding — Saudi Arabia, Retail. The country is what decides which regulators the next step suggests. Nothing else on this screen needed to change for the rest of the setup to work correctly.
Renamed to Meridian Gulf Holding — Saudi Arabia, Retail. The country is what decides which regulators the next step suggests. Nothing else on this screen needed to change for the rest of the setup to work correctly.

With the company correctly named, Rania ran the guided setup checklist — an eight-part guided sequence that, step by step, builds the group’s structure, switches on the rules that actually apply, brings in supporting documents, lets the AI draft a first version of the detailed rules, adds the rest of the team, and gives everything one last look before any of it becomes official.

3Mapping out every company in the group

Why we do this

A holding company is legally and financially responsible for its subsidiaries, and different countries mean different laws apply to different parts of the same group. Getting the ownership structure wrong here — attaching a business unit to the wrong parent, or leaving an entity out altogether — means the wrong rules end up applied to the wrong part of the business, and responsibility for a risk or a finding gets assigned to the wrong company. This is also the structure a bank, an investor or a regulator expects to match the company’s own legal registration exactly.

How to do it
  1. Open the guided setup checklist and reach the "organisation structure" step.
  2. Add each company by hand — name, type (subsidiary or business unit), which company it reports up to, country, industry — or,
  3. For a group of any real size, upload a simple spreadsheet listing all of them at once, and let the system build the whole tree automatically.
  4. The system checks the parent references itself, so each row is placed under the parent the file names.
How it connects to the rest of the system

This structure feeds directly into three later things: which rules get suggested for each company (the next step), who is ultimately responsible for each company (covered in "positions", later in this chapter), and which company any future safeguard, rule or risk gets attached to.

What the AI does here

No AI reads or interprets the spreadsheet here. Importing the structure is a straightforward, deterministic parse of rows and columns, and the parent-reference check that follows it is ordinary code checking that the tree makes sense — not an AI judging it.

The checklist opens with a simple welcome step — pick a display language, confirm the parent company’s name, move on.
The checklist opens with a simple welcome step — pick a display language, confirm the parent company’s name, move on.
The organisation-structure step, empty. Rows can be typed by hand or brought in from a spreadsheet.
The organisation-structure step, empty. Rows can be typed by hand or brought in from a spreadsheet.
The same step after uploading a three-row spreadsheet: a retail company in Saudi Arabia and a logistics company in the UAE, both legal entities, and a small trading unit in Qatar, a business unit rather than a company of its own. All three sit under the parent the file names, the holding.
The same step after uploading a three-row spreadsheet: a retail company in Saudi Arabia and a logistics company in the UAE, both legal entities, and a small trading unit in Qatar, a business unit rather than a company of its own. All three sit under the parent the file names, the holding.

4Switching on the rules that actually apply to you

Why we do this

Missing a regulation that genuinely applies is a real business exposure — a fine, a breached licence condition, or a finding an auditor raises that the board has to explain. Chasing down every regulation that might conceivably apply, on the other hand, wastes real time on rules the company was never actually subject to. Matching the country, industry and listing status recorded in the previous steps against a maintained list of regulators narrows that down to the ones genuinely relevant, so the only real decision left for a person is confirming each match is right for their business.

How to do it
  1. Based on the country and industry entered earlier, the system already suggests the regulators and laws that are likely to apply.
  2. Tick the ones that genuinely do — for this company, the country’s cyber-security authority and its data-protection law.
  3. Each one that gets switched on brings a small starter set of specific, individual rules along with it automatically.
  4. Anything already switched on earlier shows as done and cannot be accidentally duplicated.
How it connects to the rest of the system

Turning one of these on is what actually creates entries in the company’s "rules to follow" list, and — a couple of steps later — triggers the very first suggestions for which existing safeguards already satisfy each one.

What the AI does here

This step deliberately runs no AI. Matching a country, industry and listing status against a maintained list of regulators is a precise, rules-based lookup with one correct answer — not a judgement call an AI would improve on. The judgement that does belong to a person here is confirming that a suggested regulator is genuinely right for their business before switching it on — naming a regulator the list does not already know about is a different action, and it does use AI (the next step shows it).

Four rulebooks are suggested purely from the company’s own country and industry — three Saudi authorities and one voluntary international certification.
Four rulebooks are suggested purely from the company’s own country and industry — three Saudi authorities and one voluntary international certification.
Two are ticked. The wording is deliberately plain: importing "adds the regulator’s starter requirements; Zemam then drafts control mappings as PROPOSALS for your review — nothing applies itself."
Two are ticked. The wording is deliberately plain: importing "adds the regulator’s starter requirements; Zemam then drafts control mappings as PROPOSALS for your review — nothing applies itself."

5Bringing in your own documents, or simply naming a standard

Why we do this

Plenty of the rules a company actually has to follow do not come from a well-known regulator with a ready-made template — they come from a specific contract, an internal policy the company adopted voluntarily, or a certification a customer or bank requires proof of. If bringing those in were harder than switching on a well-known regulator, they would tend to get skipped, and the company would end up formally managing only the easy, well-known rules while a real — sometimes more urgent — obligation went untracked.

How to do it
  1. Either upload the actual document — a PDF or a scanned image of the law or standard — and let the system read it, or
  2. Simply type the name of a standard or regulation, even if you don’t have a copy of the text, and let the system confirm it is a real, specific, recognised one before accepting it.
How it connects to the rest of the system

This step feeds the very next one directly: every rule the system goes on to draft has to say exactly where it came from, and this is where that "where" gets established for the first time.

What the AI does here

This is one of the moments the AI is doing real, visible work. When a standard is simply named, an AI checks that it is a real, specific standard (not a vague guess), gives it a proper reference, and this runs as a short, visible process of about two seconds, which the corner panel lists from the next step on — the same cost and the same wait a live customer would see. When a document is uploaded instead, an AI reads it and pulls out the individual rules one by one, each tied back to the exact page or clause it came from.

The choice: upload a document for the AI to read and extract rules from, or simply name a standard you don’t have the text of.
The choice: upload a document for the AI to read and extract rules from, or simply name a standard you don’t have the text of.
Naming "SAMA Cyber Security Framework" and clicking Verify. The run it starts appears in the small corner panel from the next step on, with its own running time — a real run, not a mock-up of one.
Naming "SAMA Cyber Security Framework" and clicking Verify. The run it starts appears in the small corner panel from the next step on, with its own running time — a real run, not a mock-up of one.

6Letting the AI write a first draft — and why nothing is final yet

Why we do this

Turning a lengthy regulation or standard into individual, checkable rules by hand is slow, repetitive work, and doing it manually for the first time is exactly the moment something is most likely to be missed or misread. Producing a complete first draft automatically removes that transcription risk and the delay that comes with it — provided the result is never treated as final until a person has actually checked it. That check is not a formality: it is what stops a mistaken or incomplete AI draft from silently becoming an official rule the company is now expected to follow.

How to do it
  1. Click one button to ask the system to draft the individual rules behind the standard just named.
  2. Wait a few seconds while the AI reads and works through the material.
  3. Every single rule it proposes arrives already marked "pending review" — waiting on a person — and none of them counts until a person decides on it.
How it connects to the rest of the system

Every drafted rule lands in one shared "things waiting for a decision" list used by the whole company (this is explained fully in Chapter 4). Whatever approval level the company runs at, no AI draft becomes an official rule without a person’s recorded decision; from the maker-checker level up, that person is never the one who asked for the draft.

What the AI does here

This step IS the AI at work. It reads the source text and proposes each individual rule in plain language, with a short note explaining its reasoning; a rule drafted from an uploaded document also links back to the exact place in it that the rule came from. In the run pictured here, one framework yielded its rules in a matter of seconds.

Before drafting: one named standard is queued and ready.
Before drafting: one named standard is queued and ready.
After one click: real rules drafted from the named standard, each "Pending review". Nothing here is official yet — it is all a draft awaiting a human decision.
After one click: real rules drafted from the named standard, each "Pending review". Nothing here is official yet — it is all a draft awaiting a human decision.

7Adding the rest of the team

Why we do this

A single person holding every kind of access is itself a risk a bank, an insurer or an auditor will flag — among other things, it means nobody is actually checking anybody’s work. Giving each colleague a specific job, rather than the same broad access to everyone, is what makes a check by a second person — the maker-checker level of step 8 — possible at all, and it limits what any one account can see or change to only what that person’s actual job requires.

How to do it
  1. For each colleague, type their work email and their name.
  2. Pick what job they do at the company — this single choice decides exactly what they will and will not be able to see or change everywhere else in the system.
  3. This can all be done right inside the same guided checklist, so nobody has to remember to circle back and do it separately later.
How it connects to the rest of the system

Everyone added here immediately becomes a candidate to review the drafted rules from the step above, and their choice of job here is what the rest of this manual is actually about — five different colleagues, five different views of the exact same company.

What the AI does here

No AI runs in this step — it is a direct human action.

The team step of the setup checklist, before anyone is added: Add another user opens a row for each colleague, and the screen asks for at least two people with approval rights.
The team step of the setup checklist, before anyone is added: Add another user opens a row for each colleague, and the screen asks for at least two people with approval rights.

8Understanding the approval rules

Why we do this

When a board member, an outside auditor or a regulator asks who approved a decision and who checked it, the answer needs to be verifiable, not just asserted. That is why the review rules are stated before anything is approved: everyone can see in advance how many people an item needs, and how strict the company is remains a recorded decision of its holding admin, never something any one user can quietly switch off for a decision they would rather approve alone.

How to do it

This step is read-only by design. It states the three approval levels and lists who currently qualifies to approve. At the lowest level, where a workspace opened by signing up starts, one person’s action is enough, and that person may be the one who drafted the item. From the maker-checker level up, whoever drafts an item never approves it, and at the highest level two DIFFERENT approvers must sign off, not one person twice. Some items — spending-authority lines, and AI drafts whose source could not be fully verified — always take the strictest path, whatever the level.

How it connects to the rest of the system

These are the same levels enforced everywhere they apply — requirements, safeguards, risks, objectives, findings, spending-authority lines and exceptions — not something set differently screen by screen. Step 15 shows where Rania raises the level once a reviewer is on the team, and Chapter 4 shows a decision being made for real.

What the AI does here

No AI runs here. The levels are rules the system enforces, and how strict to be is a person’s decision, never left to an AI’s discretion.

The three approval levels — one approver at the lowest, someone other than the drafter at maker-checker, two distinct approvers at the highest — and who currently holds the right to approve.
The three approval levels — one approver at the lowest, someone other than the drafter at maker-checker, two distinct approvers at the highest — and who currently holds the right to approve.

9One last look, then making it official

Why we do this

A single setup session can create several new companies, several new user accounts and a dozen new rules in one action — exactly the kind of bulk change that is hard to untangle later if something goes wrong partway through. A final review before anything is written, followed by a receipt that confirms each item individually rather than one generic success message, is what lets the person responsible actually verify what was created, item by item, instead of trusting that a single "success" covered everything correctly.

How to do it
  1. Scroll through a plain-English summary of every section entered so far.
  2. Click the final "Confirm & finish" button.
  3. Wait a few seconds while the system creates everything for real.
  4. A checklist confirms each individual item — each company, each rulebook — rather than one overall tick, so a problem with any single item would be named specifically rather than hidden inside a general failure.
How it connects to the rest of the system

This is the exact moment everything from the steps above stops being a draft inside this one checklist and becomes a real, permanent record used across the whole system — visible immediately on the organisation chart, the people list, the daily dashboard, and the queue of things awaiting review.

What the AI does here

No AI runs at the point of confirming. Everything AI-assisted in this checklist already happened earlier, in step 6; this step only writes down, permanently, what a person has already reviewed on screen.

The final review screen: every section, one more time, with nothing written yet.
The final review screen: every section, one more time, with nothing written yet.
Done. The three companies and the two rulebooks, each with its own checkmark, and a note that the mapping run has started: its drafts arrive in the Review Queue, and nothing is applied without approval.
Done. The three companies and the two rulebooks, each with its own checkmark, and a note that the mapping run has started: its drafts arrive in the Review Queue, and nothing is applied without approval.

Checking the results

10Recording a contract, and seeing what it commits the company to

Why we do this

A contract binds a company as surely as a regulation does — a customer agreement can require a breach to be reported within days, a supplier agreement can require an annual audit — and those duties are easy to lose inside a signed document nobody re-reads. Recording the contract beside the laws and standards, with its end date, puts its obligations in the same register as everything else the company must meet, and makes a contract about to end visible before it lapses rather than after.

How to do it
  1. On the Requirement sources screen, upload the contract and mark it as a contract, with the date it takes effect and its end date. The setup checklist has no contract option, so this is done after it.
  2. Open Run compliance, then Contracts. The contract is listed with how many obligations come from it and when it ends; one ending within 30 days is marked with the days that remain.
How it connects to the rest of the system

The obligations count only what is already official. Those the AI drafted from this contract wait in the Review Queue, so the count is 0 until a draft is approved and applied, and it rises with each one — the approval rules of step 8, now reaching contracts.

What the AI does here

An AI read the contract’s text and drafted the obligations it places on the company, each one a draft for a person to check. None of them counts until a person’s recorded decision makes it official.

The contract, marked with the days left before it ends. Its obligations read 0 for now: nobody has applied a draft yet, and the obligations the AI drafted from its text wait in the Review Queue.
The contract, marked with the days left before it ends. Its obligations read 0 for now: nobody has applied a draft yet, and the obligations the AI drafted from its text wait in the Review Queue.

11Confirming the company structure looks right

Why we do this

An automated step is only as good as the result it actually produces, and the only way to know the company’s structure was captured correctly — rather than assumed to be correct — is for a person to look at it. This is the same check a manager would run after delegating any task: not redoing the work, just confirming it came out right before relying on it.

How to do it
  1. Open the Organisation screen again. All four companies should now be listed, each with its correct country, industry and ownership percentage.
  2. Then open Govern, Objectives, and record what the group is trying to achieve: a strategic objective for the whole group and, under it, the objective it breaks down into. In the Risk register, the sample risk’s card takes that objective as the one it threatens; the sample safeguards already linked to that risk came with the starter pack. Only a holding admin can record or change an objective; in Chapter 2, Layla reads them.
How it connects to the rest of the system

Every screen elsewhere in the system that lets someone pick "which part of the company does this belong to" is reading directly from this same list.

What the AI does here

No AI is involved in checking the result — this is a person visually confirming that an earlier step produced what was intended.

All four: the holding, and the three read in from the spreadsheet — two subsidiaries and a business unit — each carrying its own country, industry and the share the parent holds.
All four: the holding, and the three read in from the spreadsheet — two subsidiaries and a business unit — each carrying its own country, industry and the share the parent holds.

12Confirming everyone has the right job

Why we do this

Access that is too broad is a control weakness an auditor will raise; access that is too narrow means someone cannot do the job they were hired to do. One screen listing every colleague and exactly what job they were given makes it possible to catch either mistake immediately, rather than discovering it months later when someone could see — or could not do — something they should not have been able to.

How to do it
  1. Open the Users & roles screen. Every colleague added is listed with their roles (or "No role"), how they sign in, and whether their access is active.
  2. If a job is wrong, Change access on that person’s row corrects it. Someone who leaves is deactivated, never deleted: they lose access within a minute, and their past work and the audit trail stay as they are. Nobody can change their own access.
How it connects to the rest of the system

This is the same list the approval rules of step 8 check against every time something needs an approver.

What the AI does here

No AI runs here either. Confirming access was granted correctly is exactly the kind of check that should be done by a person, not delegated to one.

All six people, each one active, all signing in with the same shared starter password until each person is given their own. Five hold a role, Sara two of them, and Youssef’s row reads "No role". Every row but Rania’s own carries Change access.
All six people, each one active, all signing in with the same shared starter password until each person is given their own. Five hold a role, Sara two of them, and Youssef’s row reads "No role". Every row but Rania’s own carries Change access.

13Understanding that responsibility belongs to a job, not a person

Why we do this

People change roles, get promoted and leave; the rules, safeguards and risks they were responsible for do not stop mattering when they do. Tying responsibility to a job title rather than to whichever individual currently holds it means a resignation or a reorganisation never leaves something silently unowned — the system either shows exactly who now holds that job, or states plainly that the seat is empty and shows who is accountable for it in the meantime.

How to do it
  1. Open the Positions screen. The system has already created one "head" seat for every company automatically.
  2. A person can be assigned to sit in that seat, and moved out of it later without anything they were responsible for simply vanishing.
  3. If a seat is empty, the system says so in plain terms — as a real gap — rather than hiding it.
How it connects to the rest of the system

This is a foundational layer underneath almost everything else in the system: every safeguard, every rule, and every risk is owned by a JOB, and only indirectly by whoever currently happens to hold it. When a seat is empty, responsibility is shown moving up to whoever that job reports to, so nothing is ever silently unowned.

What the AI does here

No AI decides who is responsible for what. Positions and reporting lines are structural facts about the company that a person records directly.

Every company’s "head" seat, automatically created. Three are still empty — named as real gaps, with the system showing who inherits the responsibility in the meantime.
Every company’s "head" seat, automatically created. Three are still empty — named as real gaps, with the system showing who inherits the responsibility in the meantime.

14The daily dashboard — the company’s health at a glance

Why we do this

A manager who has to open a dozen separate screens every morning to judge whether things are broadly on track will eventually stop checking, and a genuine problem will sit unnoticed until it is expensive to fix. One screen that states plainly how much of the required work is done, how many safeguards are confirmed working, and the size of the company’s largest known exposure is what makes a daily check realistic rather than a chore that gets skipped.

How to do it

Open the Dashboard. It shows how many of the audit-readiness steps are complete, how many safeguards are actually confirmed to be working, the size of the company’s biggest known financial exposure, and a plain log of what the AI has actually done recently.

How it connects to the rest of the system

Every number on this screen is read live from the same records built in the steps above — nothing here is a separate, disconnected report.

What the AI does here

The dashboard itself runs no AI — it simply reports, honestly, what earlier AI-assisted steps actually did (with real timestamps and how long each one took), rather than hiding that work behind the scenes.

The audit-readiness steps completed so far, a real starter risk sized at 270,000 Saudi riyals a year, and a genuine, timestamped log of the AI activity from the steps above.
The audit-readiness steps completed so far, a real starter risk sized at 270,000 Saudi riyals a year, and a genuine, timestamped log of the AI activity from the steps above.

15Settings — the few things every company configures once

Why we do this

A handful of decisions apply to the whole company rather than to any one screen — how outgoing mail is sent, how strict approvals need to be, the company’s time zone, and how much AI it is using. Keeping those together in one place, rather than scattered across the screens they happen to affect, means whoever is responsible for the company’s overall configuration can find and review all of it without having to remember where each setting lives.

How to do it

Open Settings. Each of those is its own clearly labelled tab — My AI keys, time zone, Trust Center access requests, email server, approvals, usage and the regulatory watch key. Which AI serves the workspace is set by the platform’s operator, not here. Nothing needs to be touched immediately, but everything is there when it does.

How it connects to the rest of the system

The Approvals tab sets the level step 8 described. A workspace opened by signing up starts at the lowest, where one person’s action is enough; once a reviewer is on the team, this is where Rania raises it to maker-checker, so that whoever drafts an item can no longer approve it.

What the AI does here

No AI runs on this screen. These are fixed configuration choices a company makes once and revisits rarely, not decisions an AI would meaningfully assist with.

Settings opens on My AI keys; along the tabs are the time zone, Trust Center access requests, the email server, the approval level, AI usage and the regulatory watch key.
Settings opens on My AI keys; along the tabs are the time zone, Trust Center access requests, the email server, the approval level, AI usage and the regulatory watch key.

16The inbox of things waiting on a human decision

Why we do this

An approval that is easy to overlook is, in practice, an approval that never happens — and a rule or a safeguard match nobody ever reviews stays a draft indefinitely, even while the company may already be acting as though it were official. One shared, filterable inbox for everything awaiting a decision, rather than notifications scattered across different screens, is what makes it realistic for a company to actually keep up with its own review backlog.

How to do it

Open the Review Queue. Every pending item from the earlier steps is listed there, filterable by type and by how sensitive it is — and a set of filters you return to can be saved under a name, so tomorrow it is one click rather than four. Long queues are paged, so nothing sits past the end of the first screen unreachable.

How it connects to the rest of the system

This is the exact same queue every other colleague in this manual sees, filtered to what each person is actually allowed to act on — Chapter 4 shows a colleague actually working through it.

What the AI does here

Opening the queue runs no AI itself — it lists work AI already did elsewhere, waiting for a person’s decision. Chapter 4 shows that decision actually being made.

Everything drafted in the steps above, waiting for a person to make the final call.
Everything drafted in the steps above, waiting for a person to make the final call.

Chapter 2 — Governance Officer: Boards, Committees and Policy

Layla Hassan runs the parts of the business that are about oversight rather than day-to-day operations — the board itself, its committees, and the policies the company is legally expected to hold — and follows the company objectives and spending-authority limits a holding admin records. Her screen looks the same as Rania’s, but what she is allowed to change is different: she records the board, its committees, its decisions and formal exceptions, and reads the objectives and spending-authority limits without changing them.

1Seeing a different set of doors, from the same front hall

Why we do this

Every colleague using the same product, with only their own permissions different underneath, means the company does not have to run separate systems — or separate training — for each job function. It also means nobody ends up able to change something outside their own responsibility simply because it happened to be visible on their screen.

How to do it

Layla signs in with her own account. The role shown next to her name, top right, is what actually decides what she can change — not anything she picks herself.

How it connects to the rest of the system

This is the same layout every colleague in this manual sees; what differs follows the job chosen for each person back in Chapter 1. Layla’s menu has no Audit Trail, for instance, and her screen opens on her own view.

What the AI does here

No AI runs at sign-in. The role shown is a fixed fact about the account, decided when the person was added in Chapter 1.

Layla’s starting screen — same layout as Rania’s, different role badge, different rights underneath.
Layla’s starting screen — same layout as Rania’s, different role badge, different rights underneath.
Govern, the area she works in: company objectives, spending-authority limits, required policies, the board register, boards and committees, and formal exceptions. Objectives and spending-authority limits are recorded by a holding admin; she reads them.
Govern, the area she works in: company objectives, spending-authority limits, required policies, the board register, boards and committees, and formal exceptions. Objectives and spending-authority limits are recorded by a holding admin; she reads them.

2Reading the chain from what the company wants to what protects it

Why we do this

A board asks two questions about any objective: what could stop us, and how do we know the safeguard against it works? An answer assembled by hand from four registers arrives late and is rarely complete. A chain that runs from the group’s strategy, through the objective beneath it and the risk that threatens it, to the safeguard against that risk and its latest result, answers both on one screen.

How to do it
  1. Open Objectives under Govern, choose the objective Rania recorded under the group’s strategy, and open its Chain tab.
  2. The chain shows, in order: the strategic objective above it, the objective itself, the risk that threatens it, the safeguards linked to that risk, and each safeguard’s latest result at each of the three lines. Here those results came with the starter pack as samples, and a line no result has reached says so rather than leaving a gap.
How it connects to the rest of the system

Layla reads this chain; she does not build it. The objectives were recorded by a holding admin in Chapter 1, the risk is linked to its objective in the risk register, and each result comes from a test or, as here, came with the starter pack as a sample, so the chain is never a separate diagram someone has to keep up to date.

What the AI does here

No AI draws the chain or decides what is in it. It reads the records as they stand: the objectives and the risk’s objective were recorded by a person, the risk’s safeguards and their results came with the starter pack as samples, and once a test records a real result, the chain shows that instead.

The chain for the objective Rania recorded: the group strategy above it, the risk that threatens it, the safeguards linked to that risk, and their results, which came with the starter pack as samples.
The chain for the objective Rania recorded: the group strategy above it, the risk that threatens it, the safeguards linked to that risk, and their results, which came with the starter pack as samples.

3Recording the board, and seeing exactly what is missing

Why we do this

A company is routinely expected to demonstrate that it has a properly constituted board — the right number of members, an independent chair where one is required, someone keeping formal minutes — and being unable to answer that question quickly, with evidence, is itself a governance weakness a regulator or an investor will note. Stating the gaps plainly before they are fixed, rather than only after an audit finds them, is what lets a governance officer close them on the company’s own timeline instead of an inspector’s.

How to do it
  1. Open Boards & committees. Before anything is recorded, the system already names the gap plainly — "no board recorded" — for each company that should have a board. A business unit carries no board of its own, so it is not assessed.
  2. Record a Board of Directors from a ready-made template (a template simply pre-fills the usual minimum — at least three members, one of them keeping the minutes — so nobody has to know those numbers from memory). Once it is recorded, the board is checked against that rule: with nobody on it yet, it reads "too few members," "no chair" and "no secretary."
  3. Appoint a chair. Marking someone as an "independent" chair specifically requires writing down, in a sentence, why they qualify as independent — not just ticking a box.
How it connects to the rest of the system

The gaps and progress shown here are not a separate report someone has to remember to check — the exact same figures drive the notification bell every relevant colleague sees, so nothing here can quietly disagree with what a manager is told elsewhere.

What the AI does here

No AI decides whether a board meets the requirements. The gaps shown — no board recorded, too few members, no chair, no secretary — come from a fixed set of governance rules the system applies the same way for every company, not from an AI’s judgement.

Before anything is recorded: three real gaps, one for each company that should have a board and has none. The business unit in Qatar carries no board of its own, so it is not assessed.
Before anything is recorded: three real gaps, one for each company that should have a board and has none. The business unit in Qatar carries no board of its own, so it is not assessed.
Appointing Layla as Chair, marked Independent, with the required written justification for why she qualifies.
Appointing Layla as Chair, marked Independent, with the required written justification for why she qualifies.
Immediately afterwards, with Layla as the board’s independent chair: "no chair" is gone from the list of problems. The board’s other two — too few members, and no secretary — are still shown, as is "no board recorded" for the two other companies, because they all still genuinely exist.
Immediately afterwards, with Layla as the board’s independent chair: "no chair" is gone from the list of problems. The board’s other two — too few members, and no secretary — are still shown, as is "no board recorded" for the two other companies, because they all still genuinely exist.

4Policies and spending-authority limits

Why we do this

Two more things regulators and boards commonly expect: a written policy for certain topics (say, information security or anti-bribery), and clear limits on who is allowed to approve spending or sign contracts up to what amount. Not knowing, at any given moment, exactly which of those the company already has is itself a gap worth closing before an auditor or a bank asks the question first.

How to do it

Open the Policy matrix to see which required policy topics are covered and which are not; open Delegation of Authority to see the planned approval-limit ladder once the company’s first spending rules are drafted.

How it connects to the rest of the system

A confirmed policy on this screen is what later allows a colleague to be asked to formally acknowledge they have read it — a separate, later step not covered in this manual.

What the AI does here

No AI runs here. Which policies exist and what the spending-authority ladder looks like are both facts the company records directly, not something an AI infers.

Which required policy topics the company holds a policy for. None yet, so every topic listed reads Gap.
Which required policy topics the company holds a policy for. None yet, so every topic listed reads Gap.
Where the approval-limit ladder will live. No authority matrix is recorded yet, so nothing here governs who may authorise what until the company’s first spending rules exist.
Where the approval-limit ladder will live. No authority matrix is recorded yet, so nothing here governs who may authorise what until the company’s first spending rules exist.

Chapter 3 — Auditor: Read Everything, Change Nothing

Omar Al-Sabti is the company’s internal auditor. His job is deliberately the most restricted in the system: he needs to be able to see absolutely everything, in order to check it independently, but he must not be able to change any of it — not even upload a single piece of supporting evidence. That restriction is the entire point of the role, and it is enforced by the system itself, not by anyone’s good behaviour.

1A screen that tells you plainly what you cannot do

Why we do this

An internal auditor’s opinion is only worth relying on if they could not have quietly influenced the thing they are checking — that independence is the entire value of the role. Stating the restriction on screen, rather than leaving it to the auditor’s own discipline, is what makes that independence something the company can actually demonstrate to a board or an external auditor, not just something it claims.

How to do it

Omar signs in. Every one of the five areas of work is explicitly labelled "Read-only for your role" — not hidden, just visibly locked to viewing only.

How it connects to the rest of the system

This is enforced by the same job-based permission system used for every colleague in this manual — Omar sees the identical screens everyone else does, with writing switched off underneath, not a stripped-down version.

What the AI does here

No AI decides what an auditor can see or change. Access is fixed by the job assigned to the account back in Chapter 1, the same way it is for every other role.

Every one of the five areas explicitly marked read-only — stated, not just assumed.
Every one of the five areas explicitly marked read-only — stated, not just assumed.
Coverage, safeguard testing, evidence, findings and audit readiness — all visible, none editable.
Coverage, safeguard testing, evidence, findings and audit readiness — all visible, none editable.

2What "read-only" actually means when someone tries anyway

Why we do this

A restriction that has never actually been tested is a restriction nobody can vouch for. When someone in a read-only role genuinely attempts a change their role should not allow, getting a clear, specific refusal — rather than a confusing error — is what turns "auditors cannot write to the register" from a policy statement into something demonstrably true.

How to do it

Omar tried to upload a piece of supporting evidence, exactly as an auditor doing real work might reasonably attempt.

How it connects to the rest of the system

The refusal did not hide the drop-zone or pretend the option was never there — it explained, in the product’s own words, exactly why the action was blocked.

What the AI does here

No AI is involved in the refusal — it is a straightforward permission check, the same one that would refuse the same action from anyone in a read-only role.

The plain refusal: "Auditors and consultants have read-only access." This is the system’s own stated rule, not a guess from outside.
The plain refusal: "Auditors and consultants have read-only access." This is the system’s own stated rule, not a guess from outside.

3Reading the record of everything that has happened

Why we do this

An auditor’s core job is confirming what actually happened, when, and by whom — which is only possible if a complete record exists and cannot have been quietly edited after the fact. A record that every action anywhere in the system writes to automatically, rather than one assembled separately when someone asks for it, is what makes it credible as evidence rather than a summary produced for the occasion.

How to do it

Open Coverage to see which rules the current safeguards actually address, and the Audit Trail to see every action taken anywhere in the company’s account so far — filterable by object and by date range, paged, and exportable as a spreadsheet. The export is the whole filtered set rather than the page on screen, and if the set is larger than one file will carry, the file’s own first lines say so and tell you to narrow the dates.

How it connects to the rest of the system

The audit trail is not a separate log kept "for auditors" — it is the same record every action anywhere in the system writes to automatically, which is exactly what makes it trustworthy as evidence. The count shown is the number of events that MATCH the filters, not the number visible on screen, so a reader is never quietly looking at a slice they believe is the whole.

What the AI does here

No AI decides what goes into the audit trail — every action writes to it automatically and permanently, whether or not AI was involved in the original action itself. The Coverage screen is different: the panel in its corner lists the AI runs behind the suggestions, among them the mapping run that matched the rules against the safeguard catalogue, each with its own running time.

The Coverage screen, before a fresh run: the mapping suggestions already waiting in the shared Review Queue are counted here, with a plain warning that re-running adds nothing while they are undecided — and the panel in the corner shows the AI runs that produced them — regulatory mapping, requirement extraction, standard verification — each with its own real running time.
The Coverage screen, before a fresh run: the mapping suggestions already waiting in the shared Review Queue are counted here, with a plain warning that re-running adds nothing while they are undecided — and the panel in the corner shows the AI runs that produced them — regulatory mapping, requirement extraction, standard verification — each with its own real running time.
Every action so far — sign-ins, board appointments, drafted rules — filterable by object and by date, and exportable in full, visible to the one role that must never be able to edit it.
Every action so far — sign-ins, board appointments, drafted rules — filterable by object and by date, and exportable in full, visible to the one role that must never be able to edit it.

Chapter 4 — Reviewer: Closing the Loop on an AI Draft

Maha Al-Zahrani’s job in the system is the decision at the end of every AI draft: an AI may draft a rule or suggest that a safeguard satisfies it, but only a person’s recorded decision can let that draft become part of the company’s official record. At the company’s current approval level, whoever asked for a draft could decide on it too; Rania chose to have a second person decide, and that person is Maha.

1Opening the shared inbox of pending decisions

Why we do this

An AI-drafted rule or safeguard match that nobody is required to look at will, in practice, sit there unreviewed indefinitely — and until it is reviewed, the company has no official position on it either way. A single, visible queue covering the whole company is what makes that promise — that nothing an AI produces becomes official unchecked — something that can actually be verified, rather than simply asserted.

How to do it

Maha signs in and opens the Review Queue. Every pending item across the whole company is listed, filterable by status, type, how sensitive it is, and whether its source citation has been double-checked — and because a reviewer returns to the same few filters every morning, a filter set can be saved under a name and re-applied in one click.

How it connects to the rest of the system

This is the identical queue shown to Rania in Chapter 1 (step 16) — the same underlying list, simply seen through a different colleague’s permissions.

What the AI does here

Opening the queue runs no AI itself — it lists items that earlier AI-assisted steps produced (drafting rules, matching safeguards to rules), each still waiting for the human decision this chapter is about.

Maha’s starting screen, reviewer role.
Maha’s starting screen, reviewer role.
The queue of items waiting on a decision — filterable by status, type, sensitivity and whether the source has been verified, with the filter set savable under a name.
The queue of items waiting on a decision — filterable by status, type, sensitivity and whether the source has been verified, with the filter set savable under a name.

2Making a real decision on an AI-drafted item

Why we do this

A reviewer who is only shown a yes/no button, with none of the reasoning behind it, is not really exercising oversight — they are rubber-stamping. Showing the full reasoning, letting the reviewer adjust the wording before deciding, and recording "approve" and "make this official" as two separate events, even where one click does both, is what makes the review a genuine check rather than a formality on the way to the same outcome regardless.

How to do it
  1. Open the first pending item. The full AI reasoning is shown: which safeguard it matched to which rule, how confident it is, and a plain-English justification.
  2. A second panel shows an editable "your version" — Maha can adjust the wording herself before deciding, rather than only accepting or rejecting the AI’s exact words.
  3. An optional second AI opinion can be requested for a further sanity check before deciding.
  4. Click Approve. At this company’s approval level, approving an item like this one also applies it: it becomes part of the official record at once, and the approval and the application are both recorded. From maker-checker up, Apply to the register is a separate step.
  5. The item now carries a permanent link to the exact AI draft it came from.
How it connects to the rest of the system

A small note on the drawer — "no past decisions used" — shows this is the very first decision of its kind in this company’s account; from here on, the system can start learning the company’s own patterns of past decisions to inform future AI suggestions, without ever skipping the human step.

What the AI does here

The AI did all of the original analytical work being reviewed here — reading a rule, finding the safeguard that satisfies it, judging how completely it does so, and writing the justification — but the AI has no ability to make this decision final. Only Maha’s decision does that, recorded as an approval and an application.

A real AI-drafted match: one safeguard against one specific rule, full confidence, a plain-English justification, and an editable "your version" panel before any decision is made.
A real AI-drafted match: one safeguard against one specific rule, full confidence, a plain-English justification, and an editable "your version" panel before any decision is made.
The same item, fully closed out: "Applied to the register", with a permanent link back to the exact AI draft behind it. The shared inbox count falls as each decision lands.
The same item, fully closed out: "Applied to the register", with a permanent link back to the exact AI draft behind it. The shared inbox count falls as each decision lands.

Chapter 5 — Library Steward: A Reviewer With One Extra Right

Sara Al-Qahtani has every right Maha has, plus the one the product names for her role: she “approves shared-library promotions in addition to reviewer rights.” A shared-library promotion is a draft meant for the library that other companies — and accredited outside advisory firms — can adopt instead of starting from a blank page, and any such draft needs a library steward among its approvers. No screen raises one today, so in this guide Sara reviews as Maha does, and this chapter shows what she sees when she follows Maha’s decision to where it now lives.

1Following an approved connection to where it now lives

Why we do this

A reviewer’s approval is only worth something if anyone can later find what it changed. When the connection approved in Chapter 4 can be opened from the safeguard itself, with the rule it satisfies named by its code, an auditor, a manager or the next reviewer can check the record without asking who approved what, or digging through an inbox.

How to do it
  1. Open the Libraries screen. It lists the company’s own safeguards by code, title, statement and owner.
  2. Open, by its code, the safeguard in the connection Maha approved in Chapter 4. Its fact sheet lists, under Obligations addressed, the rule it was matched to — the connection Maha applied — and, under Risks mitigated, the starter pack’s sample risk it was already linked to.
  3. Its header shows the result that came with the starter pack, labelled Sample result, beside Never tested. That is deliberate: the sample’s result is shown, but it is not a test this workspace ran, so only a real test says when the safeguard was last tested.
How it connects to the rest of the system

A shared-library promotion is held to a higher bar than any ordinary draft: it is always treated as high-stakes, so it needs two different approvers, and one of them must be a library steward. That is Sara’s extra right. No screen raises such a draft today, so until one does, she reviews exactly as Maha does.

What the AI does here

No AI runs on these screens. The connection Sara opens was drafted by an AI in Chapter 4, and it became official only through Maha’s approval and apply.

Sara’s starting screen — library steward, and notably no "read-only" label, because this is a role that is allowed to write.
Sara’s starting screen — library steward, and notably no "read-only" label, because this is a role that is allowed to write.
The safeguard in the connection Maha approved in Chapter 4, opened from the Libraries screen: under Obligations addressed, the rule it was matched to, by that rule’s code; under Risks mitigated, the starter risk; and in the header, its sample result beside Never tested.
The safeguard in the connection Maha approved in Chapter 4, opened from the Libraries screen: under Obligations addressed, the rule it was matched to, by that rule’s code; under Risks mitigated, the starter risk; and in the header, its sample result beside Never tested.

Chapter 6 — Member: The Everyday View

Youssef Nasser works inside one of the group’s companies day to day. He holds no special role — the Users & roles screen lists him as "No role", which carries the same rights as the "Member" role the add-a-user form offers — and that is the ordinary, everyday seat: no admin rights, no approval rights, just doing his own job within his own part of the business.

1The view most people at the company will actually use

Why we do this

Most people at any real company are not setting up the system or approving board decisions — they are doing their own job and occasionally need to know how their part of the business is doing against its rules and risks. That everyday view has to be built from exactly the same figures as every specialist screen in this guide, not a simplified or delayed copy of them, or a manager and their own team could end up looking at two different pictures of the same company.

How to do it

Youssef signs in and sees the same layout and the same dashboard everyone else does. His starting screen opens on its own view, but the checklist progress and dashboard figures are shared across the whole company, not personalised per person.

How it connects to the rest of the system

Every figure on his dashboard — the size of the shared review inbox, the ongoing log of AI activity — is read live from the exact same records every earlier chapter built and worked with.

What the AI does here

The dashboard itself runs no AI, the same as it does not for Rania in Chapter 1 — it reports, with real timestamps, what earlier AI-assisted steps actually did.

Youssef’s starting screen. Its checklist rings are the company’s, not his own: they show the whole company’s progress, so they move as the company’s work moves.
Youssef’s starting screen. Its checklist rings are the company’s, not his own: they show the whole company’s progress, so they move as the company’s work moves.
The same dashboard every other colleague in this manual has seen, showing the same real, live figures — the number of items now waiting for review, and the same running log of AI activity.
The same dashboard every other colleague in this manual has seen, showing the same real, live figures — the number of items now waiting for review, and the same running log of AI activity.

Screen-by-screen reference

Overview

Overview /

Choose today’s job

What you do here

The welcome screen. It names the view your roles and what your position owns imply — Workspace Admin, Corporate Governance, Internal Audit, Compliance Officer, Risk Manager or Executive — states the one question that view answers, and offers to open there. Beneath it: what is waiting on you, then the five workspaces, all of them, always. A view chooses where you start, never what you may open; change it in Settings. Remembers a workspace choice if you ask it to; the wordmark always brings this screen back. A first sign-in gets a three-step introduction to the rail, the entity picker and Review.

Feeds into

Routes into the five workspaces; shows each one’s getting-started progress.

Dashboard /dashboard

Check the overall posture

What you do here

Live cross-domain posture: controls passing, coverage, evidence, risks and agent activity.

Feeds into

Read-only view over everything else.

Working the screen

Everything here is computed live from the registers — nothing on this page can be edited, and a number you do not like is changed on the screen that owns it. The entity picker in the top bar scopes every figure; if a card looks empty, check which entity you are on before concluding data is missing. A tile whose count includes sample results seeded with the starter pack says how many beside the figure. The tiles count controls by their latest result and the per-entity figures count results, so the two markers name different populations and are never added together. Money figures in different currencies are shown per currency and never added together. Divergence is judged only where loss severity bands exist in a risk's currency; risks in a currency without bands are named as not judged, never counted as agreeing.

Set up

Set up /setup

Start the setup checklist

What you do here

The Set up workspace: getting-started checklist, live setup status, the first-run wizard, and — for admins — the data-sharing switch. Your workspace email server (SMTP), which sends evidence chases and digests from your own domain, is configured in Settings; a pointer here takes you there.

Feeds into

Everything — setup is where structure, frameworks and the team come from.

Working the screen

The same next steps appear in Ask Zemam for a workspace administrator; Guide me there explains, from this workspace's own data, what to set up next and why.

Organisation /setup/organisation

Build the group structure

What you do here

Maintain the group hierarchy, each entity profile, and the departments that own risks, controls and findings.

Feeds into

Framework matching reads the profile; departments appear as owners everywhere; the top-bar entity picker scopes every screen.

Working the screen

Add entities from the tree; each carries the profile (country, sector, listed) that framework matching reads — a wrong sector here means wrong regulator suggestions later. Departments created here appear as owners across risks, controls and findings. An entity with children cannot be deleted; move or delete the children first. The top-bar picker decides which entity every other screen shows.

Frameworks /setup/frameworks

Import the frameworks that apply

What you do here

Discover regulators and frameworks for the active entity; import starter requirements; adopt requirements from the shared Global library other organisations and partners approved; pick AI scout suggestions beyond the catalog to add as verified custom standards.

Feeds into

Libraries (requirements); mapping proposals in the Review Queue.

Working the screen

Suggestions read the ACTIVE entity’s profile — switch entity and the list changes. Import brings starter requirements in directly; Global-library adoptions land the same way and count as your endorsement. An already-imported framework shows a tick instead of a second Import. AI-scout picks beyond the catalog are verified first, then appear under Requirement sources as custom standards.

Requirement sources /setup/sources

Add requirement sources

What you do here

Import standards, versioned policies and board resolutions; the AI drafts requirements as citation-checked proposals; tag policies with topics. Proprietary standards (ISO, PCI…) unlock for full-text upload once you attest a licence you already hold — quotes stay capped at 25 words.

Feeds into

Libraries (requirements); the mandated-policy matrix.

Working the screen

Upload a file or name a standard; the AI drafts requirements as proposals with citations — nothing enters the library until approved in Review. Policies need a version and a date; a newer version supersedes the old, but the old one’s requirements stay in force until the replacement’s drafts are applied — when every draft is applied and none rejected they retire by themselves; otherwise Retire the remaining obligations is offered on the superseded document, one recorded action with its count, refused while any draft is still undecided. Proprietary standards (ISO, PCI…) are refused as uploads unless you attest a licence you hold; quotes stay capped at 25 words. If citation checks come back empty for a document, run Rebuild citation index on it. Changes and deletions follow the same approval level as additions: when the level requires a second person they become a draft for review, and the row stays as it is until the draft is approved. A contract can be uploaded here, marked as a contract, with its end date.

Users & roles /setup/users

Invite the team and reviewers

What you do here

Add users and assign roles, each explained in one line — including why, from the Medium approval level up, a reviewer never approves their own proposal. A holding admin can change a person's roles or deactivate them, and access ends within a minute.

Feeds into

Approval rights across the Review Queue; ownership everywhere.

Working the screen

Roles are explained beside each assignment. The one that matters most: from the Medium approval level (maker-checker) up, a proposer never approves their own item, so the workspace needs at least one other approver before that work can move. Adding a user does not send an invitation email — share the sign-in yourself. Email addresses are unique across the platform. Right after you save a change of your own that applies at once, an Undo button stays beside it for 30 seconds; it puts back what you changed, unless the entry has changed since or the change can no longer be reversed.

Expert help /setup/partners

Engage an accredited firm

What you do here

The expert-help marketplace: browse accredited firms, request an ADVISORY or ASSURANCE engagement, and end one instantly. An independence firewall blocks assurance within 12 months of advisory work by the same firm (and the reverse).

Feeds into

Active engagements let a firm’s consultants work inside your workspace; the shared library’s partner vouches.

Working the screen

Request ADVISORY or ASSURANCE from an accredited firm; your admins can end an engagement instantly. The independence firewall keeps an assurance engagement from going live within 12 months of advisory work by the same firm — in both directions: a conflicted request can never be activated, so it never becomes an active engagement. An active engagement is what lets that firm’s consultants work in your workspace.

Positions /setup/positions

Maintain positions and the structure

What you do here

Maintain the positions that make up each entity — who reports to whom, who holds each seat and since when — and import the whole structure from a spreadsheet. Ownership of controls, obligations, risks, findings and objectives is a position’s, so a vacant seat is visible and its items escalate up the line instead of disappearing with a person.

Feeds into

Owner pickers across the registers; the attention bell (vacant positions); readiness on this page and on Govern home; the assurance graph (positions, holders, reporting lines); engaged consultants appear as external seats.

Working the screen

The page opens on the Chart: the boards and their committees on top, the head of the group, its direct reports, then each subsidiary’s head, a vacant or dormant seat drawn hollow and saying where its work goes. Click a seat to open it beside the chart — holder, reporting line, holders over time, the bodies it sits on, what it owns — or click a board to see its members and readiness. The Table is one click away, and the page remembers your choice in this browser. Every entity is born with a provisional head. Import a CSV to replace provisional seats with the real structure: the preview names every problem at once (two heads, a loop, an orphan) and nothing is written until the file is clean; positions missing from the file are ended, never deleted, and what they own stays and escalates. Seat a holder by picking an account or typing a name; end a tenure with one date — the seat’s items resolve to the next seat up the line (shown here and on the item). Amendments are effective-dated, so the structure on any past date can be reconstructed. External seats come only from activated engagements and cannot be edited here. Functional lines record oversight and dotted-line reporting, including a line to a parent entity’s committee.

Manage risk

Manage risk /risk

Open the risk workspace

What you do here

The Manage-risk workspace: heatmap, appetite line, qualitative-vs-money divergence, objectives at risk, the risk wizards, and shared risk templates other organisations and accredited firms have vetted (import one as a starting point; contribute your own from a risk card).

Feeds into

The register; objectives (the chain); the dashboard.

Risk register /risk/register

Populate the risk register

What you do here

ISO 31000 risk register with FAIR quantification: lifecycle, treatments gated by appetite in scores and money, seeded Monte Carlo analyses reproducible from their stored seed, owners and their feedback, linked controls and residual scores. Switch to the Matrix view (risk × control link states with totals) or the Portfolio view (severity × likelihood, bubble area = FAIR mean loss, hollow ring = no analysis); every code opens the risk’s fact sheet.

Feeds into

Objectives (the chain), Dashboard; control links appear in the libraries and the testing register.

Working the screen

New risks go through the wizard: sizing is POINT scores or a FAIR estimate, and codes are assigned by the platform. Scores multiply severity × likelihood; money figures come only from the FAIR engine — a model never invents a number. Accepting a risk above appetite demands a written rationale and an expiry date, and the re-review date feeds the attention bell. Matrix and Portfolio are views over the same register; a hollow ring means never quantified, not zero. Each card now shows the scores, the treatment, the owning seat and the controls already linked, and only the card you open loads the rest — the lifecycle, the FAIR sizing and the owner’s discussion — so the register stays light however many risks it holds; the open card is in the address, so a link lands on it. A risk above appetite carries the Above appetite chip whether it breaches the score limit or the money ceiling — the server decides from the same appetite the acceptance gate reads, against the category’s limit where one exists — and the register lists those risks first, each group in code order; a sort or filter you choose takes over. Hovering a score breach shows the score against its limit. A tested residual that rests on sample results carries the Sample result chip and says how many of the results counted are samples; the coverage screen says whether a score moved for a sample or did not move at all. Changes and deletions follow the same approval level as additions: when the level requires a second person they become a draft for review, and the row stays as it is until the draft is approved. A risk whose loss figure is in a different currency from its appetite limit shows Not compared: currencies differ, never Above appetite, because the two figures cannot be compared. Under the appetite, the loss severity bands set where MEDIUM, HIGH and CRITICAL begin in each currency; people who administer the registers edit them there, and saving judges that currency's risks again. The default currency, listed first, is the risk appetite's currency, or SAR until an appetite is set. A register too large for one page opens on its first page, and Previous and Next below reach the rest; Matrix and Portfolio show the same page, filters and counts apply to it, and risks above appetite come first within it. Right after you save a change of your own that applies at once, an Undo button stays beside it for 30 seconds; it puts back what you changed, unless the entry has changed since or the change can no longer be reversed.

Doing it well

A risk is an event that has not happened yet, its consequence, and the objective it threatens — name all three. Weak: “Cyber attack.” Better: “Ransomware encrypts the Jeddah plant’s production systems, halting output beyond 48 hours and breaching the delivery commitments in the supply contracts.” Risk or issue? If you can put a date on it, it has happened — it belongs in Findings. A register full of issues cannot be scored, because probability is no longer a question. Risk or cause? “Weak passwords” is a cause; the risk is what happens because of it, and the cause is what a control addresses. Score against your appetite, not instinct — accepting above appetite demands a written rationale and an expiry, by design. Where your own risk policy differs from any of this, your policy governs.

Key risk indicators /risk/kris

Track key risk indicators

What you do here

Key risk indicators: manual readings or metrics derived live from platform state (overdue tests, open findings, overdue proposals, expiring exceptions, divergence), with green/amber/red thresholds computed by the platform.

Feeds into

Early-warning signals for the register and the board pack.

Working the screen

MANUAL indicators take readings you enter; DERIVED ones compute live from platform state (overdue tests, open findings, overdue proposals, expiring waivers, divergence) and cannot be edited — change the underlying state instead. You set the thresholds; the platform computes the green/amber/red status.

Run compliance

Run compliance /comply

Open the compliance workspace

What you do here

The Run-compliance workspace: posture per framework, drift and attention list, and the compliance checklist.

Feeds into

Coverage, testing, evidence and audit readiness one tab away.

Coverage /comply/coverage

Run a mapping

What you do here

Map every requirement to controls (FULL / PARTIAL / GAP) and close gaps with approval-gated AI control drafts. A Map view renders the run as framework-grouped tiles coloured by coverage; every tile and code opens the obligation’s fact sheet.

Feeds into

Dashboard coverage, Libraries (approved controls).

Working the screen

The page opens on the Summary: each source’s obligations split into fully, partly and not covered, then how many controls carry an obligation or mitigate a risk and how many risks have a control. A bar or a count opens the link lanes filtered to exactly those items. Table and Map are one click away, the page remembers your choice in this browser, and a coverage filter pressed on the Summary opens the Table it filters. Table is the exportable view; Map shows the same run as tiles — the counts always agree. Any tile or code opens that obligation’s fact sheet. Running a mapping does not change the register: it creates proposals in the Review Queue, and re-running while they sit pending adds nothing — the banner names where the output went. The run continues in the background: you can leave the page and come back, the banner shows it in progress, and its drafts arrive in the Review Queue when it finishes. One run at a time per workspace: a second start while one is running is refused until the first finishes or is cancelled. Cancel run stops a run before its drafts land — whoever started it, or a holding admin, can cancel while the model is still working; the cancel takes effect when the model answers, and nothing it drafted is added. Once the run is saving its drafts, it can no longer be cancelled.

Libraries /comply/controls

Maintain the control library

What you do here

The system of record: browse, add, edit and delete controls, requirements and risks; review AI suggestions; see version history for controls and risks. Controls carry an accountable position — shown with whoever holds it today — and an owning department; filter to “controls I hold”. A leaver is handled in the organisation structure, not here: end the tenure and their controls escalate up the line, or move a position’s items in one action from Set up → Positions. Every row opens a fact sheet: overview, a Relations explorer over the assurance graph, testing state, and history.

Feeds into

Everything: testing, mapping, risk scoring, dashboards.

Working the screen

Adding a control (or requirement, or risk) follows the workspace approval level — at maker-checker it becomes a proposal, and the screen says so. Deleting a control that has a real test result is refused: the audit trail owns that history; a starter control whose results are all sample results can be deleted, and its sample results go with it. Owner fields carry a position and a department; there is no reassign action on this screen — the link under the table opens Positions, where a leaver’s items escalate when the tenure ends or move in one action. Every code opens the fact sheet with relations, testing state and history. Changes and deletions follow the same approval level as additions: when the level requires a second person they become a draft for review, and the row stays as it is until the draft is approved. A quantified risk keeps its currency; if its figures were always in another currency, Correct the label restates the latest analysis in that currency with the same figures, and the earlier ones stay as stored. A register too large for one page opens on its first page, and Previous and Next below reach the rest; filters and counts then apply to the page shown. Right after you save a change of your own that applies at once, an Undo button stays beside it for 30 seconds; it puts back what you changed, unless the entry has changed since or the change can no longer be reversed.

Doing it well

A control statement says who does what, how often, and what evidence it leaves. Weak: “Access is reviewed.” Better: “The IT manager reviews privileged access quarterly against the joiners-and-leavers list and files the signed review.” Control or intention? If nobody could test it from evidence, it is an intention. Write the statement so a tester who has never met you knows what PASS looks like. One control, one point of failure — a statement that bundles three activities fails as a whole when one slips.

Testing /comply/schedule

Schedule and run control tests

What you do here

Test a control at any of the three lines, for design or operating effectiveness; see the three calendars and the combined assurance strip; the wizard sets cadences in bulk. A manual determination lets a named person overrule the AI verdict with a written justification; passing over a failure follows the workspace approval level.

Feeds into

Dashboard, audit readiness, Trust Center, workpapers, findings, tested-residual risk scores.

Working the screen

Pick the line (self-assessment, Internal Control, Internal Audit) and the basis (design or operating effectiveness) — each line keeps its own calendar. The AI test writes its verdict as the control’s result the moment it runs — a FAIL raises a finding automatically. A manual determination by a named person, with a written justification, is how you override it; PASS or FAIL there requires evidence, only INSUFFICIENT stands without. Overruling a FAIL into a PASS follows the workspace approval level, and recording any PASS never closes a finding on its own — closure is a separate action in Findings. A result seeded with the starter pack is marked Sample result wherever it shows. The schedule and due dates count real tests only, so a line whose only result is a sample reads as never tested until you test it; a sample FAIL cannot exist, so no finding ever comes from one. Changes and deletions follow the same approval level as additions: when the level requires a second person they become a draft for review, and the row stays as it is until the draft is approved. Right after you save a change of your own that applies at once, an Undo button stays beside it for 30 seconds; it puts back what you changed, unless the entry has changed since or the change can no longer be reversed.

Doing it well

Choose the line by who is giving the assurance, not by who is free. Self-assessment is the owner saying “it works”; Internal Control verifies it; Internal Audit stands apart from both. The combined strip exists because “owner says PASS, audit never looked” is a real and common state. Design asks “would this control work as described?”; operating effectiveness asks “did it actually run, all period?” — a new control earns design testing first. A finding closes only at its raising line or higher — so raising at Internal Audit means Internal Audit must close it.

Evidence /comply/evidence

Upload the evidence

What you do here

Upload evidence documents (the AI parses them into cited, structured fields) and run evidence requests — ask a named person for evidence by a date, chase overdue ones, link the upload that fulfils each.

Feeds into

Testing, the Ask panel (retrieval), audit readiness.

Working the screen

Upload PDF, PNG or JPG — parsing is automatic, and fields carry page-level citations with confidence. Files are scoped to the ACTIVE entity: an empty list usually means the wrong entity, not missing evidence. Evidence requests chase a named person by a due date (emailed when your workspace email server is set); overdue ones ring the attention bell; link the fulfilling upload to close the request.

Doing it well

Good evidence answers who, what and when on its face. Weak: an undated screenshot of a settings page. Better: the signed quarterly access review naming the reviewer, the quarter, and the exceptions found. Evidence or assertion? An email saying “we reviewed access” asserts; the review itself evidences. If the source carries no date or owner to cite, a tester has nothing to verify — the honest determination is INSUFFICIENT, and a manual determination is where you record it. Keep originals: the platform stores what you upload, and the audit answers from it.

Findings /comply/findings

Work findings to closure

What you do here

The remediation register: severity, root cause, action plan, owner, due date; closure only by a passing retest at the raising line or higher.

Feeds into

Dashboard posture; the audit story auditors ask for first.

Working the screen

A failed test raises its finding automatically and deduplicates; findings you add by hand follow the workspace approval level. Closure is earned, not clicked: it needs a PASS retest at the raising line or higher, dated after the finding — and recording that retest does not close anything by itself; someone marks the finding CLOSED. Severity, owner and due date drive the attention bell. Changes and deletions follow the same approval level as additions: when the level requires a second person they become a draft for review, and the row stays as it is until the draft is approved. Right after you save a change of your own that applies at once, an Undo button stays beside it for 30 seconds; it puts back what you changed, unless the entry has changed since or the change can no longer be reversed.

Doing it well

A finding is a fact about the past with an owner and a deadline. Weak: “Improve access management.” Better: “Q2 privileged-access review not performed for the Jeddah ERP; 14 leaver accounts remained active — revoke by 15 September and evidence the revocation.” Finding or risk? A finding happened; a risk might. Recording risks here buries real remediation among hypotheticals. Closure is a retest, not a promise — plan the action so the retest can pass at the raising line or higher.

Audit readiness /comply/audit

Prepare the audit view

What you do here

One page for external auditors: controls with latest results and inline evidence.

Feeds into

Shared with auditors; read-only.

Working the screen

Read-only by design: controls, latest results and inline evidence on one page for an external auditor. Anything that looks wrong here is fixed in Testing or Evidence — not edited here. A result seeded with the starter pack is marked Sample result here too; an auditor reads it as a sample, never as a test the workspace ran.

Workpapers /comply/workpapers

Generate workpapers

What you do here

Generate a formatted audit workpaper from a control test result and its evidence.

Feeds into

Audit readiness (documentation auditors read).

Working the screen

Pick a control test result; the workpaper is generated from the stored result and its evidence — figures come from the record, never retyped. Generate again after a newer test and the paper reflects it. A workpaper cannot be generated from a sample result seeded with the starter pack — test the control first, then generate it.

Third parties /comply/third-parties

Screen your third parties

What you do here

Register your vendors, customers and counterparties and screen them against sanctions and watchlists; every possible match gets a recorded human decision (true match or false positive, with a reason).

Feeds into

The attention bell (undecided matches) and your AML/KYC evidence trail.

Working the screen

Register a counterparty and Screen it; Re-screen all runs the whole register, and every query is metered. A possible match blocks nothing by itself — it waits for a recorded disposition: true match or false positive, with a reason. Undecided matches ring the attention bell. The register chip shows the latest screening’s verdict. Changes and deletions follow the same approval level as additions: when the level requires a second person they become a draft for review, and the row stays as it is until the draft is approved.

Contracts /comply/contracts

Track contract obligations and end dates

What you do here

See which obligations come from your contracts and when each contract ends.

Feeds into

Reads the contracts uploaded under Sources and the obligations extracted from them; a contract’s obligations count opens them in the controls library.

Working the screen

Upload a contract under Sources and mark it as a contract, with its end date if it has one. Each contract shows its obligations and its end date; one ending within 30 days is marked, and one that has ended says so. Counterparties are not linked to contracts yet.

Regulatory watch /comply/watch

Watch your regulators for change

What you do here

Watch the regulators that bind your entities for change. The platform compares each regulator’s page with its last snapshot; when the text changes, the AI describes the change — instrument, clause, kind — and a person records whether it matters. Drafts for new or amended obligations go to the review queue.

Feeds into

The review queue (draft requirements from detected changes), the attention bell (changes awaiting triage, sources that could not be checked) and the requirements each change touches.

Working the screen

A holding admin switches the watch on, which seeds a source for every regulator the Regulation Finder shows your entities, and adds the workspace’s own AI key under Settings — the watch runs on nothing else, and without a key it is skipped every night and says so. Check now fetches the due sources; the first check of a source records a baseline and raises nothing. A detected change lists its instrument and clause, the requirements it touches, and any draft sent to the review queue; an approver records the triage — material, immaterial or unclear — with a note. Record a change by hand for a circular you heard about first. A source the platform cannot read (a blocked crawler, a moved page) shows as failing until you correct or retire it. Proprietary licensed standards are never watched.

Govern

Govern /govern

Open the govern workspace

What you do here

The Govern workspace: objectives, mandated-policy gaps, DoA state and the board register at a glance.

Feeds into

The governance story the board asks about.

Objectives /govern/objectives

Define the objectives risks hang from

What you do here

Define business objectives (COSO categories), nest them under the objectives they serve, and see each one’s full chain: risks → controls → three-line assurance.

Feeds into

Risks link to objectives; the chain is the board-level story.

Working the screen

Objectives sit on the four COSO categories and belong to an entity. An objective can sit under a parent objective in the same entity, one above it or group-wide, to any depth; a loop is refused, and a parent with active objectives under it cannot be archived until they are archived or moved. The chain view walks objective → risks → controls → three-line assurance; a hole in the chain is the message, not a rendering gap. A risk that points at no objective never appears in any chain — link it from the risk side. The Chain tab draws the objective’s risks, their controls and the three assurance lines as one picture; a line never tested says so. A line whose latest verdict is a sample result carries the Sample result chip, and the chain’s verdict says how many of its checked controls rest on samples; the board pack, by contrast, counts no sample at all. Changes and deletions follow the same approval level as additions: when the level requires a second person they become a draft for review, and the row stays as it is until the draft is approved. Right after you save a change of your own that applies at once, an Undo button stays beside it for 30 seconds; it puts back what you changed, unless the entry has changed since or the change can no longer be reversed.

Doing it well

An objective is an outcome the business wants, specific enough that a risk can threaten it. Weak: “Be compliant.” Better: “Maintain the SFDA licence to operate the KSA food plants, uninterrupted, through 2027.” Objective or activity? “Run quarterly access reviews” is a control activity. Objectives state the destination; risks say what could prevent it; controls answer the risks. If a risk points at no objective, either an objective is missing here or the risk is not worth carrying.

Delegation of Authority /govern/doa

Record who may approve what

What you do here

The versioned Delegation of Authority matrix: authority lines with thresholds and approvers; instantiate lines as testable controls.

Feeds into

Controls (via instantiation) and the Three Lines testing flow.

Working the screen

Matrices are versioned and immutable once ACTIVE: edit a DRAFT, activate it (holding admins, optionally citing a board resolution), and the old version stays for point-in-time testing. Lines carry thresholds and approvers; Instantiate turns a line into a testable control through the proposal spine. At maker-checker levels new lines wait in Review — and the matrix must still be DRAFT when they apply. Changes and deletions follow the same approval level as additions: when the level requires a second person they become a draft for review, and the row stays as it is until the draft is approved.

Doing it well

Write authority lines as bands a payments clerk could apply without judgement. Weak: “Large payments need senior approval.” Better: “Payments over SAR 250,000 and up to SAR 1,000,000: CFO approval; above that: CEO plus board notification.” Watch adjacent bands: a gap between them is an approval nobody holds; an overlap is an argument waiting to happen. Thresholds invite splitting — that is why the structuring detector exists. Test against real transactions after every revision.

Authority testing /govern/doa/testing

Test authority at a date

What you do here

Point-in-time authority testing: who held what authority, at what limit, on any past date — reconstructed from the effective-dated versions. Import a transactions CSV and the structuring detector flags payment patterns that stay just under an ACTIVE line’s threshold.

Feeds into

Audit evidence of authority at any date.

Working the screen

Pick any date and the matrix is reconstructed from effective-dated versions — who held what authority, at which limit. Import a transactions CSV and the structuring detector flags payment patterns that stay just under an ACTIVE line’s threshold, with the pattern and window named.

Policy matrix /govern/policies

Close the policy gaps

What you do here

The mandatory policy matrix: what the jurisdiction MANDATES versus recommends, against the policies you hold — gaps first. Attestation campaigns run here too: staff attest they have read a policy, with completion tracked to a due date.

Feeds into

Requirement sources (add the missing policy); the govern checklist.

Working the screen

Gaps first: missing MANDATORY policies, then advisories, then covered. Covering a gap means adding the policy under Requirement sources and tagging its topic — the matrix updates itself. Attestation campaigns snapshot their audience at creation and track completion to the due date. A topic chip above the table shows when the view is filtered to one topic — clear it with ✕.

Board register /govern/board

Keep the board register

What you do here

Board resolutions with a full audit trail and their action items tracked to closure; subsidiary boards roll up to the group view. Generate a board committee pack here — objectives, top risks, appetite breaches, posture, findings, DoA and expiring exceptions, every figure computed by the platform.

Feeds into

The DoA activation ceremony references resolutions; the audit trail.

Working the screen

Resolutions are immutable once recorded; their action items track to closure and overdue ones surface. Subsidiary boards roll up to the group view. Generate committee pack builds the pack from platform-computed figures — objectives, top risks, appetite breaches, posture, findings, DoA and expiring waivers — and stores it like a workpaper. Packs print to PDF from the pack itself, in the reader’s language; the Governance landing shows the latest. A pack counts no sample result in any figure built from results; when the workspace holds any at pack time, the pack says so in one line.

Exceptions & waivers /govern/exceptions

Record waivers with an expiry

What you do here

The exceptions and waivers register: every deviation from policy or control is recorded with a rationale and a mandatory expiry — no open-ended waivers. Lapsed items flip to EXPIRED automatically.

Feeds into

Audit readiness (auditors ask for this list first); the policy matrix and control posture it qualifies.

Working the screen

Every waiver needs a rationale and an expiry — open-ended waivers are refused, and lapsed items flip to EXPIRED on their own. At maker-checker levels a new exception waits in Review, and the expiry is re-checked when it applies. Auditors ask for this register first; write the rationale for that reader. Changes and deletions follow the same approval level as additions: when the level requires a second person they become a draft for review, and the row stays as it is until the draft is approved.

Doing it well

A waiver is a decision to carry a known gap for a stated time — not a quiet way to retire a control. Weak: “Password policy waived.” Better: “Password rotation waived for the legacy plant HMI until its Q1 replacement — compensating: isolated network segment and a quarterly manual review.” Name the compensating measure and the real end date; open-ended waivers are refused and expiry is enforced automatically. A waiver that keeps being renewed is a finding wearing a disguise.

Boards & committees /govern/bodies

Keep the boards and committees

What you do here

Record each entity’s board and its committees, their members with role and class (executive, non-executive, independent, external expert) and dated tenures, and see where the composition breaches the body’s own rule or a recorded mandate — and which required committees are missing.

Feeds into

Resolutions and committee packs on the board register name their body; the attention bell (governance gaps); readiness on Govern home; the assurance graph (members).

Working the screen

One live board per entity; committees sit under it and take a template rule (audit committee: majority independent, independent chair) that the body then owns and edits. Appoint members with a class and, for independent members, a written basis; cease them with a date — March and June memberships are both queryable. Breaches name the rule and its source. Committee mandates say which committees an entity must have: attested library content is published per jurisdiction, and until then you record your own from the articles or charter. A functional line to a parent’s committee satisfies a requirement and is shown as reliance, not a gap.

Internal Controls

Internal Controls /controls

Close the control gaps

What you do here

The Internal Controls convergence: uncovered obligations, unmitigated risks and un-instantiated authority lines in one view, each with an AI "suggest a control" action. Every suggestion becomes a proposal for human approval — nothing writes the library directly.

Feeds into

CONTROL proposals in the Review Queue; on approval, the control library, coverage and the testing register.

Working the screen

Three parents converge here: uncovered obligations, unmitigated risks, and authority lines without a control. Each Suggest action drafts through the proposal spine — an “Awaiting review” chip means a draft is already pending, and asking again adds nothing until it is decided. Approved controls land in the library and the test calendars pick them up. Anyone who can run the AI agents can suggest controls for uncovered obligations and for authority lines; suggesting controls for unmitigated risks needs an admin.

Control library /controls/library

Keep the control register honest

What you do here

Every control this workspace holds, and what each one actually carries: how many obligations it covers and how many risks it mitigates. Both counts read the assurance graph, so a cover that arrived through an approved proposal is included, not just the latest mapping run. This is the control-keeper's view of the catalogue; Run compliance → Controls is the same catalogue seen from the obligation side.

Feeds into

Testing schedules, coverage, risk treatment, and every figure that counts controls.

Working the screen

Start with Carrying nothing. A control attached to no obligation and no risk is either waiting for work that never arrived or duplicating one that did — neither is wrong on its own, because a control can be written before the obligation it will serve, but each one should have a reason you can say out loud. Open a code to see what it is attached to and how it has been tested. The decision to RETIRE a control is not here: it belongs on Coverage, next to the evidence of what would be left uncovered. Changes and deletions follow the same approval level as additions: when the level requires a second person they become a draft for review, and the row stays as it is until the draft is approved. A register too large for one page opens on its first page, and Previous and Next below reach the rest; filters and counts then apply to the page shown.

Coverage /controls/coverage

Judge whether the control set is enough

What you do here

Whether the controls this workspace holds are enough, read from BOTH sides. Obligations by how well their current mappings cover them; risks by whether any control stands against them at all, and whether a control that PASSED a test has actually moved the score. Run compliance → Coverage asks the same question from the obligation side only.

Feeds into

Control suggestions, the testing schedule, and the residual scores on the risk register.

Working the screen

Read the two tables as one question. A GAP obligation and a risk with no control both mean a control is missing, and the workspace home lists exactly those with a suggest action. The row worth pausing on is the amber one: controls ARE linked, but nothing that passed a test has reduced the score — a risk with two failing controls is not mitigated however well it was designed, and that is a testing problem rather than a design one. Retire last, and only from here: the scan groups controls that overlap and names one to keep, a control carrying a SOLE cover is never offered for removal, and the figures above this panel are what tells you whether anything would be left exposed. Two more rows say why a score stands where it does: one where the reduction rests on sample results seeded with the starter pack, and one where controls passed their tests but the reductions recorded on their links leave the score unchanged — review the reductions on the risk’s links. Changes and deletions follow the same approval level as additions: when the level requires a second person they become a draft for review, and the row stays as it is until the draft is approved.

Testing /controls/schedule

Keep every control's assurance current

What you do here

When each control is next due, in three calendars — because the three activities are different work: self-assessment by the people who run the control, testing by internal control, and review by internal audit. A control can be current on one line and overdue on another. Run compliance → Testing is the same register; here the question is whether the control set is being kept alive, rather than whether an obligation is evidenced.

Feeds into

Assurance status, findings, and the tested residual score of every risk a control stands against.

Working the screen

Work the overdue line first, and read WHICH line is overdue rather than only that something is. Self-assessment slipping is a different problem from internal audit slipping: the first belongs to the control’s own owner, the second to your assurance plan. A newly approved control drops straight in with no schedule until you give it one, including a control instantiated from a delegation-of-authority rule. And a control that is tested on time but never moves a risk score is a separate question — Coverage shows that one; this screen tells you whether it is being tested at all. Changes and deletions follow the same approval level as additions: when the level requires a second person they become a draft for review, and the row stays as it is until the draft is approved.

More

Partner view /partner-view

Work the approval inbox

What you do here

The consultant’s landing: proposals awaiting their independent approval and the shared-library vouch queue. Consultants read everything, approve proposals, and never write registers.

Feeds into

The Review Queue; the cross-tenant shared library.

Working the screen

Two queues: proposals in client workspaces awaiting your independent approval (maker-checker counts you as the second person), and shared-library candidates awaiting a vouch. You read everything and write nothing in the registers — they change only through approvals (contributing a risk template or vouching for a library candidate is a library act, not a register write).

Review Queue /review

Review and approve proposals

What you do here

The trust layer’s front door: at the maker-checker and two-approver levels, every register item — typed in by a person or drafted by AI, across all nine register types (requirements, controls, mappings, risks, objectives, authority lines, findings, exceptions, and manual test determinations that lift a failure) — waits here; approve (maker-checker — never your own), edit, or reject before anything enters a register. AI drafts carry an independent citation verdict, and a missing or shaky citation is no dead end: pick the source document and locator in the drawer and run the citation check on demand. An optional AI reviewer gives an advisory second opinion — citation form, sector language and length, conflicts with your other regulations — and never gates the decision.

Feeds into

All nine registers — apart from a manual determination, every row an applied draft creates permanently carries its origin (AI-approved or human) and a proposal link.

Working the screen

Filter to Pending to see what needs you. At maker-checker levels and above, you cannot approve your own draft — the database refuses it, and the button says so (a workspace on the lowest approval level lets one person add directly). Verified citations approve straight through; Partially supported and Unverifiable need a written reason and escalate to two approvers; Not supported, Source not found and Locator mismatch cannot be approved at all — fix the citation first with Pick source in the drawer. Approving does not write the register: Apply does, and bulk approve applies each item and names any that fail. Rejecting a draft an AI model wrote also takes one reason from a short list, as well as the note. A proposal marked Changes requested can come back: Send back to review returns it to In review, so it can be decided again. Each draft says whether it is new, a change or a deletion, and the queue filters by that; a change shows the live value beside the proposed one, and a deletion lists what goes with it.

Assurance Map /graph

Read the assurance map

What you do here

The whole workspace as one picture: objectives on the left, the risks that threaten them, the controls that mitigate, the obligations mapped to those controls, and the evidence supporting them on the right. Click any node to read its relationships as sentences, filter by relationship type, or use the table and CSV export beside the map — the same graph the AI agents read when they answer. Amber chips above the map count register items with no named owner — the accountability gaps.

Feeds into

Read-only over every register; Rebuild projection re-derives the links from your registers and never touches a relationship an agent or a person asserted.

Working the screen

The page opens on the Lanes: sources, obligations, controls and risks left to right, each lane with its count. Click a card to light its whole chain, and Focus lineage only hides the rest; a partly covered link is dashed and an obligation with no control is drawn hollow, never hidden. Trace its neighbours opens one item with what it comes from on the left and what it protects on the right, with its owner, latest test and open requests; Back walks the trail. The Assurance map is one click away, and the page remembers your choice in this browser. Chips filter by relationship without refetching — the layout holds still and non-matching links dim. Click a node to read its edges as sentences; Replay scrubs the picture through real recorded times, and the layout never moves during a scrub. Rebuild projection re-derives links from the registers and never touches a relationship a person or an agent asserted. Amber chips count register rows with no named owner.

Audit Trail /audit-trail

Trace who changed what

What you do here

Who changed what and when, across every screen; admins and auditors only.

Feeds into

Compliance record; version history per record opens from the libraries.

Working the screen

Filter by object type and by date range — “to” includes its whole day — and page through the result; every row names the actor, the object and the time. The count is the number of events that MATCH, not the number on screen. Export gives you the whole filtered set rather than the page you are looking at, and if the set is larger than one file will carry, the file’s first lines say so and tell you to narrow the dates. Nothing here is editable — by anyone, including admins. Per-record history opens from each register’s fact sheet; this screen is the cross-cutting view.

Settings /settings

Configure keys, email, approvals, time zone and the Trust Center address

What you do here

The workspace settings hub: your own AI API keys (encrypted, per user), the workspace email server (admin), the approval level — how many people a new register item needs, from approval-outside-the-system to maker plus two approvers (admin) — and the Usage tab: AI tokens in and out, and the reasoning tokens priced as output, who funded them, estimated cost, and storage (admin). The Time zone tab shows the date this workspace calls today; everyone sees it, and the admin sets it. Trust Center access requests (admin): the address the public page offers to a visitor who wants access.

Feeds into

AI agents run under your active key; tenant emails send from your server; creates in the nine spine registers obey the approval level (imports, third parties, KRIs and board records stay direct). Due dates, expiries and the default date on forms follow the workspace time zone.

Working the screen

My AI Keys holds your personal provider keys (encrypted; only the last four characters ever come back) — your ACTIVE key outranks the workspace picker. Email server is your workspace’s own SMTP: chases and digests send from your domain, and Send test proves it end to end. Approval level (admin) sets how many people a register write needs — one, two (maker-checker) or three; structurally high-risk items escalate above the dial, never below. Time zone (admin) sets the calendar date the whole workspace calls today; times of day do not change, and no date moves until it is changed. Trust Center access requests (admin) is the address visitors to your public Trust Center can write to: set it and the page offers Request access, a mail link to that address; leave it empty and the page shows no request link.

Trust Center trust

Share the public status page

What you do here

A public, sanitised live status page you can share with customers. When the workspace has set an access-requests address in Settings, the page offers Request access — a mail link to that address; otherwise it shows no request link.

Feeds into

Published at /trust/{tenant} — no sign-in required.

Platform

Platform /platform

Operate the platform console

What you do here

Owner-only cross-tenant console: every workspace with its usage, by AI agent, and recent sign-ins; what each AI agent may do and how its work fared; the AI providers this deployment can use, with their prices; plus levers — create a password user, remove a user’s AI keys, choose the AI provider for this deployment or for one workspace (an owner-funded sponsored key among them), or set the system email identity Zemam sends its own mail from. Conversation requests from the marketing site land here too, with a small status ladder. Password owner accounts only.

Feeds into

Read-only over all workspaces; a workspace’s own provider — one chosen for it, or its sponsored key — serves that workspace’s AI whenever a person has no active key of their own.

Working the screen

Every lever is audited. Create password users, remove a user’s AI keys, sponsor a workspace with an owner-funded AI key (its usage reports separately from user-funded), review partner applications, and work the marketing-site conversation requests through their status ladder. Set the system email identity — host, account and From address; the password is stored encrypted and shown only by its last four — and send yourself a test. A saved row overrides this deployment’s server settings, which serve when no row is saved; with neither, nothing is sent. The identity provider’s sign-in email is configured at deploy time, not here. Under AI providers, add a provider — cloud, in-house or a gateway — with its connection style, a secure public endpoint, a key shown only by its last four once saved, and the abilities it declares; a provider in use cannot be disabled, and none is ever deleted. Choose the provider this deployment uses and the one that reads documents, or give one workspace its own from its row in the workspaces list; a row managed by a workspace’s sponsorship is changed there. Prices are added per model, never edited, and usage opens by AI agent. When you add or edit a provider, choose the model for each AI activity; an activity left empty uses the provider's default model. Under AI agents, Show the agents' work lists each agent with what its output can change and whether it uses past decisions; over the period and workspace you choose, its runs, its drafts and how people decided them, with the reason chosen for each rejection, its citation blocks and its tokens by outcome. Counts only, never a workspace's content. Password owner accounts only — social sign-ins are barred by design.

Partners /platform/partners

Accredit partner firms

What you do here

Owner-only: accredit law firms and consultancies, attach their people (as consultants) to workspaces, record referral and engagement links, set the public-library moderation flag, and approve or remove shared-library content.

Feeds into

The consensus library every workspace draws from (Set up → Frameworks → Global library); partner attribution and the marketplace foundation.

Working the screen

Accredit a firm before its vouches count; screening runs on the firm and its people, and accrediting over an incomplete screening demands an audited override reason. Attach partner users, record referred and engaged links, and set the public-library moderation flag — NOT_REQUIRED, REQUIRED (adds a platform approval) or ONLY. Cast a Zemam approval on a shared risk template from its moderation card.

Closing Notes

Every screen in this manual was produced by the same six accounts working through the real product, in the order shown: an account created, a company named and structured, applicable rules switched on, individual rules drafted by AI and reviewed by a person, a board recorded and staffed, and five different colleagues finding five different, correctly limited views of the exact same underlying company record.

Nothing here was staged after the fact. The AI run times, the size of the shared review inbox, the honestly-stated gaps, and the riyal figure on the dashboard are the literal numbers the system produced at the moment each screenshot was taken. Where a step names no AI, that is because none ran — not because it was left out of the description.