EDITORIAL OPERATIONS · PRIVATE
Good work begins
with attention.
A LIVE VIEW OF GREYVEIL
At a glance.
A HUMAN RESPONSE, NEVER AN AUTOMATION
Read what needs
a human reply.
Private reader submissions stay in the protected inbox. Only assigned staff can open a conversation; publication always requires separate reader consent and editorial approval.
EXISTING SYSTEMS · NO DUPLICATE DATA
Books, catalogue & publishing ↗Orders & payment status ↗Invoices & finance records ↗Reader feedback ↗Customer account access ↗PRIVATE READER MESSAGES
Human Inbox.
The private inbox has not been loaded.
Select a submission to review its private conversation.
ACCOUNT DIRECTORY
Readers.
| Reader | Account role | Joined |
|---|
EXPLICIT ACCESS · OWNER CONTROLLED
Team & access.
Owner identity is provisioned separately after Lalit’s account is verified. Staff roles cannot be promoted to Owner. Only the Owner can assign or revoke staff access. MFA is required for every privileged query and change.
The invited person sets their own password through Supabase Auth, then enrolls MFA before opening command-centre data. Invitation links are single-use.
| Staff member | Role | Status | Assigned | Action |
|---|
REPORTS & READER FEEDBACK
Careful review.
Reports are loaded only for roles with moderation permission.
EXISTING FEEDBACK WORKFLOW
Reader feedback remains managed in the existing authenticated admin tool.
Open Feedback management ↗SENSITIVE ADMIN ACTIONS
Security & audit.
Audit entries are append-only and generated by database operations. Supabase authentication login history and provider health metrics are not exposed by this database integration and are not represented here.
| When | Actor | Action | Target | Details |
|---|