Notifications
Notifications keep you informed about the work that needs you: tasks assigned to you, comments and @mentions, approvals waiting on your decision, deadlines and SLA alerts, and updates on processes and service requests.
You do not have to go looking for these events. Arketic brings them to you in two places — the notification bell inside the platform, and your email inbox.
Where Notifications Appear
| Where | What you see |
|---|---|
| In the app | A bell icon in the top bar, visible on every page. A red badge shows how many notifications you have not read yet — once you pass 99, it shows 99+. Click the bell to open the notification panel and read them. |
| The same events are emailed to the address on your account, so you stay informed even when you are not signed in. |
You receive both in-app and email notifications by default. See The Notification Bell for a full tour of the panel, and Notification Preferences to choose what you receive.
What Triggers a Notification
Notifications fall into four groups. The group matters because your preferences are set per group, not per individual event — see Notification Preferences.
Task Activity
| Event | Who is notified |
|---|---|
| A task is assigned to you | The new assignee |
| A task is unassigned from you | The person removed from the task |
| A task is completed | The task's assignees and the person who created it |
| A task is cancelled | The task's assignees and the person who created it |
| A task needs your approval | The approver |
| Your task's approval was rejected | The person who submitted it |
| A subtask is created | The parent task's assignees |
See Approvals for how approval requests work.
Comments & Mentions
| Event | Who is notified |
|---|---|
| Someone comments on a task | The task's assignees and the person who created the task — but not the commenter, and not anyone already @mentioned in that comment (they get the mention notification instead) |
| You are @mentioned in a task comment | The person mentioned |
The notification shows who wrote the comment, which task it was on, and the beginning of the comment text so you can judge whether it needs you right away.
Comments on a cancelled task do not send notifications.
SLA & Reminders
| Event | Who is notified |
|---|---|
| Task reminder | — |
| Deadline approaching | — |
| SLA warning — the task is getting close to its SLA target time | — |
| SLA breach — the SLA target time has been exceeded | — |
| Escalation | The people the escalation is raised to |
SLA warning and SLA breach emails are the most urgent alerts in Arketic, and they are sent to you immediately rather than being grouped with other emails. If you see one, act on it.
See SLA Policies to understand how target times are defined.
Process & Requests
| Event | Who is notified |
|---|---|
| A process completes | — |
| A self-serve process is started | — |
| A new service request arrives | — |
| A service request is assigned | The person it is assigned to |
| A service request is approved | — |
| A service request is resolved | — |
See Blueprints and Creating Requests.
Always delivered
Some alerts are workflow-critical and are always delivered, even if you have muted everything else. The main one is a cross-department request — a task that comes to you or your department from another department and needs a manager's approval. Silencing these would stall the approval and block the other team, so they always reach you.
Turning a group off is about reducing noise, not about opting out of your responsibilities. Approvals and SLA alerts are the ones people most often regret muting.
@mentions in Comments
Pulling a specific person into a task conversation is the fastest way to get their attention: they get a notification addressed to them, separate from the general comment notification.
How to mention someone
- Open the task and go to the comment box. See Task Details.
- Type
@followed by the person's name or the first part of their email address (everything before the@sign). For example, to mention the person whose email istestbekir@arketic.ai, type@testbekir. - Post the comment. The mentioned person receives a mention notification with the task name and the start of your comment.
| Detail | What to know |
|---|---|
| Upper/lower case | Does not matter — @Testbekir and @testbekir both work. |
| Turkish characters | Fully supported, so names containing ö, ü, ç, ş, ğ or ı can be mentioned. |
| Names with a space | A mention is a single @ word, so a two-word display name cannot be typed as one mention. Use the person's email handle instead — it is the reliable way to mention them. |
| Access check | A person is only notified if they can actually see that task. If they do not have access, they are not notified and nothing about the task or your comment is revealed to them. |
| No duplicate | A mentioned person gets the mention notification, not an additional comment notification for the same comment. |
If a mention did not reach the person you expected, the most common reason is that they do not have access to that task. Check that they are on the task or in the right department first.
When Notifications Arrive
| Channel | Timing |
|---|---|
| In-app (the bell) | Notifications show up in the bell and the unread badge updates as the events happen. |
| Email — most events | Emails are grouped and delivered together a few minutes after the activity, so you may receive several notifications in one email instead of one email per event. |
| Email — SLA warning and SLA breach | Sent immediately, on their own, so time-critical alerts are never delayed. |
Because most emails are grouped, a quiet inbox does not mean nothing happened. The bell is always the live view.
What You Can Do With a Notification
| Action | How |
|---|---|
| Read it | Click the bell to open the panel. Unread notifications are highlighted. |
| Open the related item | Click the notification. If it is about a task, that task opens directly. If it is about a service request or a process, you are taken to the Tasks area. |
| Mark one as read | Clicking a notification marks it as read. |
| Mark everything as read | Use Mark all as read in the panel header. It clears every unread notification you have, not just the ones on screen. |
Notifications cannot be deleted or snoozed, and there is no separate notification history page — the bell panel is where all of your notifications live.
Full details are on The Notification Bell.
Choosing What You Receive
You can silence any of the four groups for yourself in Settings → Notifications. Turning a group off stops both its in-app and its email notifications for you, and it affects only your account — your colleagues keep receiving them.
Your personal settings can only mute. If an administrator has turned a group off for the whole organization, you cannot switch it back on for yourself.
Administrators and super administrators set the organization-wide baseline in Tasks → Settings → Organization Settings → Notification Settings. Turning a group off there stops it for everyone in the organization. See Task Settings.
Step-by-step instructions for both are on Notification Preferences.
Troubleshooting
| Problem | What to try |
|---|---|
| I am not receiving any notifications | Open Settings → Notifications and check that the relevant groups are on. If a group looks unavailable, an administrator may have turned it off for the whole organization — ask them to check Tasks → Settings → Organization Settings. |
| I am not receiving emails | Check your spam or junk folder, and confirm the email address on your account is correct in Profile. |
| I get too many notifications | Silence a whole group you do not need — for example Comments & Mentions or Process & Requests — in Settings → Notifications. Keep Task Activity and SLA & Reminders on. |
| Someone I @mentioned was not notified | They probably do not have access to that task. Confirm they are an assignee or otherwise able to view it, then mention them again. |
| A notification did not open the item I expected | Some notifications do not point to one specific item and simply take you to the relevant area. If a link goes nowhere, the item may have been deleted; try refreshing the page. |
| An SLA alert arrived but no other email did | That is expected. SLA alerts are sent immediately; other notifications are grouped into a later email. |
Related Pages
- The Notification Bell — reading, clearing and navigating your notifications
- Notification Preferences — choosing which groups you receive
- Task Details — comments and @mentions
- Approvals — approval requests and decisions
- SLA Policies — how target times drive SLA alerts
- Task Settings — organization-wide settings for administrators