Understanding exactly what triggers the Approval Workflow helps teams plan changes efficiently and avoid creating unnecessary approval requests that lock tasks and slow project progress. Complete List of Workflow Triggers Trigger Scenario Workflow ...
When an Approval Workflow request is raised, all affected tasks are automatically locked. No user — including authorized users — can edit these tasks until the workflow is resolved. This article explains how locking works and what to do. Why Are ...
Authorization Inheritance allows child tasks to automatically adopt the editing permissions of their parent tasks, reducing the need to manually assign User Groups at every level of the project hierarchy. What is Authorization Inheritance? When a ...
In the Approval Workflow, not every stakeholder approves requests. Some group owners are assigned as Notifiers — they are kept informed but are not required to act. What is a Notifier? A Notifier is a User Group owner who receives workflow ...
A requester can withdraw a submitted Approval Workflow at any time while it remains in Pending status. This unlocks all affected tasks and permanently removes the request. When Should You Withdraw a Workflow? • You need to revise the proposed dates ...
As a designated Approver, you receive an email notification when a workflow request is assigned to you. You must review all impacted tasks and make a formal Approve or Reject decision inside KTern Planner. Step 1 — Access Pending Approvals Navigate — ...
When your authorized task update cascades to tasks owned by other User Groups, KTern automatically triggers an Approval Workflow. You must formally submit a request before the changes are saved. When Is an Approval Workflow Triggered? Any date update ...
Node-Level Authorization controls who can edit each task in KTern Planner. This article walks through creating User Groups, adding members, and assigning those groups as editors to specific tasks. What is Node-Level Authorization? Node-Level ...