New to Veil? This page gets you working today.

Before day one — getting access

• Accounts are created by invitation. Your Administrator (or Lead) sends an email invitation — it only works for your organisation’s email domain. No invite? Ask your Administrator.
• Sign in with your Microsoft work account — Veil uses your organisation’s normal single sign-on; there is no separate Veil password.
• First screen: you land on “Home” — your personal dashboard with the “Statutory deadline health” panel (“On track”, “Urgent”, “Overdue”) and your work queue.
• Check who you are: the bar at the top of every page shows your workspace, your visibility (for example Org-wide or Department-scoped), and your role initials at the right. Wrong role or missing cases? That’s a question for your Lead.
• Which Act applies to you? Councils run under LGOIMA; central-government agencies under the OIA. Your Cases page says which — it’s titled “LGOIMA Cases” or “OIA Cases”.

See only your regime on this site

Every page here shows both Acts side by side. If you know yours, choose it — the paired callouts will show only your regime (you can switch back any time).

Who to ask

Tip: print this page — the checklists and the table above print cleanly.

Reviewer

You are the first-pass human check: decide every detection, attach the right withholding ground, and sign the document off for senior review. The golden rule: the AI suggests, you decide — nothing is ever pre-redacted.

Your first hour

• Sign in and read your dashboardOn “Home”, find the “Statutory deadline health” panel — “On track”, “Urgent”, “Overdue” — and your queue below it.
• Open “My Queue”It lists every document awaiting review across the cases you can see — not just ones assigned to you. Check the case’s Documents tab for your assignments.
• Open a “Ready for Review” documentWatch the badge flip to “In Review” the moment you’re in.
• Read one detection card end to endExpand it: the flagged text, its type and confidence, the “AI Explanation”, “Public Interest Consideration”, and “Suggested ground”.
• Make your first two decisions“Redact” one clear-cut personal detail; “Don’t redact — keep visible” something plainly releasable.
• Toggle “Original” / “Redacted”Remember: the preview is visual only — permanent redaction happens at export.
• Find a card flagged [REVIEW REQUIRED]Legal privilege, safety, law enforcement. These always wait for your individual decision — bulk accept skips them.
• Bookmark your quick-reference cardPrint it from the quick reference page.

Your learning path

• Module 00 — Foundation (45–60 min)
• Module 02 — The Reviewer (60–75 min)
• Videos: episodes 1–4 and 8

Deep reference: the review screen · what you can upload · FAQ & troubleshooting

Senior Reviewer

Everything a Reviewer does, plus quality-checking others’ decisions, the harder disclosure calls, and the case-wide bulk tools. You cannot give final sign-off — that separation is deliberate.

Your first hour

• Do the Reviewer first hour firstYour tier builds on first-pass review.
• Audit one “Reviewed (Initial)” documentCheck each decision against its ground using “Reasoning” and “Change History”.
• Send something back“Request Changes” → “Send Back” with a short reason — it returns to “In Review” and the reviewer’s queue.
• Open the “Bulk review” pageRead its three steps. Step 1 auto-accepts by confidence, step 2 clears structured PII, step 3 is “Review by reach”. [REVIEW REQUIRED] types are excluded from every sweep.
• Know your two wallsNo “Final Approval”, no “Ombudsman Package” — those belong to the Final Approver and Lead.
• Find “Custom Rules”You co-own agency detection rules with the Lead: keywords, patterns and entities mapped to grounds.

Your learning path

• Module 00 — Foundation
• Module 02 — The Reviewer
• Module 03 — The Senior Reviewer (30–40 min)
• Videos: episodes 1–5, 7, 8

Deep reference: bulk review · version snapshots · custom rules

Final Approver

You give the final, freezing sign-off on documents and the case-level attestation — the last human gates before redactions are burned in and a package leaves the building.

Your first hour

• Find your approval queueIt’s on “Home” — “Approval queue — by deadline risk”. (The rail item “Approvals” opens the shared active-review queue.)
• Approve one training document“Final Approval” → “Confirm Approval”. The document becomes “Signed Off” and its detections are frozen.
• Understand the freezeAfter sign-off nothing on the document can change — problems must be sent back before this point.
• Know the independence ruleYou can’t sign off a document whose detections you reviewed yourself — Veil blocks self-approval.
• Walk the attestationOn “Finalise & Close”: choose the “Disclosure outcome” (“Granted in full” / “Granted in part” / “Refused”) and press “Attest case complete”.
• Memorise the fail-closed ruleA Requester or Ombudsman package is blocked if verification finds a leak or cannot run. “Couldn’t verify” is not “clean” — never bypass a block.

Your learning path

• Module 00 — Foundation
• Module 02 — The Reviewer
• Module 04 — The Final Approver (30–40 min)
• Videos: episodes 1–6, 8

Deep reference: sign-off & attestation · export & verification · when an export is blocked

Lead (request manager)

You own requests end to end — create cases, assign work, manage deadlines, release and close — and you can do everything the reviewing roles can. You’re also the person your team will ask first.

Your first hour

• Create a training case“New Case” → “Log a new request”. Veil assigns the “Reference” and “Statutory deadline” automatically.
• Upload sample documentsOn “Document Ingestion”, drag in test files — never real case material while learning.
• Configure the workflow“Review Workflow Setup”: drag people onto “Collect”, the review stages, and “Final Sign-off”; press “Save Workflow”.
• Assign documentsDocuments tab → tick rows → “Assign Reviewer”. Remember: an assigned document can only be actioned by its assignee.
• Find “Extend deadline”It lives on the case’s Details page, with the reason written to the audit trail.
• Plan your team’s rolloutHave your Administrator invite the team; decide roles and visibility; sequence the training (Foundation first, everyone).
• Read the current limitationsOne page: what’s not in the current release — brief your team so nobody is surprised.
• Skim the facilitator kitRunning the hands-on modules for your team? The trainer kit lists what to stage first.

Your learning path

• Module 00 — Foundation
• Module 01 — The Lead (90 min)
• Module 02 — The Reviewer (recommended)
• Videos: all eight episodes

Deep reference: creating requests · workflow setup · export & release

Administrator

You configure and run the system — and by design you can see nothing of case content. Your day-one job is making sure everyone else’s day one works.

Your first hour

• Confirm the wallCheck your navigation: no route into cases, “My Queue”, or “Reports”. That’s correct — system and case access stay separate.
• Set the agency nameSettings → organisation identity. External export packages are blocked until it’s set.
• Invite your first usersEmail invitations, restricted to your organisation’s domain. Only an Administrator can grant the Administrator role.
• Check the regimeIt’s shown in Settings but fixed at activation — a change needs redeployment, so flag concerns early.
• Know your servicesWhether OCR, AI detection, and Microsoft 365 are configured — your team will ask, and the answers explain most “why won’t this process” questions.
• Note what isn’t yoursCustom Rules belong to the Lead and Senior Reviewer; case-level blocks go to the Lead or a Final Approver.

Your learning path

• Module 00 — Foundation
• Module 05 — The Administrator (30 min)
• Videos: episodes 1–2

Deep reference: what to tell operational staff · FAQ & troubleshooting