TaskRox Help & User Manual

The Administration area is available to platform-level super users. It is separate from normal organisation settings.

Use it for cross-org oversight, not for day-to-day project administration inside a single tenant.

The main admin navigation includes: - Overview — platform stats, recent signups, recent activity - Organisations — tenant list and rollups - Users — cross-org user management - Projects — cross-org project visibility - AI — provider and usage metrics

The system section includes: - Audit Log — platform-wide action history - Login History — every authentication attempt with success/failure, IP, browser details, and failure reason

Login History is useful for security monitoring, troubleshooting MFA/login problems, and platform forensics.

For deep-drill traces of these tables, including the writer paths, action-key conventions, and forensic queries, see the [Login History and Audit-Log Interpretation](/admin/help/audit-login-history) topic in Superadmin Help.

Operational, route, service, and DB-level traces for high-impact admin areas live in [Superadmin Help](/admin/help). Each topic follows a layered Information Architecture so an operator can land on a single-paragraph summary and reach the exact route handler / service function / table column in two clicks or less.

Phase-1 deep-drill topics:

• [Signup and First-Workspace Provisioning](/admin/help/signup-flow) — every field, validation, and DB write traced from /api/auth/signup through signup().
• [Platform User Creation Paths (Signup vs Invite)](/admin/help/user-creation-paths) — three paths into users, contrasted side-by-side.
• [Workspace Context Resolution (org_id vs active_workspace_id)](/admin/help/workspace-context) — how every request decides which workspace to scope to.
• [Super Admin Access Boundaries and Escalation Surfaces](/admin/help/superadmin-boundaries) — where super_user bypasses RBAC and where it does not.
• [Login History and Audit-Log Interpretation](/admin/help/audit-login-history) — two distinct telemetry trails and how to join them.
• [Workforce Admin User-Link Capability](/admin/help/workforce-user-link) — set/clear workforce_person.user_id to recover /my/training/* access without SQL.

Each topic is structured as L1 Summary → L2 Operations → L3 Technical Trace → Verification → Change Risk so the same page serves both quick operational checks and engineering-grade investigations.