Troubleshoot Hiring

Use the visible state, organization, and job assignment to narrow a Hiring problem before changing data.

Hiring is unavailable

Confirm that:

1. you are signed in to the intended Infra One account;
2. you are an organization member or admin, not a guest;
3. Hiring is enabled for your user account;
4. you selected the intended organization when Select an organization appeared.

An organization admin can verify membership. Infra One support or the platform owner must verify account-level Hiring availability.

A job action is missing

• Create requires organization-member or organization-admin access.
• Editing, publishing, or closing an existing job requires its creator, a hiring-manager or job-admin assignment, or organization-admin access. A reviewer or an unassigned organization member cannot make those changes.
• Opening rapid review requires organization job access, but its decision, rating, and note controls require reviewer access for the card’s job.
• Organization-wide status changes and Kanban moves require application-management access.
• For a synchronized job, Edit can render and open the form, but saving cannot update the synchronized job. Publish and close controls are disabled or reject the change. Make those changes in the connected applicant tracking system.

See Hiring permissions and states for the complete matrix.

A personal profile cannot be completed

Open My profile and check the guided section list. Skills appears after you select a target role that has a configured skills list. Hiring reports Cannot submit yet. Complete the remaining profile sections. and returns to the first incomplete section when required profile data is still missing.

Check the current caps when a section remains invalid: one to four specializations for roles that require them, 10 work-history entries, 10 education entries, and 10 skills; 60 characters for each name, 160 for contact email, 100 characters for relocation destinations, 200 for the short phrase, and 2,000 for each longer Share response. Engineering and design also require a portfolio URL.

The Hiring personal profile belongs to the signed-in platform user. If you are trying to continue a job application, use the separate Talent portal account instead.

An organization setting is absent

The Settings group includes only entries covered by your current organization capabilities. Ask an organization admin to confirm access to Team, Email templates, Scorecard templates, Notifications, or Connector settings. The current product does not enforce Limited as a Team-level view-only boundary: a Limited pool member can receive any per-job role. Removing a person from Team removes their assignment rows, but creator access is independent of those rows, and an organization member who creates another job is added back to the pool when necessary and receives job-admin access. Use organization membership controls when Hiring access must be prevented. Do not ask someone to share an ATS token; connector credentials must remain in an approved secret source.

A job is absent from the public board

Open the job in Hiring and check its state. Only Published jobs appear in public discovery. A Draft public detail is unavailable; direct Paused and Closed details remain readable but do not offer Apply. Draft, Paused, and Closed jobs do not offer a new or refreshed application wizard. A wizard already open in a browser does not re-check the job state at final submission, so closing a job is not an atomic cutoff for in-flight applicants.

Direct jobs cannot be paused or reopened locally. A closed direct job is also hidden from the organization’s Jobs page by the initial Status ≠ Closed filter; remove or edit that filter to find it. Change a synchronized job’s paused or closed state in its ATS.

If the job was synchronized, confirm its source state in the connected applicant tracking system.

An applicant view changed

Check whether the browser is using table or Kanban layout and whether the URL explicitly selected a layout. The explicit URL choice wins over a saved preference.

Older saved layouts receive Applied on once while preserving saved fields and widths. Hide the field again if it is not useful. A saved default sort still shows newest applications first.

Stage and Status disagree

For an imported application, Stage always reports the current ATS stage. Hiring’s shared Status follows the ATS only until a recruiter first changes the status or moves the card in Kanban. That first local move permanently transfers Status ownership to Hiring; it is not pushed back, and later syncs no longer overwrite it. If the local move was unintended, choose the intended Hiring status manually. Changing the ATS stage alone will not reclaim ownership.

A review stack is empty

Rapid review does not use the applicant browser’s search, status, or assessment filters. A single positive Job filter can open a job-scoped stack; otherwise Review opens the organization-wide stack. The stack is snapshotted when the visit begins.

Stack cleared means that visit has no card left to present; skipped cards can still be undecided. Refresh or reopen review to rebuild the snapshot. Undo only reopens the latest decision recorded during the current visit, and refresh clears that undo history. If a card is visible but its controls are disabled, you do not have review access for that card’s job.

AI chat has the wrong scope

Check the selector above the conversation. Choose All jobs for the whole organization or a job title for a focused question. Changing scope intentionally clears the selected open conversation. Jobs outside the current organization cannot be used as the scope.

The applicant cannot continue

Applicants sign in and apply on talent.infra.one, not in the authenticated Hiring workspace. Share the public job link, then use Troubleshoot Talent portal for sign-in or submission problems.