What Are Adobe Workfront Terms for HR? Essential Glossary & Automation Reference

Adobe Workfront terminology is the operating language of structured HR automation. Before your team can configure requisition workflows, build compliant approval chains, or connect your ATS to an onboarding project template, everyone involved must speak the same language. This glossary defines every core Workfront term HR and recruiting professionals encounter—explained in the context of talent acquisition, onboarding, compliance, and performance management. It is a prerequisite for implementing the HR automation with Adobe Workfront for recruiting approach that separates strategic HR functions from administrative ones.

Use this reference when scoping a Workfront implementation, training your team, or auditing an existing configuration for gaps.

Project

A Project in Adobe Workfront™ is the primary container for a planned set of tasks designed to achieve a specific HR outcome.

For HR professionals, a project represents any bounded initiative: a new talent acquisition campaign, an annual performance review cycle, a policy rollout, or an onboarding cohort. Projects define scope, assign resources, set deadlines, and track progress across all contributing team members.

The strategic value of the project object is automation: Workfront™ projects can be triggered automatically—when a requisition is approved in an ATS, for example—pre-populated with a standardized task list, assigned to the correct recruiter and coordinator, and given a deadline calculated from the target start date. This eliminates manual project creation and guarantees consistency across every hiring initiative. Asana’s Anatomy of Work research consistently finds that a substantial share of knowledge worker time is lost to status-chasing and duplicated coordination tasks; auto-generated projects eliminate both.

Task

A Task is a specific, assignable action step within a Workfront™ Project.

Tasks are the granular units that move an HR initiative forward: “Draft offer letter,” “Schedule panel interview,” “Complete background check authorization,” “Provision system access,” or “Send 30-day check-in survey.” Each task carries an owner, a start date, a due date, and optional predecessor relationships that enforce sequencing.

Automating task creation—generating a full onboarding task list based on a new hire’s department, location, and role level—ensures that no step is skipped and that accountability is established from day one. HR teams that automate employee onboarding with Adobe Workfront report dramatically shorter time-to-productivity and fewer onboarding errors.

Issue

An Issue in Workfront™ is an unplanned problem, exception, or request that surfaces during a project or task.

In HR workflows, issues capture what wasn’t anticipated in the original project plan: a candidate withdrawal that requires pipeline updates, a hiring manager requesting additional interview slots outside the scheduled window, a background check vendor error, or a budget exception that needs executive review. Issues are logged, assigned, prioritized, and tracked to resolution—preventing disruptions from becoming invisible gaps.

Automation integrations can convert external events directly into Workfront™ issues. A candidate status change in an ATS can instantly create an issue in the corresponding hiring project, alert the recruiter, and trigger a notification to the hiring manager—eliminating the email chain that would otherwise delay action by hours or days.

Request Queue

A Request Queue is a centralized intake point for collecting structured work requests from any stakeholder.

For HR, the request queue replaces ad-hoc email threads as the intake channel for role requisitions, HR support tickets, training requests, policy clarification questions, and accommodation requests. Requestors submit a form; HR receives structured, complete, routable data. Requests are triaged, prioritized, and converted into projects or tasks—with status visibility returned automatically to the requestor.

The request queue is the foundation of scalable HR service delivery. Without it, every intake is a negotiation. With it, every request follows the same structured path, captures all required data at the point of submission, and enters the workflow without manual reformatting. Teams looking to streamline their recruitment funnel with Workfront automation typically implement request queues as their first configuration milestone.

Portfolio

A Portfolio in Workfront™ groups multiple related projects so leaders can evaluate them collectively.

For HR, a portfolio might contain all active hiring campaigns, all projects associated with a specific business unit’s talent needs, or all compliance-related HR initiatives for a fiscal year. Portfolio-level views show aggregate resource utilization, total budget consumption, and strategic alignment scores across all contained projects simultaneously.

The portfolio layer enables the resource trade-off decisions that define strategic HR: when two hiring campaigns compete for the same recruiter’s capacity, portfolio data shows which initiative carries higher business priority—making the decision data-driven rather than political.

Program

A Program is a grouping layer that sits between a Portfolio and individual Projects.

Programs cluster related projects under a shared initiative without merging them. An HR example: a “Q3 Engineering Hiring Initiative” program might contain three separate projects—one for senior engineers, one for mid-level engineers, and one for engineering management—each with distinct timelines and owners, but all reportable together under the program umbrella. Programs make it possible to manage related work at the right altitude without losing project-level granularity.

Custom Form

A Custom Form is a configurable data-capture layer that can be attached to any Workfront™ object: project, task, issue, request, or user profile.

HR teams use custom forms to capture metadata that Workfront’s native fields don’t include: job grade, cost center, FLSA classification, hiring manager approval chain, EEOC category, relocation eligibility, or background check vendor preference. Data entered in a custom form at intake flows automatically into downstream tasks, reports, and dashboards—eliminating the need to chase information after a project is already in motion.

Custom form design is the highest-leverage configuration decision in any Workfront HR deployment. Every field you fail to capture at intake becomes a manual follow-up later. The full post on how Adobe Workfront custom forms transform HR processes covers the design principles in depth.

Approval Process

An Approval Process is a defined sequence of reviewers who must sign off before a Workfront™ object advances to its next stage.

In HR workflows, approval processes enforce compliance checkpoints without requiring manual follow-up from the process owner. A requisition approval process routes a new headcount request to the hiring manager, then the department head, then Finance—in sequence, with automatic escalation if a reviewer misses the deadline. An offer letter approval process routes the letter to Legal and then to the VP of HR before the recruiter is authorized to send it.

Approval processes are among the most under-configured features in HR Workfront™ deployments. Teams that build approval processes into every high-stakes HR checkpoint—requisitions, offers, policy changes, headcount exceptions—generate audit trails that hold up under compliance review. Teams that skip this configuration end up rebuilding compliance evidence manually after the fact. The satellite on automating ironclad HR compliance with Adobe Workfront covers approval architecture in detail.

Predecessor

A Predecessor is a task that must reach a specified completion state before a dependent task can begin.

Predecessors enforce sequencing automatically. In an onboarding workflow, “Background check cleared” is a predecessor to “Issue system credentials”—preventing IT from provisioning access before the check is complete. In a recruiting workflow, “Offer letter approved” is a predecessor to “Send offer to candidate.” Predecessors eliminate the class of errors that occur when downstream tasks are started out of sequence because no one checked whether the upstream step was actually done.

Automation Rules

Automation Rules are the native if-then logic engine inside Workfront™ that triggers defined actions in response to specified conditions—without human intervention.

When a task status changes to “Complete,” an automation rule can update the parent project’s percent-complete, notify the next task owner, and move the project to the next phase status simultaneously. When a request is submitted through a queue, an automation rule can assign it to the correct HR specialist based on the request type, set a due date based on SLA, and send a confirmation to the requestor.

Automation Rules handle the deterministic, repetitive coordination work that consumes recruiter and HR coordinator time. McKinsey Global Institute research has consistently identified structured, rule-based coordination tasks as the category of knowledge work most immediately automatable—and Workfront’s™ native automation layer targets exactly this category.

Workfront Fusion

Workfront Fusion™ is Adobe’s native integration and scenario-automation layer that connects Workfront™ to external systems through multi-step automated workflows.

While Automation Rules operate within Workfront’s own objects, Fusion™ scenarios cross system boundaries. An HR Fusion™ scenario might watch an ATS for status changes, pull the candidate and role data when a trigger condition is met, create a Workfront™ project from a template, populate custom form fields with ATS data, assign tasks by department, and send a Slack notification to the hiring team—all in a single automated sequence, triggered without human initiation.

Fusion™ is the integration layer that eliminates the manual data transcription errors HR teams experience when copying candidate information between systems. Parseur’s Manual Data Entry Report estimates the fully loaded annual cost of a data-entry-focused employee at over $28,500—and that figure doesn’t account for the downstream cost of the errors themselves. David, an HR manager in mid-market manufacturing, experienced this directly when an ATS-to-HRIS transcription error turned a $103K offer into a $130K payroll entry—a $27K mistake that ended in the employee’s resignation.

Template

A Template in Workfront™ is a reusable project structure—including tasks, assignments, durations, predecessors, and custom form fields—that can be instantiated into a live project at any time.

For HR, templates encode institutional knowledge. A “Software Engineer Hiring” template contains every task required to source, screen, interview, evaluate, offer, and onboard a software engineer—pre-sequenced, pre-assigned by role, and pre-configured with the correct custom form fields. When a new requisition is approved, the template fires and a complete, consistent project appears. Templates are how HR teams scale: the process is defined once, encoded once, and executed consistently across every subsequent hire.

Report

A Report in Workfront™ is a configurable query that surfaces structured data from any set of Workfront objects based on defined filters, groupings, and columns.

HR-specific reports include: open requisitions by hiring manager, time-in-stage by role type, overdue onboarding tasks by department, offer acceptance rate by recruiter, and compliance checkpoint completion rate by project. Reports are the foundation of data-driven HR management. They also feed measuring HR strategy and efficiency ROI with Adobe Workfront—the practice of translating operational data into business-level outcomes that justify HR’s resource claims.

Dashboard

A Dashboard is a Workfront™ canvas that assembles multiple reports, calendars, and external pages into a single consolidated view.

HR leaders use dashboards to monitor all active hiring campaigns, track onboarding completion rates, surface at-risk projects before they miss deadlines, and review compliance checkpoint status across all active initiatives—without opening individual projects. Dashboards are the visibility layer that makes Workfront™ a management tool rather than a task tracker.

Milestone

A Milestone is a significant checkpoint within a project that marks the completion of a major phase or deliverable.

In an HR context, milestones mark phase transitions: “Candidate Shortlist Finalized,” “Offer Extended,” “Start Date Confirmed,” “Day 30 Check-in Complete.” Milestones are visible in project timelines and portfolio views, giving HR leaders a quick signal of where each initiative stands without reviewing every individual task. They are also common trigger points for automation: reaching the “Offer Extended” milestone can automatically initiate the pre-boarding checklist.

Resource Management

Resource Management in Workfront™ is the set of tools—Workload Balancer, Resource Planner, and utilization reports—that show how team capacity is allocated across all active work.

For HR leaders, resource management answers the questions that most HR teams answer by gut feel: Which recruiters are over-allocated? Which coordinators have capacity to absorb a new initiative? If we open three new requisitions this quarter, what is the realistic impact on time-to-fill given current team capacity? Gartner’s talent management research consistently identifies resource visibility as a top gap in HR operating models. Workfront’s™ resource management layer closes that gap with structured data.