Doctech/Super Admin/Project Roadmap
Project tracking · preview

Super Admin · Governance

Project roadmap & delivery status

A single place to see what has been completed, what is in progress and what remains before Doctech is production-ready.

← Control CentreStatus document
Important distinctionCompleted means the static preview or planning document exists and passed local checks. It does not mean authentication, backend security or live printer monitoring is operational.
Completed milestones1Foundation & navigation
In progress2Dashboard design and governance
Remaining milestones4Architecture through production

Delivery milestones

v0.11.0 status
✓COMPLETED

1. Static foundation & navigation

Individual HTML pages, shared assets, dashboard directory and role-specific navigation previews.

  • Folder structure standardised under assets/, app/, auth/ and docs/
  • Internal page and asset references checked in this ZIP
  • Versioned replaceable ZIP delivery established
IN PROGRESS

2. Dashboard design & user experience

Continue improving each role's pages and workflows while keeping empty states honest and text readable.

  • Super Admin command-centre direction established
  • Role-specific menus and page workspaces created
  • Remaining: review every page at desktop/mobile sizes and refine each workflow
IN PROGRESS

3. Role policy & governance

Document who can view, manage, administer or override each capability and within which scope.

  • Draft permission matrix and security boundary principles completed
  • Remaining: decide disputed permissions and approve final role/resource scopes
Review Roles & Permissions →
4REMAINING

4. Product architecture & backend plan

Define tenant hierarchy, data ownership, authentication, APIs, feature entitlements and agent communication before implementation.

  • Data model and tenant boundaries
  • Authentication/session/recovery plan
  • Feature entitlement and rollout design
5REMAINING

5. Secure backend implementation

Implement and test real identity, permissions, saved settings and tenant isolation.

  • Server-side role and resource checks
  • Persistent feature flags, emergency pause and audit events
  • Automated negative tests for cross-tenant access
6REMAINING

6. Windows Agent & print management

Connect real printer inventory and print activity through a secured agent/integration rather than pretending browser JavaScript can access Windows queues.

  • Agent enrolment and health heartbeat
  • Printer/queue discovery and job event capture
  • Reporting, quotas, secure release and cost allocation
7REMAINING

7. Security, QA & production readiness

Validate the complete system before real customer use.

  • End-to-end and role/tenant security tests
  • Monitoring, backup/restore and incident process
  • Privacy review, deployment and rollback runbook

Current next actions

Before backend build
01Review role permissionsConfirm the outstanding policy choices on the matrix page.Open →
02Review remaining dashboard pagesCheck links, layout and mobile presentation on the testing subdomain.Open directory →
03Freeze architectureAfter policy decisions, prepare the tenant/data model and backend implementation plan.Read roadmap →