For administrators

Administration

The administration console is where people get access, roles are defined, delivery channels are configured, and the system's health is watched.

๐Ÿ‘ฅ Users๐Ÿ”‘ Roles๐Ÿ“จ Notificationsโš™๏ธ Operations๐Ÿ† Progress
Who can open the console?

Only people with system administration access can open Administration. Each page inside also needs its own permission, so the console can be shared between several administrators with different responsibilities.

The console at a glance

Overview

System health: users, active projects, background services, and recent notification volume. Shows healthy or needs attention.

Users

The people directory: accounts, status, passwords, roles, and exceptions.

Roles

Reusable permission packs and the full permission catalog.

Notifications

Email, browser push, and WhatsApp delivery, with a test-message button.

Operations

Background workers, queues, schedules, and incidents.

Progress

Rules for XP, daily caps, excluded projects, and the leaderboard.

Project-specific matters such as ERP connections, budgets, and stage decisions are managed inside each project, not in the console.

Manage users

  1. Create the accountAdd the person's name and email and set their status.
  2. Set a passwordSet an initial password, or reset a forgotten one. Passwords need at least 14 characters.
  3. Assign rolesGive the person one or more roles. This is the normal way to grant access.
  4. Add exceptions only when neededA direct allow or deny handles a true one-off case. Keep these rare.
Disable instead of delete

Disabling a user stops them signing in, but their history on projects stays intact.

The user hub

Open any person to see their hub for a chosen week, month, or custom range of up to a year.

SectionWhat you see
OverviewItems that need attention, plus a Progress panel with level, XP, recent awards, and whether tracking is on.
WorkItems where they are assignee or reporter: open, overdue, and due soon, grouped by project and status.
TimeRecorded time, billable time, totals per project, timer versus manual entries, and whether a timer is running now.
AccessRoles and direct exceptions. You can also add the person to projects here.
ActivityTheir actions on work, projects, and documents.

How permissions work

Access is built from small, specific permissions, such as "read financials" or "approve change requests". A role is a named bundle of permissions. Give people roles, and they get exactly what the role includes.

Layer 1

Signed in

A valid, revocable session.

Layer 2

Permission

The action is allowed by the person's roles.

Layer 3

Project access

The person belongs to the project, or has a grant for it.

Layer 4

Data protection

The database itself refuses data the person may not see.

  • Read and write are separate. Someone may open the Timeline but not move dates, or see Financials but not change them.
  • Hiding a button is not security. Every action is checked on the server, whatever the screen shows.
  • Labels are not permissions. Being named on the project board or listed as a stakeholder does not grant access.
  • New permissions grant nothing until a role or a person is given them.

Build a role

Under Roles, create a custom role by selecting permissions from the catalog. System and protected roles are locked to keep the basics safe. A few common shapes:

Example roleTypical access
Team memberRead and update work items. No access to finance.
Finance ownerRead financials and, where appropriate, manage budgets and costs.
Change approverApprove change requests. Give this only to people with real authority.
Stage decision makerRecord go / no-go at stage gates.
Always check the result

After changing a role, sign in as a test user with that role, or ask the person, and confirm that the menus and project tabs match what you intended.

Notification delivery

Under Notifications, set up the providers used to deliver alerts: Email (SMTP), browser push, and WhatsApp. Secrets are sealed once saved and are never shown again. Use Send test to confirm each channel works.

Operations

Operations shows the background work that keeps the app running: workers, queues, schedules, and incidents. Notifications and automations run here. If alerts are delayed or a schedule is late, start here.

Progress settings

Turn XP tracking on or off, and set the daily cap, the point table, the reopen window, the excluded projects, and the leaderboard. Turning scoring off doesn't change any project work, and past awards are kept.