Skip to main content
This page lists every notification TimeTracker can send. Use it to find out why a message arrived, or which setting turns it off. Each notification has three facts that matter to you:
  • What triggers it – the action or the scheduled check that fires it.
  • Who receives it – the people the system picks as recipients.
  • Which channels it uses – in-app, email, or a webhook.

How to read the tables

Every notification belongs to one category. Categories are what you switch on and off in your notification settings. You cannot switch a single notification type on or off – you switch its whole category. Channels in the tables mean:
  • In-app – a row in your Inbox and a count on the bell.
  • Email – a message to your account email address.
  • Webhook – a POST to an endpoint you configured. See Webhooks.
Default means the channel is on unless you turn it off. Available means the channel can carry the notification but is not on by default. Always means the channel cannot be switched off.

The rule behind every table

You are never notified about your own action. The person who did the thing is removed from the recipient list. If you assign a task to yourself, no notification is sent. If you are the only person who would have received it, no notification exists at all. There are exceptions, and they are all messages about you that the system raised on your behalf – a reminder you scheduled, an export you asked for, a security alert on your own account. Those are marked self in the tables below.

Tasks and assignments

Category: Work assigned to you.
Completion watchers are a named list an admin sets, not a role query. If you want a delivery lead to hear about every task that gets finished, add them to the watcher list rather than changing anyone’s role.

Timesheets

Category: Approvals.
The reviewer who closes a period is not notified about the close. Only the people whose time got locked are.

Approval escalations

Category: Approvals. Priority is high, so these stand out in your Inbox. A submitted approval that nobody acts on escalates on a fixed schedule: Each level fires once per item. A repeated scan cannot send the same escalation twice.

Time Clock

Category: Approvals, except where noted. Time Clock is off by default. See Apps and modules.

Time off

Category: Approvals, except where noted.

Expenses

Category: Approvals. “Eligible to approve” means the person holds the approval capability and the submitter is inside their supervision scope. See Supervision scope.

Invoices and payments

Category: Money.
Client-facing invoice emails never create an in-app notification. A client contact is outside your workspace and never sees your internal Inbox.

Budgets

Category: Money. See Budget alerts for how thresholds are set.

Projects

Category: Project changes, except where noted.
A portal comment goes to one person on purpose – the project manager. Mailing every Owner and Admin would make client conversation the noisiest thing in the product.

Exports

Category: Project changes. Export notifications are kept for 30 days, shorter than the usual 90, because the download itself expires.

Members and access

Category: Account.
An invite email is not optional. An invitation that cannot email the invitee is useless, so this one type ignores every preference.

Security

Category: Security. Priority is high. Email is always on for these – you cannot switch it off. Security notifications are kept for 365 days, far longer than the 90-day default, so you can look back at an access question months later.

Billing and plan

Category: Money. These messages cover access only – what your workspace can now do and what you should do about it. Receipts, tax invoices and card retries come from the payment processor, not from TimeTracker.

Daily reminders

Category: Daily reminders. These are always about you, so you always receive your own. Reminders are kept for 30 days. They arrive at the time you chose, in your own timezone. See Reminders.
A reminder never gets rolled into a digest and never gets held back. The whole point of a reminder is that it lands at the moment you picked. Switching the Daily reminders category off still stops them completely.

Digest summary

Category: Account. See Digests.

Retention

Notifications do not stay forever. Retention only removes the notification record. It never touches the task, timesheet or invoice the notification was about.

Permissions

Anyone can receive notifications. What you receive depends on what you can see, not on a notification setting. A capability is not a scope. Holding time.approve means you may approve. Your supervision scope decides whose timesheets reach you. See Roles and capabilities.

Common questions

Because you did it. TimeTracker removes the person who performed an action from that action’s recipient list. You already know what you did.The exceptions are messages the system raises on your behalf – your own reminders, your own export, your own security alerts, and your own billing notices. Those are marked self in the tables above.
No. You switch a whole category on or off per channel. The categories are listed at the top of this page. This keeps the settings screen short and keeps the rules predictable.
Three. The invite email that goes to a new person, and the two security alerts – email address changed and unusual sign-in. Everything else is yours to control.
No. A client-portal contact is outside your workspace. Client-facing messages such as a sent invoice go out by email only and never create an in-app row.
Recipients are resolved per notification type. Some go to the whole Owner and Admin group, some go to one named person, some go to whoever can approve the item. Find the type in the tables above and check the “Who receives it” column.
A notification can also be sent as an HTTP POST to an endpoint you own, so another system can react to it. Set one up under Webhooks.

Troubleshooting

A notification type is missing entirely. The app it belongs to may be turned off. Time Clock, for example, is off by default, so no timecard notification can fire. Check Settings → Apps. Approvals never arrive. Approval notifications need someone who can approve. If nobody in the workspace holds the approval capability, or nobody’s supervision scope covers the submitter, the recipient list is empty and no notification is created. Emails stop but in-app rows keep arriving. Your email channel is off for that category, either by your own choice or by a workspace default. See Your notification settings.

Notifications overview

How the notification system fits together.

Your notification settings

Choose what reaches you, and on which channel.

Inbox

Read, filter and clear your in-app notifications.

Reminders

The daily checks and how to schedule them.

Webhooks

Send notifications to your own systems.

Roles and capabilities

Who can do and see what.