Administration
Users & Departments
From Admin Users, an administrator adds new team members, assigns their role and department, resets passwords, and deactivates accounts that should no longer sign in — deactivating rather than deleting keeps that person's history intact on projects they worked on.
Admin Departments manages the department list itself, which is what powers department-scoped views elsewhere (an HOD's project list, for instance).
Letting other roles manage users
User and department management doesn't have to stay with the administrator. In Roles & Permissions, tick Users → Manage users and/or Departments → Manage departments for a role — an HR role, for example. People with that role then see a Users & Access group in the menu with just the pages they were given.
- They can create and edit users, activate or deactivate accounts, and send login details.
- Admin accounts are protected — they are marked Admin only and can't be edited, deactivated or sent a new password.
- The Admin role can't be given to anyone, and nobody can change their own role.
- Roles & Permissions, Settings, Audit Log, Backup and System Update stay with the administrator.
Roles & Permissions Setup
The seven built-in roles covered in Roles & Permissions can be fine-tuned from Admin Roles — adjusting exactly what each role can view, create, edit or approve, down to individual actions like assigning tasks or approving budgets. New roles can also be added here if the built-in seven don't quite match how your organization is structured.
System Settings
General configuration for the deployment lives at Admin Settings — the displayed application name and subtitle, your organization's name as it appears on-screen, the logo and favicon shown in the interface, and the default language new users see before they pick one for themselves. This is also where Email Notifications are switched on system-wide.
Report Template
From Admin Report Template, an administrator chooses which sections appear in every Project Report (PDF) — Project Overview, Key Metrics, Milestone Progress, Overdue Tasks, Upcoming Deadlines and Team Workload can each be switched on or off — plus the header band color and an optional footer note (a disclaimer, full company name, or confidentiality line, shown at the bottom of every report). This is one shared template for the whole system, not one per project.
AI Settings
Every AI feature listed under All AI Features has its own on/off switch here, so any feature can be disabled individually without affecting the others. Each feature can also be set to run on Google Gemini or Zeta AI (the company's own AI server); with the fallback option on, a feature set to Zeta AI automatically answers with Gemini if Zeta AI fails. Under Automation, administrators also switch the Project Monitor on or off and set the number of days for each of its checks; Scan Now runs a check immediately and Send the Monday Report Now sends the weekly report straight away to everyone who would normally receive it — only needed if the scheduled report was missed. The team workload summary (formerly the weekly digest) is part of that same Monday report; tick "Include the team workload summary in the Monday report" in the Project Monitor box to keep it.
To see a report before it goes out, use Send a Test to Me: choose a user under "Content as received by" — for example your CEO or a PM — and click Send Test. You get exactly what that person would receive on Monday, marked [TEST], and nobody else is sent anything; the real Monday report still goes out as scheduled. If your own account email isn't a real mailbox, type an address in "Send email to (optional)" and the test email goes to that address only (the notification still appears in your account). Tip: run Scan Now first so the test uses the latest issues.
From General Knowledge (Zetty) on the same page, administrators upload company-wide documents that the chat assistant refers to for every project — see Zetty Knowledge Base. This is available only when the chat assistant runs on Zeta AI.
Audit Log
A running record of who changed what and when — role and permission changes, user account changes, and other administrative actions — for accountability and for tracing back a change nobody remembers making.
Database Backup
From Admin Backup, an administrator can trigger a full database backup on demand, download any previous backup file, or remove old ones that are no longer needed. Keeping a recent backup on hand, off-server, is worth doing on a regular schedule rather than only when something's already gone wrong.
System Update
From Admin System Update, an administrator applies new application updates directly from the browser — no server access or command line needed. The current version and update history are shown on the same page, so it's clear what's installed and when it last changed.