Enterprise Documentation

Enterprise Guide

Deployment, operation, and end-user documentation for AIAuth Enterprise (self-hosted).

AIAuth Enterprise — Admin Guide

This guide is for the IT / Compliance admin deploying AIAuth Enterprise on behalf of their organization. End-user documentation is in the companion Enterprise User Guide.

AIAuth Enterprise is self-hosted only. You run the server on your infrastructure. Finch Business Services LLC (the software vendor) has no access to your data.

1. Getting Started

1.1 What AIAuth Does for Your Organization

Chain of custody, not content surveillance. Your users press Ctrl+Shift+A to create a tamper-proof receipt of their AI-assisted work. The receipt carries metadata (who, when, which AI tool, review status) — never the content itself. Your dashboards answer "Who is using which AI tools? Are they reviewing output? Is content flowing externally?" without the privacy cost of screen recording or content capture.

What you can see: per-user attestation rates, AI-tool adoption, review quality (time-to-attest, rubber-stamp detection), external-content-flow rates, policy violations, cross-format chain integrity.

What you cannot see, by design: the actual text of AI prompts, the content of attested documents, browsing history outside AI sites, screenshots, keystrokes.

1.2 Activating Your Enterprise Account

  1. Email sales@aiauth.app with your company name, estimated user count, and domain(s) you'll deploy to.
  2. You receive an invoice and, once paid, a signed license key (a single long string).
  3. Paste the license key into config.yaml on your server.

No ongoing phone-home. The license validates offline against our public key at server startup.

1.3 Your First 30 Minutes (Self-Hosted Quickstart)

Option A — Docker (recommended for production):

git clone https://github.com/chasehfinch-cpu/AIAuth.git
cd AIAuth/self-hosted
cp config.yaml.example config.yaml
# Edit config.yaml: paste license_key, set organization.name, domains, server_url
docker compose up -d

Option B — Python venv (for non-Docker environments):

cd AIAuth/self-hosted
./install.sh /path/to/config.yaml
# Creates venv, installs deps, writes systemd unit + nginx vhost, starts service.

After either path: - Your server is running at the URL you set in config.yaml. - Keys have been generated in /var/lib/aiauth/keys/ (or whatever storage.key_dir points at). - The anonymous hash registry and enterprise_attestations database are initialized. - Your organization is registered from organization.name + organization.domains. - You are the first admin.

Verify: curl $SERVER_URL/health should return {"status":"ok","version":"0.5.1",...}.

2. Deploying to Your Organization

2.1 Chrome Extension Deployment

Individual pilot (1-10 users): ask each user to install from the Chrome Web Store and enter $SERVER_URL in their Settings panel.

Full rollout (Workspace-managed): 1. In Google Workspace Admin Console → Apps → Chrome → Apps & Extensions, add the AIAuth extension by ID. 2. Set Installation Policy to Force install for the target OU. 3. Set the Managed configuration JSON: json { "enterprise_server": "https://aiauth.yourco.com", "org_domain": "yourco.com", "tier": "enterprise", "require_verification": true } When users open the popup, the Server URL is pre-filled, tier is pre-selected as enterprise, and the "Start Attesting (unverified)" button is hidden — they must verify their corporate email.

2.2 Desktop Agent Deployment

Windows (v0.5.2+ with MSIX): GPO / Intune / Winget push. Silent-install flags /S /SERVER=https://aiauth.yourco.com /LICENSE=<key>.

macOS (roadmap v0.6.0): Jamf / Munki; config delivered via ~/Library/Preferences/aiauth.plist.

Before an org-wide rollout, deploy to one department (Finance, Legal, or Engineering are good candidates) for 30 days. On day 30, the pilot report generator produces a branded HTML/PDF summary:

python scripts/render_pilot_report.py \
  --server https://aiauth.yourco.com \
  --session $ADMIN_SESSION \
  --org-id $ORG_ID \
  --admin-email you@yourco.com \
  --department Finance \
  --from 2026-04-01 --to 2026-04-30 \
  --out pilot-report-finance.html --pdf

Email the report to leadership; it's the strongest case for the full rollout.

3. Managing Users

3.1 Inviting Users

Current state (v0.5.1): users self-invite by setting the Server URL to your deployment and clicking Verify My Email with their corporate email address. Because their email domain matches one of your claimed domains, they become members of your organization automatically.

Bulk invite via CSV / LDAP / Azure AD sync is on the v0.6.0 roadmap.

3.2 User Account Linking

If an employee already has an AIAuth account with a personal email, they can link their corporate email to the same account. This enables: - Attestation history carries over when they change employers. - Consent-gated: personal attestations become visible to your org dashboard only if the user opts in via /v1/account/consent.

3.3 Offboarding an Employee

When an employee leaves, run:

curl -X POST $SERVER_URL/v1/admin/pseudonymize \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $ADMIN_SESSION" \
  -d '{"email": "departed@yourco.com", "org_id": "ORG_abc"}'

This: 1. Replaces uid_encrypted with NULL on all their attestation rows. 2. Sets uid_pseudonym to a one-way hash (audit records still identifiable cross-rows within the org). 3. Marks their org_members.left_at. 4. Their uid_hash remains so subsequent ingest attempts from that email return EMAIL_OFFBOARDED.

3.4 Department Mapping

Upload a CSV mapping email → department:

email,department
alice@yourco.com,Finance
bob@yourco.com,Engineering

(Current state: department mapping via CSV import is operator-run via the admin endpoints; a UI is v0.6.0. Unmapped users appear under "Unmapped" in the dashboard.)

4. Reading the Dashboard

Your dashboard lives at https://aiauth.yourco.com/v1/admin/dashboard (admin session required). Also accessible at https://aiauth.yourco.com/demo with a managed session token.

4.1 Dashboard Overview

Top KPIs: Total Attestations, Unique Users, Review Rate, Rubber-Stamp Alerts, External Exposures, Shadow AI Alerts, AI-Authored Artifacts, Prompt-Chain Coverage.

4.2 AI Usage Heatmap

Departments × AI tools. Cell intensity = attestation count. Look for: - Cells where an unapproved AI tool dominates. - Rows where a single tool is concentrated (possible tool lock-in).

4.3 Shadow AI Heatmap

concurrent_ai_apps reveals which AI apps your users have OPEN at attestation time — even the ones they're not using for this specific attestation. A high ratio of "times open" to "times attested from" flags ungoverned AI tool usage.

4.4 Review Rate Scorecard

Letter grades per department: - A: ≥95% reviewed, 0 critical violations. - B: ≥85%. - C: ≥70%. - D: ≥50%. - F: <50%.

A low grade means someone is attesting without reviewing. This is usually a process problem, not a people problem — consider enforcing a mandatory-review-delay policy.

4.5 Time-to-Attest Distribution

Histogram of tta (seconds between AI output and attestation). The 0-10s bucket is flagged red — under 10 seconds on >500 characters of content almost always means the user didn't read it (rubber-stamping).

4.6 Chain Integrity Monitor

Shows broken chains: documents whose parent receipt can't be found. Common causes: - Document was attested by someone outside your org (intentional boundary). - Pre-AIAuth history (OK to leave). - Receipt was deleted via DSAR (noted in consent_log).

4.7 Policy Violations

The built-in policy engine evaluates each attestation against: - dual-review-financial (high) — financial content attested by only one person. - no-rubber-stamping (medium) — tta<10 AND len>500. - external-must-attest (critical) — content flowing externally without review. - unverified-financial (medium) — financial content from an unverified extension. - shadow-ai-detected (low) — AI app open but not used for this attestation. - ungoverned-ai-content (medium) — AI-authored file with no parent chain.

4.8 External Exposure Report

Attestations where dest_ext=true. By destination (email, messaging, code-repo), by classification.

4.9 AI Authorship Detection

Counts of receipts where ai_markers.verified=true (Copilot docProps, ChatGPT/Claude/Gemini PDF markers, C2PA image manifests). Identifies AI-authored content even when no one attested it through AIAuth — useful for catching shadow usage.

5. Running Reports

5.1 Pilot Report (30-day)

See scripts/render_pilot_report.py in the repo. Produces a standalone HTML with your org's logo, prospect sign-off block, observations, and recommendations.

5.2 Compliance Report (Quarterly)

https://aiauth.yourco.com/samples/compliance-report?source=live&org_id=$ORG&session=$TOK serves a print-friendly 8-section audit report.

5.3 Custom Exports

GET /v1/admin/dashboard/data?org_id=$ORG&from=$D1&to=$D2 returns the full data contract as JSON. Pipe into your own BI pipeline.

6. Data, Privacy, Compliance

6.1 What AIAuth Stores

  • Anonymous hash registry (6 columns) — no PII.
  • accounts + account_emails — emails stored as HMAC hashes. Only the hashes; never plaintext.
  • enterprise_attestations — full receipt metadata. uid stored as HMAC hash + AES-GCM encrypted ciphertext. Decryptable only by authenticated admins on demand.
  • consent_log — append-only audit trail. Details stored as AES-GCM ciphertext.

6.2 Data Hardening

If your server is compromised, a filesystem attacker gets: - Email hashes (irreversible without SERVER_SECRET) - Fernet ciphertext (decryptable only with SERVER_SECRET) - The anonymous registry (PII-free)

Residual risks: - The signing keys are plaintext PEM on disk. Keep backups offline; rotate annually. - SERVER_SECRET in .env is plaintext. chmod 600, not in any off-server backup.

6.3 GDPR + DSAR Handling

POST /v1/admin/dsar supports: - export — return all data tied to an email (decrypts ciphertext in-response). - pseudonymize — replaces uid_encrypted with NULL, keeps audit record with uid_pseudonym. - delete — hard delete of all attestations (nuclear; chain integrity affected).

Pseudonymize is the recommended default for offboarding; delete is for explicit DSAR requests.

6.4 Self-Hosted Data Sovereignty

Your server, your jurisdiction, your control. Finch Business Services LLC has no access. The one outbound call — license validation — happens once at startup via HMAC verification against our public key; no personal data is transmitted.

2.5 Operations: Backup and Recovery

2.5.1 Non-optional: keys backup

Run backup.sh --install-cron daily during initial setup. Archives land in /var/backups/aiauth/ by default.

./self-hosted/scripts/backup.sh --encrypt age:$PUBKEY --to s3://yourco-backups/aiauth/ --retain 30d

Encrypt with age (or GPG), push to off-server storage (S3, SFTP). Keep the age private key in a password manager or HSM — never on the AIAuth server itself.

2.5.2 Restore

systemctl stop aiauth
./self-hosted/scripts/restore.sh /path/to/backup.tar.gz.age --decrypt age
systemctl start aiauth

2.5.3 Key Rotation

Annually:

# 1. Generate new key in keys/key_002_active.pem
# 2. Update key_manifest.json:
#    - set key_002 status=active, current_signing_key=key_002
#    - set key_001 status=retired, valid_until=<today>
# 3. Restart service
# Both keys remain loaded; new receipts sign with key_002, old receipts verify with key_001.

2.5.4 SERVER_SECRET Rotation

If SERVER_SECRET leaks:

systemctl stop aiauth
NEW=$(python -c "import secrets; print(secrets.token_hex(32))")
# In config.yaml, move current server_secret -> server_secret_previous,
# set server_secret to $NEW.
systemctl start aiauth
# Server runs in DUAL-SECRET mode — old tokens and hashes still validate.
# All active users will be asked to re-authenticate on next /me call.
python ./self-hosted/scripts/rotate_server_secret.py --re-encrypt
# Wait 7 days for users to re-auth naturally. Then:
# Remove server_secret_previous from config.yaml; restart.
python ./self-hosted/scripts/rotate_server_secret.py --prune-orphaned

2.5.5 Disaster Recovery Playbook

Scenario Recovery
Signing keys lost, backup intact ./restore.sh --keys-only + restart
Signing keys lost, NO backup Issue new license with fresh keys; historical receipts become unverifiable (document this in compliance record).
SERVER_SECRET lost, ciphertext unreadable Follow 2.5.4 rotation flow (email hashes and tokens orphan gracefully).
aiauth.db corruption ./restore.sh --db-only + any missed ingests replay from client queue.
Full server loss New box → docker compose up with old config.yaml → ./restore.sh full archive. ~30 min downtime.

7. What AIAuth Provides Post-Handoff

After your initial deployment, AIAuth's involvement is minimal:

  • Software updates: GitHub Releases. You choose when to git pull + redeploy.
  • License renewals: annual. We email a new key 30 days before expiry. Expired licenses enter a 30-day grace period before losing enterprise features; attestation signing always continues.
  • Bug reports: GitHub Issues.
  • Optional paid support: direct Slack + SLA, pricing on request.

What AIAuth does not provide post-handoff: - Access to your attestation data (we don't have it). - Account recovery (you manage your own signing keys). - Real-time monitoring (that's your ops team's responsibility).

AIAuth Enterprise — User Guide

This guide is for employees whose company has deployed AIAuth Enterprise. Short version: almost nothing changes about how you work. Keep reading for the details.

1. What's Changing for You

Your company now uses AIAuth to create a chain of custody for AI-assisted work. When you use ChatGPT, Claude, Copilot, or any other AI tool to help produce work output, you press Ctrl+Shift+A to create a tamper-proof receipt proving:

  • What AI was used
  • When it was used
  • That you reviewed the output before using it

That's it. Your workflow doesn't change beyond one keystroke.

What your employer can see through AIAuth: - Which AI tools you use for work (ChatGPT, Claude, Copilot, etc.) - How long you spend reviewing AI output before attesting (time-to-attest) - Whether you approved, modified, or rejected the output - The metadata category of what you produced (spreadsheet, code, document, etc.) - Whether the content appears to flow to external destinations

What your employer cannot see, by design: - The actual text of your AI prompts - The actual content of what you write - Your browsing history outside of AI sites - Screenshots, keystrokes, or any content capture - Prompts and content you haven't attested

AIAuth is a chain-of-custody tool, not a surveillance tool. Your employer sees metadata about the shape of your AI-assisted work; they do not see the substance.

2. Getting Set Up

2.1 If the Chrome Extension Was Pre-Installed

Look for the AIAuth icon in your browser toolbar (a small blue "A"). Click it: 1. The Server URL should be pre-filled with your company's AIAuth server (e.g., aiauth.yourco.com). 2. Enter your corporate email address (e.g., you@yourco.com). 3. Click Verify My Email (Recommended). 4. Open your corporate inbox — there's a one-time link waiting. Click it (or copy-paste it into the extension's verification box). 5. You're ready. Press Ctrl+Shift+A on any AI site to attest.

2.2 If You Need to Install It Yourself

Your IT department will point you at the Chrome Web Store listing. Install the extension, then follow 2.1 above.

2.3 If You Already Had a Personal AIAuth Account

You can link your corporate email to your existing account so your attestation history carries over: 1. Log into your personal AIAuth account in the extension. 2. Go to Settings → Link Additional Email. 3. Enter your corporate email. 4. Verify via the one-time link.

Your prior personal attestations remain private by default. You can optionally opt in to share them with your employer's dashboard via Settings → Consent. Your employer sees only what you explicitly consent to.

3. Daily Workflow

3.1 Attesting AI-Assisted Work

After you've reviewed AI output and decided it's ready to use:

  1. Select the output text on the AI site.
  2. Press Ctrl+Shift+A (or Cmd+Shift+A on Mac).
  3. A receipt is created. You'll see a toast notification with a short code like [AIAuth:a1b2c3d4].
  4. That code is copied to your clipboard. Paste it wherever you want proof of provenance — alongside the content in an email, in a Slack message, in a document comment, etc.

3.2 Reviewing Before You Attest

The extension records how long you spent looking at the AI output before pressing Ctrl+Shift+A. This is the "time-to-attest" metric. Under 10 seconds on long content triggers a "rubber-stamp" alert.

If you're genuinely skimming something short, no alert fires. The threshold is calibrated for "long content reviewed too quickly to have actually been read."

3.3 File Attestation

Right-click any file → AIAuth: Attest this file. The agent hashes the file locally, reads AI-authorship markers, and creates a receipt. The file is never uploaded anywhere.

3.4 When You're Offline

Press Ctrl+Shift+A anyway. The receipt is created locally with a "Pending" badge. When you're back online, the extension syncs pending receipts automatically.

4. Your Receipts

4.1 Where They're Stored

  • On your device: always. Open the popup to see your recent receipts.
  • On your company's AIAuth server: for corporate attestations (once your corporate email is verified and linked to the org). Your employer's dashboard shows these.
  • On your personal AIAuth account: for attestations made with your personal email. Your employer does NOT see these unless you opt in.

4.2 Verifying a Receipt

Anyone with the short code or the full receipt JSON can verify it at aiauth.yourco.com/check (or aiauth.app/check for personal-tier receipts). Verification is cryptographic — no account required.

4.3 Sharing a Receipt

In the extension popup, click Share next to a receipt. The full signed JSON is copied to your clipboard. Paste it anywhere that needs proof of chain of custody.

5. Leaving the Company

When you leave:

  • Your personal attestation history stays with you. Your personal AIAuth account is unaffected.
  • Your corporate attestations stay with the company. Your name is pseudonymized in the audit record so you're no longer personally identifiable, but the audit-record integrity is preserved.

Your employer cannot retroactively extract your personal attestation data. AIAuth's pseudonymization is one-way.

6. FAQ

Can my employer see what I type into ChatGPT? No. Only a one-way hash of the prompt is recorded, and only when you create an attestation. Your employer sees the hash — not the prompt text. The hash cannot be reversed into the original prompt.

Can my employer see what AI apps I have open on my computer? On the enterprise version, yes — but only AI applications we recognize (ChatGPT Desktop, Claude Desktop, Cursor, Copilot, Perplexity, Poe), only at the exact moment you press Ctrl+Shift+A, and never the contents of those apps. This is called the Shadow AI Heatmap. On the free version, this is never collected.

This is disclosed here because your employer is a consent-required data controller for this data, and consent requires that you know what's captured.

Do I have to use this? Your company's policy determines this. AIAuth is technically optional — if you don't press Ctrl+Shift+A, no receipt is created. But if your company's policy says "all AI-assisted client deliverables must carry an AIAuth receipt," not attesting means your work isn't shippable.

What if I forget to attest? Nothing breaks. Attestation is additive — your work still happens, just without the audit trail. Your manager might ask you to attest retroactively; you can do this by pasting the text into the extension popup's "Attest pasted text" box.

Can I use AIAuth for personal projects? Yes. Install the extension at home with your personal email. Your personal attestations live on your personal account and never touch your employer's systems.

What if my time-to-attest is flagged as rubber-stamping but I really did read the content? The threshold is <10 seconds on content >500 characters. If you consistently read fast, talk to your manager — the threshold can be tuned per-organization. If you were skimming because you'd already reviewed the content in an earlier attestation, you're not doing anything wrong; the metric captures "how long between the AI producing this and you attesting," not "how long you reviewed it."

What happens if my company's AIAuth server goes down? Attestation works offline. Your extension queues pending receipts and syncs them when the server is back. You'll see a "Pending" badge on unsynced receipts.

Can AIAuth the company (Finch Business Services LLC) see my data? No. Your company runs AIAuth on their own infrastructure. Finch Business Services LLC (the software vendor) has no access to the data — they ship the software, your IT team operates the server.