Manager, Practitioner, and Superuser Roles

This one‑page guide explains the difference between Manager, Practitioner, and Superuser roles in ADP Workforce Manager so departments receive the right level of access while protecting payroll accuracy, system stability, and compliance.

Purpose 

This one‑page guide explains the difference between Manager, Practitioner, and Superuser roles in ADP Workforce Manager so departments receive the right level of access while protecting payroll accuracy, system stability, and compliance. 

High‑level distinction 

• Manager → Supervises people. Reviews and approves time for their own team. 

• Practitioner → Runs operations. Manages time & attendance across teams or departments. 

• Superuser → Owns the system. Configures rules, security, and structure for the entire organization. 

Think people leadership vs operational administration vs system ownership. 

 

Manager Role 

What Managers can do:

Managers are responsible for oversight of their direct (and, if configured, indirect) reports: 

• Review and approve employee timecards 

• Address exceptions (missed punches, overtime alerts) 

• View schedules and staffing for their team 

• Make limited timecard edits (if enabled) 

• Run team‑level reports 

What Managers cannot do:

• Access employees outside their reporting hierarchy 

• Configure schedules, pay rules, or accrual policies 

• Run cross‑department or system‑wide reports 

• Manage users, roles, or security 

• Perform payroll or system administration tasks 

Who should be a Manager:

• Department managers 

• Shift supervisors 

• Team leads with time approval responsibility 

 

Practitioner Role 

What Practitioners can do:

Practitioners support the organization operationally and have broader access than Managers: 

• Edit and correct timecards for multiple teams 

• Manage schedules, shifts, and coverage 

• Resolve escalated timekeeping issues 

• Run cross‑department and detailed reports 

• Support managers and employees with Workforce Manager usage 

What Practitioners cannot do:

• Change system configuration or security roles 

• Modify pay rules or accrual logic 

• Manage integrations or global system settings 

(These responsibilities remain with Superusers.) 

Who should be a Practitioner:

• Payroll staff 

• HR Operations 

• Time & attendance administrators 

• Central workforce management teams 

 

Superuser Role 

What Superusers can do:

Superusers have the highest level of access and are responsible for system design, security, and governance: 

• Create and manage users, roles, and permissions 

• Configure pay rules, work rules, and accrual policies 

• Maintain organizational structure (locations, departments, job codes) 

• Configure timekeeping rules, schedules, and approval workflows 

• Manage integrations and global system settings 

• Resolve system‑level issues that other roles cannot 

What Superusers should not do:

• Perform routine daily timecard approvals unless required 

• Be assigned broadly across departments 

Superuser access should be highly restricted to reduce payroll risk and prevent unintended system changes. 

Who should be a Superuser:

• HRIS system owners 

• Senior Payroll or HR leaders 

• IT / HRIS administrators supporting integrations and audits 

 

Side‑by‑side comparison 

Area	Manager	Practitioner	Superuser
Scope of access	Own team	Multiple teams/departments	Entire organization
Approve timecards	✅ Yes	✅ Yes	✅ Yes
Edit timecards	Limited	Broad	Broad
Scheduling	View / limited	Manage	Configure
Reporting	Team‑level	Cross‑organization	System‑wide
System configuration	❌ No	❌ No	✅ Yes
Security & roles	❌ No	❌ No	✅ Yes
Primary focus	Supervision	Operations	System ownership

 

Recommended best practice 

• Managers approve and oversee their people 

• Practitioners manage day‑to‑day workforce operations and support managers 

• Superusers configure, secure, and govern the system 

• Avoid assigning multiple roles unless there is a documented business need 

Clear separation of roles: 

• Reduces payroll and compliance risk 

• Prevents over‑permissioning 

• Keeps accountability and audit trails clear