SPH SecureDocs — Firebase

SPH SecureDocs Firebase

Real login, persistent document records, private storage paths, role-based access, secure viewer, and audit logs.

Use Firebase as the real backend for SPH SecureDocs.

This version signs users in with Firebase Authentication, stores metadata in Firestore, keeps files in Cloud Storage, checks access by role and allowed users, and writes persistent audit logs.

🔐 Email/Password Auth
📄 Firestore Records
☁️ Private Storage
🧾 Persistent Logs
Documents
0
Firestore records
Authorized Users
0
Unique user IDs across docs
View Events
0
Persistent audit logs
My Role
Guest
Loaded from users collection
Protected docs
0
📄
Waiting for Firebase data
Allowed users
0
👥
User ID permissions
Logs
0
🧾
Open and page-view events
Auth Status
Off
🛡️
Rules must be published

Firebase Auth

Sign up or sign in with email/password. New users are created as viewer by default.

Not signed in.
After your first signup, make that user an admin once in Firestore: users/{uid}.role = "admin".

Upload secure document

Admins and staff can upload PDFs, store metadata in Firestore, and keep the file in Cloud Storage.

Real access control comes from Firebase Auth plus published Firestore and Storage rules. The UI alone is not security.

Document table

View your secure records, open protected files, and manage content based on your role.

DocumentOwnerStatusAllowed UsersExpiresViewsActions

Current profile

Loaded from Firebase Auth and Firestore.

UID
—
Role
Guest
Email
—
Name
—
Admins and staff can upload documents. Viewers can only open documents where their UID is allowed.

Persistent access logs

Firestore keeps your audit events between sessions.