NOTQIN — OT Track

Team Access Guide

5 min read

Team Access Guide

One sentence. You read on the portal (browser, magic-link), you write on GitHub (web UI is fine). Two tools, no install required beyond a browser.

Your access — at a glance

YouRead hereWrite hereDaily chat
Elwalidhttps://ai.ahmedbenahmed.comGitHub web UI on digitpme-vault(tool TBC at kick-off)
Imranehttps://gtm.ahmedbenahmed.comGitHub web UI OR Google Doc mirror (your choice)(tool TBC at kick-off)
Oussamahttps://ot.ahmedbenahmed.comGitHub web UI on digitpme-vault + PRs on the code repo(tool TBC at kick-off)
Mouadhttps://ot.ahmedbenahmed.comGitHub web UI on digitpme-vault + PRs on the code repo(tool TBC at kick-off)
AhmedAll four URLs + local Obsidian + gitLocal Obsidian (writes flow to git)All channels

Step 1 — Get into the portal (5 minutes)

  1. Open the URL for your role (table above).
  2. The page redirects to a Cloudflare Access magic-link prompt.
  3. Enter your email (the one Ahmed allow-listed — typically your @gmail.com or @uh1.ac.ma).
  4. Click the link in the email Cloudflare sends. You’re in.
  5. Bookmark the URL. Sessions last ~7 days; you’ll re-auth weekly.

Trouble. If you get “You do not have permission to view this page” — your email isn’t on the Access policy. Tell Ahmed. He fixes in the Cloudflare dashboard in 30 sec.

Step 2 — Find your stuff

Each portal is filtered to your audience. You’ll see:

  • All four of you (everyone): the Operating Thesis, the ISA-95 / MQTT / OT-UNS reference cards, the 7 Stage-1 concept notes (OEE, MTBF, etc.), the CBAM regulatory reference, this guide.
  • Your team-internal docs: Path-to-Pilot, Team Onboarding Pack, your own working files (notes / feedback / spike notes / audits).
  • Your role-specific docs only:
    • AI portal: elwalid-notes, AI Spike Notes — Elwalid, Feedback — Elwalid
    • GTM portal: imrane-notes, Feedback — Imrane, AMICA target list, CBAM Warm-Intro Tracker, GTM playbooks
    • OT portal: oussama-notes, mouad-notes, sector pack audits, field-readiness checklist, feedback forms, Morocco UNS Standard, sector overlays

You will NOT see (intentional, founder-only): finance, advisor targets, brand-conflict history, decision log, lost-deal post-mortems, customer-state truth file.

Ahmed sees all four portals; he’s allow-listed on every policy.

Step 3 — Write your stuff

Three things you’ll write during the 2-week onboarding:

  1. Your <name>-notes.md — reading notes (you create this content)
  2. Your Feedback — <Name> 2026-06.md — the 19-question form (fill the placeholders)
  3. Role-specific deliverables — Elwalid’s spike notes, Imrane’s tracker rows, Oussama/Mouad’s sector-pack audits

Two ways to write back into the vault:

Option A — GitHub web UI (recommended, no install)

  1. Go to https://github.com/<Ahmed-handle>/digitpme-vault (Ahmed shares the link + adds you as collaborator).
  2. Navigate to the file (use the search bar — type the filename).
  3. Click the pencil icon (edit).
  4. Edit in the browser. Markdown preview tab on the right.
  5. Click Commit changes at the bottom. Default: create a branch + PR. Accept.
  6. Ahmed gets notified, reviews, merges. Usually within 24h.

No git knowledge required. GitHub does everything in the browser. If you can edit a Google Doc, you can do this.

Option B — Obsidian + git (for the technical ones)

If you want the full Obsidian experience locally (Oussama, Mouad, Elwalid probably):

git clone https://github.com/<Ahmed-handle>/digitpme-vault.git
cd digitpme-vault
# Open this folder in Obsidian: File → Open vault → this folder

Edit in Obsidian, then:

git checkout -b your-name/notes-week1
git add .
git commit -m "elwalid: week 1 reading notes + 3 spikes"
git push origin your-name/notes-week1
# Open the PR on GitHub

Option C — Google Doc mirror (Imrane fallback if GitHub feels heavy)

Ahmed creates a Google Doc per file you own (notes, feedback, AMICA rows). You edit in Google Docs. Ahmed copies into the vault weekly. Slower but zero-friction — pick this if and only if GitHub web UI is genuinely blocking you.

What stays OUT of git and the portal

  • Customer-facing deliverables (signed SOWs, NDAs, sent proposals, customer call recordings) → Google Drive shared folder (Ahmed creates at kick-off). Never commit a signed contract to git.
  • Real-time chat → Discord / WhatsApp / Slack (pick one at kick-off). Decisions of consequence get re-posted into the vault Decision Log by Ahmed.
  • Secrets (passwords, API keys, customer credentials) → never in git, never in the vault. Use a password manager Ahmed sets up.

When things break

ProblemFix
Magic-link email doesn’t arriveCheck spam. Wait 2 min. If still nothing, ping Ahmed — he can re-trigger.
Portal page says “not found”The file probably exists but isn’t tagged for your audience. Ping Ahmed — usually a 1-line frontmatter fix per Portal Audience Routing 2026.
Portal is showing old contentQuartz rebuild may not have run since Ahmed’s last edit. Ping him to rebuild (deploys take ~3 min).
You can’t find a file you know existsUse the portal’s search (top-right). If still nothing, it’s likely founder-only on purpose. Ask Ahmed if you genuinely need it.
GitHub PR has conflictsDon’t try to resolve in browser. Ping Ahmed in chat.
You wrote 2 hours of notes and lost themIf in GitHub web UI: it auto-drafts. If in Obsidian: it auto-saves. If in Google Docs: it auto-saves. You did not lose them. Refresh first.

Sensitivity reminder

Anything you read on the portal or in the vault is internal to the NOTQIN team. Specifically:

  • Don’t share screenshots outside the team without checking with Ahmed.
  • Don’t paste customer names (YNNA Steel, Sonasid, OCP Safi, named AMICA Tier-2s) into public LinkedIn posts, Twitter, or external Discord/Slack.
  • CBAM Warm-Intro Tracker has named accounts and intro paths — that is the most sensitive operational file in your access. Treat accordingly.

If in doubt: ask first.

See also

Graph View

Backlinks