--- title: Core concepts description: The vocabulary that runs through the rest of the docs — accounts, organizations, members, jobs, candidates, roster, goals, rewards. product: platform audience: both voice_pillar: coordinate --- # Core concepts The vocabulary that runs through the rest of the docs. Skim this once and the rest of the site reads faster. ## The operational problem Workforce tools usually invent their own dictionaries. Hiring lives in one system, scheduling in another, recognition in a third. The same person is a "candidate" in one tool, a "team member" in the next, and an "employee ID" in the third — with no shared model tying it together. Operators end up translating between systems instead of running their floor. ## How Array HQ solves it Array HQ uses a single, consistent set of nouns across recruiting, operations, and rewards. The same person flows from candidate to team member to roster line without changing identity. The same organization powers hiring in //Recruiting and day-to-day operations in //Ops. The vocabulary below is the model. ## How it works ### Account and organization An **account** is the top-level entity that owns billing, members, and data. An **organization** lives inside an account and represents a separate operating unit — a brand, a region, or a business line — when one account needs more than one workspace. ### Members and roles **Members** are people with access to Array HQ. Every member has one or more **roles** that control what they can see and do — Admin, Ops, or Recruiting. Organization access is assigned separately. ### Jobs and candidates A **job** is a role you're hiring for at an organization. A **candidate** is a person being evaluated against that job. **Screening** is the staged evaluation that decides which candidates become hires. ### Roster The **roster** is the active workforce at an organization. Once a candidate is hired they appear on the roster as a **team member**. ### Talent **Talent** is the umbrella word for the people your operation runs on — candidates being evaluated, team members on the roster, and the frontline experience they share. When the docs say the **My Array HQ app** or **Talent and Team Members**, they mean the worker-facing side of the platform, as opposed to the operator portal. ### Goals and rewards **Goals** are the operational behaviors you want to drive — speed, attendance, output, compliance. A **reward** is something a team member can redeem points for — a meal credit, a fuel card, store gear — drawn from a catalog your organization curates. **Points** are the currency team members earn against goals and redeem for rewards. Rewards are tied to goals: points are only earned by hitting them. ### AI Agents **AI Agents** are the autonomous workers inside Array HQ. They source candidates, screen applicants, surface roster issues, and post status updates without manual prompting. Each agent has a defined job, runs continuously, and reports its work into the same system humans do. ## Key terms | Term | Meaning | |---|---| | Account | Top-level entity that owns billing and data. | | Organization | A workspace inside an account. | | Member | A person with access to Array HQ. | | Roles | The permission sets assigned to a member. | | Job | A role you're hiring for at an organization. | | Candidate | A person being evaluated for a job. | | Screening | The staged evaluation of candidates for a job. | | Roster | The active workforce at an organization. | | Team Member | A person currently on the roster. | | Talent | The umbrella term for candidates and team members. | | Goal | An operational behavior tied to rewards. | | Reward | Something a team member redeems points for, from the catalog. | | Points | The currency team members earn and redeem. | | AI Agent | An autonomous worker inside the platform. | ## Related - [Account & access](account-access.md) - [Accounts and Organizations](../platform/accounts-organizations.md) - [AI Agents](../platform/ai-agents.md) - [Glossary](../resources/glossary.md) — operator terms used across the docs