Curated candidate groupings for nurture and pipeline-building (talent_pools). Embedded-masters candidates; deployed alone, materializes a thin candidate shell. Mirrors standalone talent-acquisition CRM products.
2. Entity summary
Name
Description
Talent Pools
Curated segment or pipeline of candidates kept warm for future roles (e.g. silver medallists, alumni, target-school grads, hard-to-fill skill clusters).
Candidates
Person known to the recruiting org, with or without an active application. Carries contact details, resume, tags, GDPR consent, and source. Distinct from Employee until hired.
flowchart TD
classDef master fill:#d4f4dd,stroke:#27ae60,color:#0b3d20;
classDef embedded_master fill:#fff4cc,stroke:#c79100,color:#5b4500;
talent_pools["Talent Pools"]
candidates["Candidates"]
talent_pools -->|"groups"| candidates
class talent_pools master;
class candidates embedded_master;
3. Entities catalog
#
data_object
role
mastered in
necessity
pattern flags
notes
1
talent_pools (Talent Pools)
master
-
required
-
-
2
candidates (Candidates)
embedded_master
ats-candidate-crm
required
personal_content
-
4. Aliases and industry synonyms
(no industry-scoped aliases or non-synonym alias types loaded for this scope; generic synonyms are omitted as common knowledge.)
5. Relationships
5.1 Intra-scope edges
from
verb
to
cardinality
kind
necessity
owner_side
notes
talent_pools
groups
candidates
many_to_many
reference
required
target
-
5.2 Built-in edges (users and other platform built-ins)
(no relationships against platform built-ins recorded for this scope.)
5.3 Cross-scope edges
from
verb
to
cardinality
necessity
notes
skill_profiles
feeds
candidates
one_to_many
optional
-
candidates
submits
job_applications
one_to_many
required
-
candidate_referrals
introduces
candidates
one_to_many
required
-
recruitment_sources
attributes
candidates
one_to_many
required
-
recruitment_agencies
sources
candidates
one_to_many
required
-
recruitment_events
attracts
candidates
one_to_many
required
-
candidates
becomes
employees
one_to_one
required
-
candidates
becomes pre-employee
pre_employees
one_to_one
required
-
6. Cross-domain context
6.1 Master consumers (other modules / domains that embed this scope’s masters)
6.2 Outbound handoffs (events this scope publishes)
(no outbound handoffs whose payload is in this scope.)
6.3 Inbound handoffs (events this scope reacts to)
(no inbound handoffs whose payload is in this scope.)
6.4 Master providers (modules / domains that own masters this scope embeds)
data_object
role here
necessity
canonical owner(s)
slice notes
candidates
embedded_master
required
ATS-CANDIDATE-CRM (ATS)
-
7. Lifecycle states (per touched entity)
candidates (Candidate)
This scope holds candidates as embedded_master; the canonical state machine is owned by ATS-CANDIDATE-CRM.
order
state_name
initial?
terminal?
requires_permission?
derived gate
description
1
prospect
✓
-
-
-
Person known to the recruiting org with no active application.
2
active
-
-
-
-
Candidate has at least one open application or is actively engaged.
3
hired
-
✓
✓
ats-candidate-crm:hire_candidate
Candidate accepted an offer and converted to employee.
4
do_not_hire
-
✓
✓
ats-candidate-crm:flag_do_not_hire
Candidate flagged as ineligible for future consideration; gated decision.
5
archived
-
✓
-
-
Candidate kept in the database but not active in any pipeline.
talent_pools (Talent Pool)
order
state_name
initial?
terminal?
requires_permission?
derived gate
description
1
active
✓
-
-
-
Pool is open for additions and nurture campaigns.
2
paused
-
-
-
-
Pool nurture is temporarily halted (off-season, budget freeze) but membership is retained.
3
archived
-
✓
-
-
Pool is closed; membership is retained for historical attribution but no further outreach occurs.
8. Permissions and business rules (derived)
8.1 Permissions
permission
tier
description
included in :admin?
ats-talent-pools:read
baseline-read
Read access to every entity in the module
✓
ats-talent-pools:manage
baseline-manage
Edit operational records
✓
ats-talent-pools:admin
baseline-admin
Edit reference data and inherit every workflow gate below
-
8.2 Business rules
(no flag-derived business rules.)
We use cookies
We use cookies to enhance your browsing experience and analyze our traffic. By clicking "Accept", you consent to our use of cookies.