Login accounts for the portal. Requires an admin role on your own account.
Add a user
Projects
Archiving a project hides it from every picker, switcher and search, and freezes it
read-only — nothing is deleted and every work package, SOP and comment is kept exactly as it is.
Unarchive here to bring it back; the project returns unchanged.
Click “Refresh projects” to load.
Default members on new projects
Everyone flagged here is added automatically to every project created from now on,
with the role chosen here. It does not touch projects that already exist — for those, use
Project access in the user table above. Administrators are listed with nothing
to set: they already reach every project.
Click “Refresh” to load.
Features
Switches that change what the suite offers on every project.
Loading…
Notifications & email
Email notifications for work-package assignments, and self-service password resets. Off by default — turn this on only once SMTP is configured. The SMTP password is read from the SMTP_PASSWORD environment variable and is never stored here.
Loading…
All feedback & comments
Every comment submitted across the suite — who wrote it, what they said, and where they were (page & step) when they commented.
Click refresh to load.
Activity log
Who changed what, and when — across projects, SOPs, work packages, and user accounts. Stored server-side in the shared database.
Click refresh to load.
Usage logs
Engagement recorded by the suite — sessions, step views, and actions. Note: stored locally per browser, so this reflects activity on this machine.
Click refresh to load.
Database snapshot
Click refresh to read row counts from SQL via the API.
End-to-end smoke test
Creates a throwaway project, exercises the issue gate / status / metrics / comments, then deletes it (cascade). Mirrors server/smoketest.py.
Ready.
Demo data
Seed a realistic DEMO project (SOP + a spread of Work Packages) into SQL, or remove all DEMO-/SMOKE- projects.
Ready.
Note: the seeded project appears in the home picker; its SOP/WPs live in SQL but won't render in the Creator/Dashboard until the front end is wired to the API (Phase 2).
