Skip to main content

Complete and manage Tasks

Tasks bring work from People, Planner and other Markular modules into one personal list. A Task shows the work you need to do, the module it belongs to and its due date when one is set. Opening or completing a Task does not give you wider access to the related personnel or business information.

Some Tasks are a step in a larger employee journey or another coordinated process. You complete these Tasks in exactly the same way as a directly assigned Task. Markular updates the journey automatically when the Task is completed, so you do not need to report the same work in a second place.

When this applies, the Task shows the journey name and a short progress summary, for example 2 of 3 activities completed. A later activity appears only when the work it depends on is finished. You see the context needed for your own Task, not the contents of colleagues' activities or who they are assigned to.

Find the work you need​

Open Workspace, then My Tasks. Search by Task title or description, or filter the list by module, status or due date. The status filter keeps Not applicable (someone said it did not apply) and Deviation (someone could not get it done) apart from Not needed (an optional journey activity the journey no longer needed). Your choices stay in the page URL, so browser navigation and bookmarks return you to the same view. Avoid putting sensitive personal information in the search field because search terms are part of that URL.

Select Why me? on a Task to see whether it was assigned directly, through a Group or Function, or because you are the employee or active manager concerned. This explanation is based on the same responsibility rules Markular uses when it decides whether the Task belongs in your list.

Choose how Task notifications arrive​

Select Notifications on My Tasks to choose how Markular reminds you about new assignments and deadlines. In-app notifications appear under the bell in the top bar. A notification about a journey Task names the journey and the person it is about, and usually the Task. Selecting a Task notification opens My Tasks with only that Task, and Show all my tasks takes you back to the list. Task email never names the Task, but its button opens the Task the same way. Task email can be sent immediately, collected into one daily summary at your chosen local time, or turned off. Due-soon and overdue reminders can be controlled separately.

You get a due-soon reminder about two days before a Task's due date. If the due date passes and the Task is still open, you get an overdue reminder, and then one more every week until the Task is closed. If you get a Task less than two days before it is due, you get no due-soon reminder, since the notice that gave it to you shows the due date. If you get a Task that is already overdue, including when you are added to one, or its due date is moved to a date that has passed, your first overdue reminder comes a week later. A Task that waits for an earlier Task sends no reminders until it is ready for you. Turning off overdue reminders also stops the weekly ones.

HR following a journey can also send you a reminder about a Task. It arrives in Markular and by email right away, also with a daily summary, unless you have turned Task email off.

Changing these choices does not affect product announcements or existing Timekeeper notification settings. An email contains a safe sign-in link and a general explanation; it does not copy the Task title, HR details or document contents. Markular checks that you can still access the Task before each notification is delivered and checks access again when you open it.

A Task can show an action such as Open person in People. Markular only shows the action when you already have access to that person and checks access again when the profile opens.

Some Tasks show a few details about the person they concern, such as the last working day, employee number or work email. The step the Task comes from decides which details appear, and they show only while the Task is ready or in progress. A Task that waits for an earlier step shows only the person's name, and a completed Task shows none of them. Sensitive personal data, such as identity numbers, private contact details or health information, is never shown on a Task.

If the action is absent, use the Task description to continue or ask the Task owner for help. The Task itself does not grant access to a profile, document, schedule or timesheet.

A follow-up from an employee conversation behaves the same way. The assignee sees the agreed Task title, description, due date and status. Private notes, individual preparation and the shared conversation outcome are not copied into the Task. Open conversation is available only when the assignee is also a participant; Markular checks this again each time the conversation opens. The surrounding Task interface, status and due date follow your language and regional settings. The agreed title and description remain exactly as written by the participants. Platform notifications and email are delivered according to the assignee's saved notification and language settings.

If a module is later removed from the organization, its historical Tasks remain visible but cannot be opened or completed. The Task explains why the action is unavailable. This preserves accountability without bypassing the organization's current module setup.

Complete a Task assigned to you​

  1. Open Workspace, then My Tasks.
  2. Find the Task you want to finish.
  3. Review its description, module and due date.
  4. If the Task asks for evidence, select Activity & evidence, choose an available document and select Add.
  5. Select Mark as done.

If your Task is part of a journey, completing it may make the next activity available to you or a colleague. My Tasks refreshes automatically so newly available work appears without a second confirmation step.

If the work takes a while, select Start first. The Task then shows In progress with Started by you, so colleagues who share it can see that someone is on it. Select Stop working on it to set it back to not started. Tasks you read and acknowledge or review and confirm have no Start, because they are one step, and neither does a probation or exit conversation, which you complete in the conversation itself.

Where a Task allows it, Not applicable closes it without doing it. If you like, say why in the dialog. Everyone in your company who sees the Task can read your reason; an external contact who shares it does not.

When a task could not be done​

Sometimes you can't get a Task done, for example when the phone was never handed in. Where the Task allows it, select Record deviation instead of leaving it open:

  1. Under What happened?, choose a reason: Not returned, Not done in time, The person did not respond, Could not be done or Other. Some Tasks offer reasons of their own as well, listed before Other.
  2. Write a Note about what happened. Some Tasks require it; on others it's optional.
  3. Select Record deviation.

The Task closes for everyone who shares it, and this can't be undone. Someone gets a new Task to follow it up, due in 7 days: the person who started the journey, the person's current manager or specific people, as the checklist says. If no one can be found, the person who started the journey follows it up. The dialog names who that is, for example Lise Leder gets a task to follow it up, or Lise Leder and 2 others when several share it. Only you, HR following the journey and the person following up can read your note.

The journey stays open until the follow-up is done. If the person who follows up can no longer be given the Task, Markular says so and the Task stays open. Tell HR.

The follow-up Task says which deviation it follows up, who recorded it and when, with the note. When you have dealt with it, select Mark as done. You can write What was done? before you close it.

A completed, not applicable, deviation, not needed or cancelled Task remains visible with its final status and cannot be completed again. A line under the status says how it ended: who completed it, who marked it not applicable and why, if they said, Deviation with the reason and who recorded it, The required tasks were done for an optional journey activity that was no longer needed, or why it was cancelled. If another browser or administrator changes the Task while you are viewing it, Markular asks you to refresh instead of overwriting the newer change.

Read and acknowledge information​

Some journey Tasks ask you to confirm that you have read and understood a specific piece of information.

  1. Open Workspace, then My Tasks.
  2. Find the Task and select Review and acknowledge.
  3. Read the complete statement in the dialog.
  4. Select I have read and understood the information above.
  5. Select Acknowledge.

Markular records who acknowledged the statement and when. The button remains unavailable until you select the confirmation. This action is an acknowledgement, not an electronic signature or consent. If a document requires a legally binding signature, follow the separate signing process provided by your organisation.

Confirm a controlled action​

Some Tasks require a responsible person to confirm that an agreed action, such as closing employee access during offboarding, has been completed.

  1. Open Workspace, then My Tasks.
  2. Find the Task and select Review and confirm.
  3. Read the complete confirmation statement.
  4. Select I confirm that this action has been completed.
  5. Select Confirm completion.

Markular records who confirmed the action and when. The button remains unavailable until you make the explicit confirmation. This records the responsible check; it does not itself close an account in an external system.

Add comments, attachments and completion evidence​

Select Activity & evidence on a Task to keep the practical conversation and supporting references with the work. Only the people the Task is assigned to can add a comment or reference. For shared work, that is everyone who currently receives the Task. Closed Tasks remain read-only.

  • Comments are for short, work-related coordination. Avoid copying sensitive document contents or unnecessary personal details into a comment. A comment from an external contact, someone outside the organisation who was given the task in a journey, shows their name with an External label. When an external contact does the task themselves, the comments say External contacts on this task can read these comments. Keep that in mind before you write.
  • Attachments link an existing document to the conversation.
  • Completion evidence is a document that the Task type requires before the work can be marked as done. The Task shows how many valid items are still missing.

Tasks do not copy or take ownership of attached documents. People or another source module remains responsible for the document, its access rules and its retention. Markular checks your document access when the reference is displayed and again whenever you download it. A Task therefore does not create wider document access for you or another recipient.

If a referenced document is deleted, rejected by file validation or no longer available to you, the Task keeps an understandable unavailable reference but does not expose its previous name or contents. Required evidence then blocks completion until valid evidence is available. Comments and document references have retention classifications separate from the longer-lived Task history, so the organization can apply an approved retention schedule without erasing the Task's final status.

Complete work from a shared queue​

A shared queue lets a Group or Function share responsibility without creating a personal Task for every member. The Task explains why it appears, for example Assigned through Group: Personnel Coordinators.

  1. Open Workspace, then My Tasks.
  2. Find the Task and review the assignment explanation and due date.
  3. Do the work, then select Mark as done.

Anyone who currently receives the Task can complete it, add comments and evidence, or acknowledge or confirm it when the Task asks for that. Nobody has to take the Task first, and starting it does not lock it. When a colleague has selected Start, you see Started by with their name and can still complete the Task. Only the person who started it can select Stop working on it. When one person completes it, it is done for everyone, and the Task shows who completed it. If a colleague completes the Task while you are viewing it, Markular asks you to refresh instead of completing it twice.

Group and Function membership is evaluated from active, dated organization data. When work creates one Task per member, the recipients are fixed when the Tasks are created. For a shared queue, current membership is used for as long as the Task is open: someone who joins the Group sees the Task, and someone who leaves it no longer does. If you completed a shared Task, marked it not applicable or recorded a deviation, you keep seeing it, read-only, after you leave the Group. Due date reminders go to everyone who currently receives the Task and stop when it is closed.

Queue membership is responsibility, not data access. A Task never grants permission to a profile, document, schedule or timesheet. Markular checks the relevant module access again when related content is opened.

Cancel an assigned Task​

You need permission to manage Tasks. This permission lets you manage Task assignments; it does not by itself reveal the related HR, planning or document content.

  1. Open Workspace, then My Tasks.
  2. Select Manage tasks.
  3. Find the Task and select Cancel task.
  4. Choose the approved reason that best explains why the work is no longer required.
  5. Confirm the cancellation.

Cancellation is permanent for that Task. Markular keeps the Task and its history instead of deleting it. The change is also recorded in the Activity log without copying the Task title, description, related personnel data or document contents into it.

A Task that is part of an employee journey cannot be cancelled here, because the journey waits for it. Its row shows Open journey instead. On the journey you can mark the Task as done for the person, or cancel the whole journey. If you cannot open journeys, the row shows Part of a journey; ask someone who manages journeys. A Task from a checklist shows Part of a checklist and is closed from that checklist.

If a person no longer has an account​

Only people with an active Markular sign-in identity can receive newly resolved Tasks. Task history is retained if an earlier direct recipient is no longer available. Administrators will see Unknown recipient when Markular can no longer resolve that historical account. Work for a shared queue is shown as Shared queue, not as an unknown person.