Interviews — redesign configuration guide
Customer administrator — nextgen / redesign
1. Prepare the form and campaign information
- Open Performance → Interviews [new] and choose Create campaign when ready to create a campaign.
- Select a published form from Forms [new], not a legacy Assessment questionnaire.
- Review the form's publication status, languages, required fields and employee/evaluator wording before using it.
The campaign editor separates basic information, timeline/phases and advanced settings. Campaigns have Draft, Not started, In progress, Completed and Archived lifecycle states. Form publication is independent: publishing a form does not activate a campaign.
2. Set dates, preparation mode and visibility
- Set the start/end dates and review the phase dates shown for the selected mode.
- Choose the preparation mode that matches the campaign sequence.
- Set employee/evaluator answer visibility and signature options for each phase.
- Save the step, then reopen the campaign settings and confirm the selected values.
| Setting | Choices / dependency | Effect and validation |
|---|---|---|
| Campaign dates | Start/end dates; phase dates depend on the selected mode. | The client validates timeline ordering. Verify dates and all displayed phase boundaries before activation; no universal duration is assumed. |
| Preparation mode | Parallel, evaluator-only, serialized and interview-only modes. | Determines which preparation phases exist and their order. Available interview steps depend on that configuration. |
| Employee can see evaluator answers | Boolean phase visibility setting. | Determines cross-participant visibility for the configured phase; question audience remains separate. |
| Evaluator can see employee answers | Independent boolean phase visibility setting. | Do not infer reciprocal visibility from the employee setting. |
| Signature required | Yes/No. | Controls signature requirements. This setting is locked when editing an in-progress campaign. |
| Allow employee signature refusal | Yes/No; depends on signature being required. Locked during in-progress editing. | Controls the refusal option; it is not a general right to edit signed content. |
| Show employees' answers | Advanced boolean setting; locked during in-progress editing. | Additional answer-visibility configuration. Check how it combines with phase visibility and participant reveal/hide options. |
The values saved for an existing campaign are authoritative. Defaults can depend on the form and platform configuration; do not copy an assumed default from another company.
3. Verify population, evaluators and administration
- Select the intended employees or groups, then review the resulting participant list.
- Assign the primary evaluator and, where enabled, any additional evaluator.
- Confirm the campaign owner and the people who can read, create, update, delete or delegate reviews.
- Reopen the assignment step and confirm that each participant has the intended evaluator and permissions.
Nextgen exposes separate read/create/update/delete campaign permissions and a delegation permission. Additional evaluator support has a two-evaluator limit and prevents duplicate active assignments; this does not establish legacy parity.
CampaignAccessChecker::checkAccess allows a super administrator or the campaign's creator/owner for operations that invoke that checker. It does not define every list/read/write policy. Confirm each intended administrator action and ordinary participant journey separately.
4. Activate and monitor
- Review the form, schedule, role assignments and signature/visibility rules together.
- Use the available campaign action to activate or publish when the setup is ready.
- Monitor each participant's preparation, answer sharing, completion and signature separately from campaign status.
- Open or generate the final report/PDF when available. If it is missing or outdated, inspect the output status and regenerate only after confirming answers and workflow state.
For changes after launch, assess answered content and locked settings first. Duplicate a form for a new version when appropriate, then configure a new campaign. A duplicate is not a migration of historical answers. No general automatic rollback is verified.
Platform-team reference — separate from customer setup
Legacy
The 2023 playbook lists interview campaign and questionnaire activation, annual-interview sub-navigation, optional signature comments, hiding the meeting-completed button and hiding scheduling. These describe one standard rollout. It also places the employee interview bell/navigation control under core settings. Confirm current tenant switches and role rights instead of enabling all options indiscriminately.
Nextgen
Verified in code: legacy shell app/config/neobrain/company/definitions.yml declares smr_campaigns and smr_settings_forms, requiring enable_new_neobrain_hybrid_platform plus their respective access roles. Forms also declare nextgen action scopes. Shell navigation access and API authorization are separate layers.
Nextgen workflows need scheduled execution; generated outputs and notifications can depend on asynchronous infrastructure. Optional questionnaire AI assistance has its own provider configuration. The platform team manages runtime configuration and delivery.
Validation and troubleshooting
| Problem | Administrator check |
|---|---|
| Interviews [new] missing | Hybrid activation, campaign navigation access, API permissions and workspace. |
| Expected questionnaire unavailable | Correct generation, publication, languages and access. |
| Preparation blocked | Assignment ownership, required answers, status/phase, dates and lock. |
| Settings disabled during editing | In-progress restrictions and dependencies such as signature refusal requiring signature. |
| Different answer visibility than expected | Question audience, phase rules, advanced settings and participant reveal/hide state. Test with the intended personas. |
| No notification / PDF | Templates, triggered events, worker execution and output status; do not promise delivery from configuration alone. |
Implementation references and deployment dependencies
Verified in code: legacy src/Company/InterviewBundle/Controller/DefaultController.php (newAction, changeEvalAction, unlocking/signature actions); app/config/neobrain/company/definitions.yml. Nextgen front src/modules/ModuleConfig/Campaigns/components/CreateCampaignSteps/{TimelinePhasesStep,AdvancedSettings}.vue; nextgen back src/Http/Api/Routing/V2/{review_campaign,user_review}.yaml, src/Infrastructure/Persistence/Service/ReviewCampaign/{CampaignAccessChecker,CampaignConfigurationKeyProvider}.php, src/Infrastructure/Persistence/Service/Review/UserReviewManager.php.
Product references: Playbook – Interviews, v11, 6 September 2023, and unlock guidance, v5, 21 May 2026. The playbook describes the legacy configuration model; unlock guidance covers completed and signed interviews.
Feature availability, notification delivery, migration and permission parity depend on tenant deployment. Ask the platform team about shared settings and the campaign administrator about campaign-specific access.
Last updated on 3 November 2026