How to Add Members to User Groups and Assign Task-Level Edit Permissions Using Node-Level Authorization in KTern Planner?
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 Authorization is a permission framework in KTern
Planner that determines which users can edit specific tasks (nodes) in the
project hierarchy. Only users within the assigned User Group — or those who
inherit permissions from a parent task — can modify task details such as dates,
resources, and dependencies.
Step 1 — Create a User Group
- Navigate — Transformation
Hub → Users → User Groups
- Action — Click + Add
New User Group (top right corner)
- Fill in — Group
Name, Description, Owner, and Members
- Save — Click Create
to finalize the group
Only Project Administrators can create or delete
User Groups. Group Owners can edit their own group details.
Step 2 — Add or Edit Members in a User Group
- Locate — Find the
User Group in the list
- Edit — Click the
pencil (Edit) icon in the rightmost column
- Members — Add or
remove users as needed
- Save — Click Save to
apply changes
Step 3 — Assign User Group as Editor to a Task
- Open — Navigate to
the KTern Planner
- Locate — Find the
task you want to restrict editing for
- Editor Column — Click
the Editor column for that task
- Select — Choose the
User Group from the dropdown (multiple groups can be assigned)
- Result — Only users
in the assigned group can now edit that task

How Authorization Inheritance Works
If a parent task has an Editor Group assigned, all child tasks automatically inherit that authorization. When a different group is explicitly assigned at the child level as the Editor, the child task holds both its own assigned Editor Group and the inherited group from the parent — and this combined inheritance continues to propagate down to all further descendant tasks.
|
Authorization Hierarchy
Example
Task 1.0 →
Editor: Team A
└── Task 1.1 →
Inherits: Team A
└── Task 1.2 →
Editor: Team B, Inherits: Team A
└── Task 1.2.1 →
Inherits: Team B, Team A
|
Key Rules
- Project Administrators can change the admin designation
and manage all user groups
- Group Owners can edit their own user group details
- Only users in the editor group (or inherited group) can
edit task details
- All users can view tasks, but editing is restricted to
authorized personnel
- Deleting a User Group requires reassigning all task
ownership first
Related Articles
How Does Inheritance Work in Node-Level Authorization in KTern Planner?
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 ...
What Are The Different Types of User Access Levels In KTern.AI?
This document outlines the four different user access control types available in KTern.AI: Super Standard Basic Limited Each access level grants specific permissions for users to interact with various KTern.AI functionalities. 1. Super User Super ...
How Can You Effectively Use KTern’s New Simulation Planner?
To begin, log in to KTern and navigate to the desired project. Follow the steps below to access and utilize the Simulation Planner effectively: Navigating to the Wave Landing Page and Planner Preview Once logged in, go to the Timeline under Digital ...
How to invite a new user to a project in KTern?
Inviting a new user When users log into the KTern application, they will automatically land on the Home - Project Launchpad page, where you can view a list of projects that they are a part of on Home Launchpad. Then you can select and enter the ...
How to plan day wise activities for the initial phase using KTern.AI ?
Planning day-wise activities can be a daunting and time-consuming task, especially in large, complex projects. Teams often face several challenges when breaking down goals into daily deliverables: Why day wise planning is important? 1. Foundation ...