In-app, not a portal

Embed file upload in your app

Your users already have an account. Put the upload checklist on a page they already use — onboarding, a vendor profile, a compliance tab — instead of sending them to another product to log in again.

Portal vs embed

Standalone document portals chase files in a separate login. That is fine for a back-office team with a spreadsheet. It is the wrong shape when documents are part of a product you already ship.

• Your auth, navigation, and branding stay in place
• Holectus never emails or texts the end user
• Storage, status, review, and expiry sit behind the embed and the API

Same identity you already have

Map the signed-in user (or vendor, contractor, applicant) to a Holectus subjectId. Mount the subject checklist on their page and, if your team reviews files, mount<DocumentManager /> behind your own admin RBAC.

import { DocumentChecklist } from '@holectus/react';

// app/vendors/[id]/documents/page.tsx
export default function VendorDocuments({ vendorId }) {
  return (
    <DocumentChecklist
      tokenEndpoint={`/api/holectus/session?s=${vendorId}`}
    />
  );
}

Then gate on valid

Upload is the start. Before you activate an account or pay a vendor, callassert_valid so you know the required files are currently good — not just sitting in a bucket.

How to wire it