Job Management uses a hierarchy model to define how responsibility is distributed across users in your organization. When registering a portal group, an administrator selects a hierarchy type that governs who can create jobs, execute work, and close jobs. This model reflects how your organization operates in practice.
Two-Level Hierarchy - Supervisor and Worker
In a two-level hierarchy, job management responsibilities are divided between two distinct roles: Supervisors and Workers.
•Supervisor: Oversees the job lifecycle. Supervisors create jobs, assign them to workers, monitor progress, resolve conflicts before job closure, and close completed jobs.
•Worker: Carries out the assigned work. Workers execute jobs, make edits in the job's branch version, and sync with the default version during active work.
This model suits organizations where oversight and execution are handled by different people, such as a field crew supervised by a project manager.
Responsibilities by Role
Responsibility |
Supervisor |
Worker |
|---|---|---|
Create and assign jobs |
Yes |
No |
Execute jobs and make edits |
No |
Yes |
Reconcile during active work |
No |
Yes |
Resolve conflicts and close jobs |
Yes |
No |
Single-Level Hierarchy - Worker Only
In a single-level hierarchy, a single user type handles the entire job lifecycle from start to finish. Workers in this model act as both the executor and the manager of a job.
Worker - acting as Supervisor - Creates and assigns jobs, performs edits, reconciles versions, resolves conflicts, and closes jobs.
This model suits smaller teams or organizations where individuals manage their own work end to end, without a dedicated oversight role.
How Hierarchy Affects the System
The hierarchy type configured for a group determines which UI elements and actions are available to its members.
It also shapes the approval workflow around job closure:
•In a two-level hierarchy, a job completed by a worker must be reviewed and closed by a supervisor. The supervisor is responsible for the final reconcile and post.
•In a single-level hierarchy, the worker closes the job themselves after completing the work.
Conflict resolution behavior is configured separately from hierarchy but is applied consistently across both models. See Resolve Conflicts in Job Management for details.
Hierarchy Is Set at Group Registration
The hierarchy type is assigned when a portal group is registered with Job Management.
Once the group is registered, the hierarchy cannot be changed.
If your organization's workflow changes and a different hierarchy is needed, a new group must be registered.
All members of a registered group share the same hierarchy model. If different teams in your organization require different models, register them as separate groups.
What's Next
