Internal portal · access by assignment only

Every document your team needs. Nothing they shouldn't see.

A single, access-controlled home for hardware and software knowledge: a library you see only what you were given, a dashboard that tells you what to do next, guided learning paths, a reader that stays out of the way — and a review-first way to add new content.

Access roles
3Access roles
Documents sent to outside AI
0Documents sent to outside AI
Key actions audited
100%Key actions audited
Capabilities

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 knowledge in front of the right person, help them learn it, and show that it was read.

One library, access by assignment

Sections, modules and folders to any depth. A grant on a branch covers everything inside it; people and teams see only what they were given — enforced in the app and again by the database.

A home that knows what's next

The dashboard answers “what should I do now?”: pick up exactly where you stopped (page, section, lesson), then anything waiting on you, then what colleagues shared.

Guided learning paths

Ordered lessons and multi-module paths with sequential unlocking, required and optional steps, and a cancellable continue — arranged by drag and drop or keyboard.

A reader that stays out of the way

PDF, HTML and images in one content-first viewer: focus mode and zoom that survive moving between lessons, reading width, outline, bookmarks, shared notes and markup.

Add content, reviewed first

Upload files or write a Markdown lesson. Details are suggested on your own server — nothing is sent anywhere — and nothing is visible until a person saves or publishes it.

Share, discuss, get notified

Send a document or grant access in one step, @mention colleagues, comment, ask a module admin, and choose in-app or email notifications — right away or as a daily summary.

Views, downloads, uploads, shares, permission changes and completions are written to an audit log — never the documents' contents.
How it works

From request to first lesson — and keeping it current

  1. 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. 2

    An admin grants access

    A super admin approves the request and grants sections or teams. The new person gets a welcome email with the portal address — never a password — and everything else stays invisible.

  3. 3

    Pick up, read, complete

    The dashboard opens on what to do next. Lessons unlock in order, progress and notes are saved per person, and module admins see how their readers are doing.

  4. 4

    Admins keep it current

    Drop in files or write Markdown. The portal suggests the details on its own server; an admin checks them, then saves a draft or publishes — and arranges lessons by drag and drop.

Security

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.

  • Files behind a permission check

    Files live in private storage (the server's disk or a private bucket) and are only ever served after a permission check — including the lesson lock of a learning module.

  • Sandboxed HTML

    Uploaded HTML and Markdown lessons render in a sandboxed frame under a strict content-security policy with scripting disabled outright.

  • Nothing leaves the server

    Suggested details come from text analysis built into the portal — no AI service, no API key. Credential-like values are removed before anything is analysed.

  • A person decides

    Uploads are checked from their bytes and stay private until someone saves or publishes them. Suggestions can never publish, grant access or change lesson order.

  • A complete trail

    Sign-ins, views, downloads, uploads, shares, permission changes and completions are recorded with who, what and when — never the content itself.

Already have an account?

Sign in with your LM Machine Visioncredentials. If you don't have access yet, send a request and an administrator will review it.