Talent Pool — configuration guide

Prepare access, pool information and the population maintained in each pool. This guide is for authorized administrators. Use functional for daily workflows and technical for API and processing details.

Talent Pool availability, data and actions depend on your organization’s setup and the permissions assigned to each role. Coordinate activation and platform services with the platform team before configuring pools.

Responsibility and generation matrix

Owner	Legacy	Redesign / nextgen
Project / platform team	Hybrid activation and legacy navigation rights expose the redesigned Talent Pool entry.	API authorization, employee data, rule processing and People Review synchronization infrastructure.
Customer administrator	No separate legacy Talent Pool maintenance screen was identified in the inspected paths. Legacy access controls are a prerequisite for the integrated entry.	Authorized pool creation/editing, manual membership and dynamic rules; role permissions administered through the applicable roles workflow.

A legacy navigation shell can open a nextgen screen. Do not create two independent pool catalogues or infer a legacy-to-nextgen data migration from that navigation alone.

Customer administrator — access preparation

1. Agree who needs to read pools, maintain their information, manage members and delete pools.
2. Ask the platform team to confirm the redesigned module's activation and navigation prerequisites.
3. Configure the required roles through Roles and permissions.
4. Use separate authorized roles for read, create, update, member-add, member-remove and delete duties. Menu access does not grant each action.
5. Prepare reliable employee records and rule fields before defining dynamic membership.

Permission	Effect in the checked feature
read-talent-pool	Lists pools, pool detail and membership through the API; included in the integrated navigation definition.
create-talent-pool	Creates a pool and controls frontend creation actions.
update-talent-pool	Changes pool information/rules. Also controls availability of Dynamic selection in the add-members modal.
delete-talent-pool	Deletes a pool; controls delete actions.
add-user-to-talent-pool	Adds manually selected members and exposes Add members.
remove-user-from-talent-pool	Removes eligible memberships and exposes removal selection/actions.

No universal default grant for these permissions was established. A job title such as HR or Manager does not establish an effective permission. Pool membership itself does not assign any of these rights.

Pool name and description

Create a pool from the list, or open a pool's information panel and choose Edit. Supply a clear name and, where useful, a description of its intended population and maintenance owner. Review the final action before saving and verify the reopened record afterward.

Field	Frontend behavior	Backend contract / scope
Name	Required; blank on creation; maximum 250 characters in the checked creation form.	titles is a required locale-keyed translation map, with a 255-character translation limit. Do not assume duplicate titles are forbidden.
Description	Optional; blank on creation; textarea limit 500 characters.	descriptions supports optional localized content, with a 1,000-character translation limit and HTML sanitization. The API limit does not override the lower UI limit.
Language	Creation sends text under the company locale, falling back to the frontend default locale.	Interface language and content-translation keys are separate. No full multilingual editor journey was verified here.
Owner / creation date	Presented as information rather than editable fields in the checked forms.	The UI uses creator information; API owner fields are separate read-only properties.
Pool status	No Active/Archived editor was verified in the inspected pool form.	The API defines Active = 1, Archived = 2; the entity defaults to Active. This is separate from candidate employee-status filtering.
Read-only	No editable switch in the inspected form.	Defaults false on the shared group entity. A read-only pool rejects updates, deletion and membership changes.

Do not change the interface language expecting pool content to translate automatically. Keep tenant-authored titles and descriptions appropriate for the intended audience.

After saving, reopen the pool and confirm its name and description. Manage pool information separately from its membership; removing a member does not remove the pool.

Manual membership

Use the pool's Add members action and Manual selection. Search/filter candidates, select the intended employees and review the selected-users panel before confirming. The search field, Active/Inactive filter and multi-manager selector filter candidates; they are not persistent membership rules.

Selection checkboxes apply to the current candidate page. The selected-users panel can retain selections from other pages. Before saving, review the entire panel rather than relying on the visible candidate rows. The frontend excludes already-loaded members locally; final server handling remains authoritative.

To remove a manual member, use the member removal workflow. Review linked People Review campaigns before changing population. No automatic undo of downstream campaign effects was verified.

Dynamic membership

Dynamic selection requires the update permission in addition to access to the add-members workflow. It uses the shared rule builder in talent_pool context, with a preview panel.

1. Confirm that employee attributes used by the rule are complete and maintained by an authoritative process.
2. Define the field, supported operator and correctly typed value for each condition.
3. Review the AND/OR grouping and resulting preview. Fields and operators depend on your workspace’s rule configuration; ask the platform owner which choices are available.
4. Review manual selections too: a single modal session can submit manual additions and rule changes.
5. Save only the reviewed population definition, then verify the eventual member list and linked campaign participants.

Setting / control	Meaning and validation
Field	Chooses an employee attribute supplied by the configured rule builder. Ask the platform owner which fields and operators are available in your workspace.
Operator	Defines the comparison for that field. Use the allowed operators supplied by the builder, not a guessed free-text operator.
Value	Must match the field type. The current converter handles integer and existence values specially and omits conditions with empty/null/undefined values.
AND / OR expression	Combines conditions inside the expression. Root expressions in the API rules array are AND. Multiple visible sections must not automatically be described as OR.
Preview	Helps inspect the prospective population. It is not proof that background persistence or campaign synchronization has completed.
Empty rules	The current save converter can submit an empty rules array. The backend processing path removes rule-created memberships when rules become empty. Manual memberships require separate consideration.

The modal validates conditional rules when Dynamic selection is active. Review the current saved definition and preview before confirming a change. If you switch between Dynamic selection and Manual selection, review both the selected employees and the rule changes before saving.

Illustrative example: an approved rule on an available organizational attribute can maintain a pool as employee data changes. This is a population rule, not an AI talent score or a recommendation to make an employment decision.

Project / platform-team reference

The legacy feature definition for smr_talent_pool declares:

Dependency	Checked definition
Hybrid activation	enable_new_neobrain_hybrid_platform
Legacy navigation right	smr_talent_pool_access
Redesigned scope	read-talent-pool
Admin destination	admin/modules/talent-pool

Verified in code: legacy app/config/neobrain/company/definitions.yml, CompanyNavigationExtension::getSmrTalentPoolFeature, and nextgen frontend routes. These definitions are platform prerequisites, not instructions for customer administrators to change server configuration.

Documented in Confluence: the SMR playbook, v3, 24 September 2026, describes hybrid activation, unified navigation and separate legacy menu rights/redesigned action permissions. Its recommended Admin/HR access is deployment guidance rather than a code default.

The platform must operate the group-rule message publisher/consumer and People Review synchronization consumers. Rule changes can complete later than the save request. No runtime service status, processing latency or retry policy was verified. No direct AIHub dependency was identified in the traced pool workflow.

Review membership changes

1. Confirm the pool’s purpose, owner, employee data source and access roles before changing its population.
2. For manual changes, review the complete selected-members panel and the confirmation count. Reopen the pool to check the member list afterward.
3. For dynamic changes, review the rule, preview and field values before saving. Membership updates run asynchronously; reopen the pool later to check the resulting population.
4. Before changing or removing members from a linked pool, coordinate with the People Review campaign owner and check the campaign’s participant list after synchronization.
5. Before deleting a pool or clearing its rules, follow your organization’s retention and change-approval process. A later text or rule change does not guarantee that already-synchronized campaign effects are undone.

Symptom	Check
Entry hidden	Legacy hybrid switch/menu right and redesigned read permission.
Dynamic selection absent	Update permission and access to the add-members modal.
Missing candidates	Candidate filters, employee data, effective user visibility and already-loaded member exclusion. Exact population authorization must be validated for the tenant.
Cannot remove a member	Rule-created membership must be changed through its rule; read-only pools reject attachment/detachment.
Rules saved but members stale	Background rule consumption, field values, rule validation and member-count refresh.
Error after partial change	Manual additions and rule updates are separate changes. Refresh the pool before retrying; an error does not necessarily undo an earlier successful change.

Platform team handoff

Ask the platform team to manage the hybrid activation, legacy navigation right, redesigned module permissions, employee-data availability, rule-processing service and People Review synchronization. These are workspace dependencies, not customer-level pool settings. For implementation details, see the technical guide.