Superadmin

Platform-wide administration and project bootstrap.

The superadmin shell is the platform control layer. These pages are where organizations, global users, template sets, currencies, audit history, and new projects are managed. Superadmin routes sit under /admin.

Overview Authentication Supervisor Manager Employee

Superadmin Workflow Summary

  1. Use the projects registry to inspect existing projects and start project creation.
  2. Create a project on one long form with metadata, roles, funding, and the initial team.
  3. Create organizations from the organization registry dialog.
  4. Inspect and maintain global users, role templates, and supported currencies.
  5. Use the audit page to review recorded system actions.

Task Recipe

Create A New Organization Root

Run this when a brand-new tenant must be added before any projects or members exist.

  1. Open /admin/organizations.
  2. Use Add new to open the organization dialog.
  3. Enter the organization name and short name.
  4. Set the default currency that should anchor new project defaults for that tenant.
  5. Create the organization, then return to the projects area when the first project needs to be created.

Task Recipe

Create A New Project

This is the most important superadmin workflow because it connects organization selection, template choice, funding setup, and initial team creation in one save path.

  1. Open /admin/projects and choose Create project.
  2. Select the target organization.
  3. Enter the core project metadata including funding mode, start month, and duration.
  4. Choose a saved labor-role template set or define a custom project role set.
  5. Enter the initial funding sources so the effective month starts with a complete configuration.
  6. Add at least one supervisor, plus any optional managers or employees.
  7. Assign the initial labor role for every added member.
  8. Create the project and verify that it appears in the project registry.

Task Recipe

Investigate A Platform Change Through Audit

Use this when someone asks whether a change was recorded or who triggered it.

  1. Open /admin/audit.
  2. Apply the relevant filters to narrow the event list.
  3. Scan the returned rows for the entity or action you care about.
  4. Open the row-level detail action to inspect a single event more closely.
  5. Use the audit record together with the corresponding admin page to explain the change.

Project Registry

The projects registry is the main landing page for project administration. It shows the platform-wide project list and provides the starting point for creating new projects.

Route/admin/projects
Main actionCreate project

What You Can Do Here

  • Filter the project registry before reviewing the list.
  • Inspect the existing project catalog across organizations.
  • Start the full project-creation flow from the dedicated create link.
  • Use the admin sidebar to jump directly to the other superadmin registries.
  • Use the registry as the default place to confirm whether a project already exists before creating another one.
Click the screenshot to open it full screen.

Create Project

Project creation is a single long page rather than a wizard. That matters during onboarding because the entire setup has to be understood as one save operation: organization selection, core metadata, labor-role definition, initial funding, and the initial team all live on one route.

Route/admin/projects/new
Required sectionsProject metadata, labor roles, funding, initial team

What You Can Do Here

  • Select the target organization where the project will be created.
  • Enter the project’s core fields such as code, funding mode, start month, and duration.
  • Choose a saved role template set or keep a custom project labor-role set.
  • Define the initial funding sources and payout inclusion flags.
  • Add the initial supervisors, managers, and employees before the first save.
  • Assign an initial labor role to each initial member.

Typical Use Case

  1. Open /admin/projects/new from the project registry.
  2. Fill out the metadata and choose the role-template strategy.
  3. Enter the starting funding model.
  4. Add at least one supervisor and any optional initial members.
  5. Create the project when all sections are complete.
Click the screenshot to open it full screen.

Create Organization

The organization registry uses a popup form for tenant creation. This is the route used before a new organization can receive its first project.

Route/admin/organizations
EntryOrganizations page → Add new

What You Can Do Here

  • Review the organization list with current tenant names and counts.
  • Create a new organization with its name, short name, and default currency.
  • Edit existing organization metadata from the row-level action.
  • Use the registry as the pre-project check to confirm tenant setup is ready.
Click the screenshot to open it full screen.

Users Admin

The global users page is the central directory for platform accounts. This is where a superadmin looks up user state across organizations rather than from within a single project team page.

Route/admin/users
Main actionsFilter users, edit rows, inspect pending invite states

What You Can Do Here

  • Filter the user registry before paging through results.
  • Inspect each global user’s state from the grid.
  • Edit admin-managed user fields from row actions.
  • Reach pending-invite operations for non-superadmin users when applicable.
  • Use the page to answer cross-organization user questions that a project-level members page cannot answer.
Click the screenshot to open it full screen.

Role Template Sets

Role template sets are the reusable labor-role bundles used during project creation. Superadmins maintain this reference data once so later projects can copy a stable role set.

Route/admin/role-template-sets
Main actionsFilter, reset filters, create template set, edit existing set

What You Can Do Here

  • Inspect the currently available template sets.
  • Create a new template set before creating future projects.
  • Edit the current definition of an existing template set.
Click the screenshot to open it full screen.

Currencies

The currencies registry exposes the supported currency list and its editable rates. This is the place to verify usage context before changing active or numeric values.

Route/admin/currencies
Main actionsFilter, reset filters, edit a currency row

What You Can Do Here

  • Review the list of supported currencies.
  • See which rows are editable from the current admin page.
  • Open the row-level edit flow for rates or active-state changes.
Click the screenshot to open it full screen.

Audit History

The audit page is the cross-platform review surface for recorded actions. It is useful for onboarding because it shows where superadmins go when they need to confirm that a change happened and inspect the logged event stream behind an operation.

Route/admin/audit
Main actionsFilter audit rows and inspect more details per row

What You Can Do Here

  • Filter audit rows before scanning the event list.
  • Reset the current filters if the page needs to return to the default view.
  • Open the row-level “More” action to inspect a specific event more closely.
Click the screenshot to open it full screen.