1. The My Work inbox
My Work is one page that gathers everything with your name on it, so you do not have to visit four screens to find out whether anything needs you.
Requests currently at your level. Empty for most employees — see the Approvals chapter if it is not empty for you.
Everything on your task board that is not done, with a link through to the calendar view of them.
System notifications you have not opened — approvals moving, requests decided, announcements.
Your last seven days of in and out times, for a quick check that nothing is missing.
The same figures appear as tiles on your home page. My Work is the page you open to act; the tiles are there to tell you whether you need to.
2. The task board
Tasks are personal notes with a due date. Nobody is scoring you on them — they exist so the things you promised in a meeting do not live on a paper scrap.
The board has three columns, and you move a task by dragging it:
-
Add a task
Use the quick-add box. A title is enough; a due date makes it show up in the right place later.
-
Edit it in place
Click the text to change it. No separate edit screen.
-
Attach a file or a picture
Attachments can be added to a task, and images open full size when clicked.
-
Drag it as it progresses
Moving a card to Done takes it off your open list and out of your overdue count.
It is the same board everywhere. The task list on your home page, the To-Do tab inside the leave dialog, and the board itself are three views of one list. A task added in any of them appears in all of them, and moving it between columns works from any of them.
Tasks with a due date also appear on the calendar, so a busy week is visible before it arrives rather than after.
3. The bell and the chat button
There are two separate unread counts, and they never mix. This trips people up, so it is worth thirty seconds.
| Where | Counts | Examples |
|---|---|---|
| The bell header |
System notices — things the ERP is telling you | Your leave was approved · a request has reached your level · an announcement |
| The chat button floating, bottom corner |
Messages from people | A colleague's message · a mention · a missed call |
So a bell showing nothing does not mean nobody has written to you, and a quiet chat button does not mean your leave has not been decided. Check both, or check My Work, which shows the notice side in full.
Clicking the bell opens your notifications; the Unread notices tile on your home page opens the same list already filtered to unread.
4. Chat
ZakERP has messaging built in, reached from the floating button in the corner of every page. It exists so that a question about a document can be asked next to the document, without the answer disappearing into a personal phone.
- Contacts — your colleagues, ready to message. No group to be added to first.
- Voice notes — record and send, with a preview before you send it. Far faster than typing on a phone in a workshop.
- Edit and delete — fix a message after sending. Edited messages are marked as edited.
- Forward — pass a message to someone else; the result is tagged as forwarded so context is not lost.
- Files and pictures — drag one into the conversation. Images open full size when clicked.
- Emoji — because tone survives better with them than without.
Chat is not the record. Approving in chat approves nothing, and a leave request agreed in a message does not exist until it is in the system. Use chat to discuss and the screens to decide — that is what keeps the audit trail honest and protects everybody in it.
5. Shortcuts
The Shortcuts panel on your home page is your own list of links to the screens you open constantly.
On a page you use often, use Add This Page and it is saved. Use Add new to enter a link yourself, and Delete to drop one you no longer need. The list is yours alone — it is not a menu grant, and it cannot open anything your role could not already open.
6. A working habit
The people who find ZakERP calm rather than noisy tend to do the same small thing: they open My Work once at the start of the day, clear what is there, and close it.
Approvals get decided while they are small, tasks get moved before they are overdue, and notices get read while they still matter. Reacting to every notification as it arrives feels more responsive and is, in practice, slower for everyone.