Sign in to access your secure office database
Staff accounts are provisioned via the Firebase Authentication console.
| Company | Work Type | Staff | Due Date | Priority | Status | Billing | Remarks | Actions |
|---|
Computed from the client list already loaded — no extra cost to check this. Email greetings go out automatically to everyone shown here with an email on file. WhatsApp wishes go out automatically too, but only to Priority clients — check the column below before sending anything by hand.
Loading…
Overdue and upcoming work for whoever is currently selected in the Staff scope above — switch to All staff for the full picture. Reminders themselves go out automatically each morning; this is only to check the contact details are actually reachable before that happens.
Loading…
One record per client. Used to fill in details when adding a task, to decide which recurring work each client needs, and to tell apart clients with similar names.
Loading…
Requests clients have submitted through the Portal. These are not tasks yet — review each one and convert it into a proper task with a due date and assignee.
Loading…
Notices picked up automatically from the office inbox. This is an alert list, not a task list — open the notice on the department portal, deal with it there, then update the status here so it stops showing as pending.
Loading…
Who may open the Task Tracker, and which client each Client Portal login belongs to. Only an admin can change these.
Add the email address each staff member signs in with. It must match exactly. Everyone who uses the Tracker must be listed here before the new security rules are published — anyone missing will be locked out.
Loading…
Link a client's email address to their client record. A client who signs into the Portal sees nothing at all until you link them here — signing in with an email does not prove who someone is, so this step is deliberate and cannot be automatic.
Loading…
The Client Portal's security rules only let a client see tasks that carry their
clientId — no task has one yet. This checks every task against your Clients
list by GST/PAN, then by company name, and shows you the counts. Nothing is
written until you review the numbers and press Apply below. Safe to run more
than once — it only touches tasks that don't already have a clientId.
New and edited tasks get this automatically from now on; this is only for tasks that
already existed before today.
You marked this task as Done. Would you like to notify the client?
Are you sure you want to delete this task?
Creates this period's recurring work from the client list. GST returns for monthly filers every month and for quarterly filers at each quarter end; income tax returns and audits in March. Nothing is created until you have seen the preview and pressed the button.
Upload the client spreadsheet. Nothing is saved until you have seen the preview and pressed Apply. Clients are matched on GSTIN where present, otherwise PAN — so re-importing updates existing records rather than creating duplicates.
For a company, firm or trust, the date of birth field above belongs to the entity's date of incorporation, not a person — so it is never used for birthday greetings. Add each partner or director here instead, and they will each be wished on their own birthday. For a proprietor or individual, this section isn't needed.
Upload an Excel (.xlsx) or CSV file to bulk import clients and tasks.
Only the account(s) below can delete tasks or restore a backup. Everyone else can add, edit, and update tasks normally.
To change who's an admin, edit ADMIN_EMAILS near the top of this file's code and redeploy — and update your Firestore Security Rules to match (see SETUP_GUIDE.md).
A full backup downloads every task exactly as stored (including portal credentials), so it can fully restore your data later — unlike the CSV/PDF reports, which are for reading, not restoring.
Portal logins used to be stored on each task, so the same login was repeated many times. This copies them onto the matching client records, removing repeats. Nothing is deleted from the tasks, so the originals remain if anything looks wrong. Run it once.
Links each login to the staff name used on tasks. Once someone is listed here, opening the Tracker shows their own work straight away, and the edit history records their name rather than their email address.
This overwrites any existing task that shares an ID with the backup. Use this to undo an accidental mass-deletion or data problem — not for routine use.
Same idea, for client records (PAN, GSTIN, contact details) instead of tasks — reads a
CCA_Backup_Clients_...json file (from the automated nightly backup) and overwrites
any existing client that shares an ID with the backup.
Restoring a backup is an admin-only action.
| Work Type & Period | Due Date | Status | Billing |
|---|