An organization holds members, API keys and a service identity that owns its API-stored assets.
Name
Slug
Status
Members
Active keys
Created
No organizations yet — create the first one (Xinsere itself is a fine start).
Users
Everyone with an account, across all organizations — role, membership and security posture.
Name
Email
Role
Organizations
2FA
No users match.
Super admins
The highest tier — Xinsere staff only. Super admins operate the whole platform: create/suspend organizations, mint API keys, view every import. They do not get to read any customer's files. Grant sparingly. Org (tenant) admins are managed inside each organization.
Name
Email
Added
Members
New users are emailed a one-time link to set their own password.
Name
Email
Role
Added
No members yet.
API keys
Keys are shown once at mint time; only a hash is stored.
Name
Prefix
Scopes
Created
Last used
Status
No API keys yet.
Security
Forensic watermarking — every download or preview by a non-owner embeds an invisible, on-chain-logged mark tracing the copy to its recipient. Recommended on.
Visible image watermark — additionally weaves a faint pixel-domain mark into raster images so a screen grab can be traced. It very slightly perturbs the picture; leave OFF for pre-res / professional imaging where any change is unacceptable. Invisible marking above is unaffected.
Marking-policy matrix — per file-format class, whether previews and downloads get marked. Production masters (raw/uncompressed video, images, audio) default to unmarked — bit-perfect for editorial use. Distribution copies and documents default to marked — traceable. Click a cell to cycle Default → Mark → Don't mark. Only applies while forensic watermarking above is On.
Format class
Preview
Download
Danger zone
Suspend this organization — all its API keys stop working immediately. Members keep their accounts but lose org access.
This organization is suspended. Reactivating restores members and API keys.
Imports
Cloud-to-cloud migrations into Xinsere — encrypted, fragmented across clouds, integrity-verified (3 layers), permissioned on-chain.
Migration runs
No migration runs yet. Runs appear here as the connector imports data.
On-chain permission batches
Each batch anchors up to 1,000 files' share permissions in one flat-gas transaction (Merkle root on Polygon Amoy).
Merkle root
Files
Scope
Status
Tx
Anchored
No permission batches anchored yet.
Audit log
Every data access, recorded against the individual acting identity. Append-only; each day's entries are sealed with a Merkle root anchored on Polygon.
Trace a file
Found a file in the wild? Upload it — embedded forensic marks resolve to who accessed it, when, and the on-chain seal.
When
Actor
Type
Action
Organization
File
Bytes
Seal
No matching entries.
Settings
Platform configuration. Values are environment-managed — changing them is a deploy, not a form; this page shows what's live.
General
Identity and runtime basics.
Security
Sign-in enforcement, password policy and abuse ceilings. 2FA enrollment lives in each user's own Settings; admin 2FA enforcement is staged behind a flag.
Email & Domains
Outbound security and invitation email. Delivery is best-effort by design (a send failure never blocks the action that triggered it), which means a misconfigured sender looks identical to a delivered message from the outside — use the test below to check for real.
Storage & Blockchain
Where permissions are anchored. Fragment storage spans multiple clouds by design.