Every document your team needs. Nothing they shouldn't see.
A single, access-controlled home for hardware and software knowledge — with guided learning paths, a distraction-free reader, and progress tracking that reflects what people actually read.
- Access roles
- 3Access roles
- Permission types
- 6Permission types
- Actions audited
- 100%Actions audited
Built for the way engineering teams actually read
Not a file share with a login screen. Every part of the portal exists to get the right document in front of the right person — and to prove it was read.
Access by assignment
Three roles and six permission types, enforced in the app and again by row-level security in Postgres. People see only the modules they're assigned.
Guided learning paths
Turn any module into an ordered course: sequential gating, required and optional lessons, auto-advance, and a completion policy you choose.
Distraction-free reader
A fullscreen shell that survives lesson-to-lesson navigation — PDFs, images, and HTML in one viewer with zoom, outline, and no layout flashing.
Progress that means something
Pages count only after a stable dwell, and fast scrubbing earns nothing. Jumping to the last page doesn't mark a document complete.
Notes and bookmarks
Per-user annotations and bookmarks that jump straight back to the page or section, plus an outline built from the document itself.
Bulk upload
Drag in files or a whole folder. Edit titles inline, set the target module and status, and watch a per-file queue report success or failure.
From request to first lesson in three steps
- 1
Request access
New joiners submit a request from the sign-in screen — name, work email, the role they need, and why. It grants nothing on its own.
- 2
An admin assigns modules
A super admin approves the request, sets the role, and assigns the modules and permissions that person should have. Everything else stays invisible.
- 3
Read, annotate, complete
They work through documents or ordered lessons in the reader. Progress, bookmarks, and notes are saved per person and visible to module admins.
Least privilege, checked twice
Internal documentation is often the softest target in a company — everything in one folder, shared with everyone, forever. This portal is built the other way around: nothing is visible until someone is explicitly given it, and every check happens in two places.
Enforced in the database
Row-level security policies mean a missing app-side check can't leak a document. The database refuses the read.
Time-limited file access
Files live in private object storage and are served through short-lived presigned URLs, generated only after a permission check.
Sandboxed HTML
Uploaded HTML renders in a sandboxed frame under a strict content-security policy with scripting disabled outright.
A complete trail
Sign-ins, views, downloads, uploads, permission changes, and completions are all recorded with who, what, and when.
Already have an account?
Sign in with your Knowledge Access Portalcredentials. If you don't have access yet, send a request and an administrator will review it.