No scans available yet
Projects appear here once they've been added to your account.
Settings
Where scans are stored
Define each server or share once, then activate the one the site should serve from. SMB shares are mounted by Kubernetes, so the viewer never handles the password itself.
Adding an SMB server the first time: save it below → press Manifest and apply that one YAML on the cluster (it holds no credentials, and it's the only step needing kubectl) → press Connect → once it reads connected, press Use this. Later changes to that same server need only Connect.
Conversions
Scans are converted to the streaming format once, in the background, a few at a time. Anything someone is actively opening jumps the queue.
Health
Recent errors
Workflow stages
The progress tracker shown on every scan page. One per line, in order.
Site
The cap on how many points a converted scan keeps. Applies fully to text formats (.pts / .xyz / .ply), which ship every point to the browser — 25 million is roughly a 375 MB download. .e57 goes through the streaming octree, which preserves every point in the source up to the cap; above what one pod's RAM can hold the converter auto-decimates to fit. The 2 B ceiling is a guardrail against typos, not a technical limit — pick whatever number covers your biggest expected scan. Existing scans keep their current detail until they're re-converted (Settings → Conversions → Retry).
Email (invites & password resets)
SMTP is used for invite emails and password-reset links.
Without it, invites still work — the sign-in URL is returned so you can hand-deliver it.
Env vars (SMTP_HOST or MAIL_360_USER) override these fields.
Performance
How much of the cluster each viewer server may use when converting scans. Raising these speeds up conversion; the servers restart to apply, which takes about a minute. Share links keep working throughout.
Reserved amounts (what the scheduler guarantees) stay small deliberately — raising those is what makes servers unschedulable, which would take the site down rather than just slow it.
People
Invite someone
They sign in with their existing Google or Microsoft work account — no password to manage. If email is configured, they get an invite email; otherwise the account is created and you can hand-deliver the sign-in URL.
Domain rules
Anyone with a verified email at these domains gets access automatically.
Staff account (password + authenticator)
Internal staff — owners and administrators only. Customers should be invited above (they sign in with Google/Microsoft).
Companies
Folder → company
Each top-level folder in the scan directory becomes a company automatically. Reassign one here if the folder name doesn't match the customer.