Tasks

In Cakewalk, Tasks represent the actions users need to take to complete requests. Tasks are automatically created when requests require input from an approver.

👥 Who It Applies To

Role	Capabilities
Users	Complete tasks assigned to them (e.g., approving requests if they're part of a user group).
Managers	Approve/deny access for their team, handle offboarding tasks, review requests.
App Owners	Approve/deny requests for apps they own.
Admins	Oversee all tasks, reassign tasks, complete tasks directly, manage escalations.

---

📖 Key Concepts

• Tasks: Represent the specific steps required to complete a request. They are automatically generated by policies when input is needed from an assignee.

• Task Types:

  • Review Tasks → Require approval or denial (e.g., approve access requests).

  • Action Tasks → Require a concrete change (e.g., grant/revoke access, update permissions, archive apps).

  • Standalone Tasks → System-created outside of request flows (e.g., install the browser extension, review onboarding/offboarding).

• Policies & Requests: Tasks are always generated from an underlying request and the policy assigned to it (See Policy, Request and Task Data Model)

💡Why this matters: Tasks operationalize governance, embedding compliance into daily workflows without requiring admins to chase people.

---

🛠 Task Workflows

Approve / Decline Requests

• Definition: Review tasks generated when an employee requests access, a permission change, or an app removal.

• Steps:

  1. Open the task in Slack or the Cakewalk dashboard.

  2. Review details (requester, app, justification, last activity).

  3. Select Approve or Deny (optional justification required).

• All decisions are logged for auditability.

• Why this matters: Ensures app access is governed and auditable, while keeping approval workflows fast and efficient.

---

Complete Action Tasks

• Definition: Action tasks generated when workflows require concrete changes (e.g., granting/removing access, updating permissions, archiving apps).

• Steps:

  1. Open the task from Slack or Cakewalk dashboard.

  2. Perform the required action in the third-party app (e.g., provision a user, change permission, archive app).

  3. Mark the task as completed.

• Why this matters: Turns governance workflows into concrete outcomes, ensuring accountability and visibility.

---

Complete Standalone Tasks

• Definition: System-created tasks not tied to a user request.

• Examples:

  • Install the Cakewalk browser extension.

  • Confirm onboarding/offboarding steps.

• Why this matters: Embeds security and compliance steps into daily workflows.

---

Reassign Tasks

• Definition: Admins can reassign tasks if the original approver is unavailable or a workflow is blocked.

• Steps:

  1. Navigate to Request log in Cakewalk.

  2. Locate the task within the corresponding request.

  3. Select Reassign → choose a new assignee.Task is routed to the new assignee.

• Why this matters: Prevents bottlenecks and ensures workflows don’t stall when someone is unavailable.

---

📋 Task Actions at a Glance

Action	Who performs it	What happens	Why it matters
Approve / Deny	Assignees	Review and decide on requests (access, permissions, removal).	Ensures governed, auditable access workflows.
Complete Action Task	Assignees	Perform required changes (provision, deprovision, update permissions, archive app).	Turns governance workflows into concrete, trackable outcomes.
Complete Standalone	Depends on task	Fulfill system tasks (install extension, confirm onboarding/offboarding).	Embeds compliance/security steps directly in user workflows.
Reassign Task	Admins	Redirect task to a new approver.	Keeps workflows moving and avoids bottlenecks.