Update the onboarding settings
Change the company onboarding settings — the steps every onboarding includes, their owners, due dates and scheduling, the default ticket owner, priority and subscribers, and the Primo AI agent options. Only the fields you send are changed; everything else keeps its stored value, so send just what the user asked to change rather than the whole object. defaultTaskOwner, owner and defaultTaskSubscribers take a Primo employee id (type EMPLOYEE) or the Clerk user id of an admin with no employee record (type EXTERNAL_ADMIN) — look the person up with getEmployees first; a person who does not belong to the company is refused. Sending null clears a field. The new settings apply to onboardings created afterwards, never to the ones already open. Call getOnboardingSettings first so you can tell the user what the change replaces.
Authorizations
Use your Primo API key in the Authorization header as Bearer <API_KEY>.
Body
Whether the professional email step is part of every onboarding.
Whether the SaaS provisioning step is part of every onboarding.
Whether the equipment step is part of every onboarding.
Whether the Primo AI agent drives the equipment step instead of a human owner.
Whether the Primo AI agent is put on every onboarding ticket.
Whether ordered devices are enrolled in MDM automatically.
Whether Primo suggests SaaS applications for the joiner.
CREATE provisions a new address, EXISTING reuses the one the HRIS carries.
CREATE, EXISTING USE_AS_IS, MANUAL_CONFIRMATION Steps Primo executes without waiting for an admin to validate them.
EMPLOYEE_INFORMATION, EMPLOYEE_EMAIL, EMPLOYEE_PROVISIONING, EMPLOYEE_EQUIPMENT Assignee of the onboarding ticket and of every step with no owner of its own. Null means unassigned.
LOW, MEDIUM, HIGH Per-step overrides of owner, due date and scheduling.
Response
Whether the professional email step is part of every onboarding.
Whether the SaaS provisioning step is part of every onboarding.
Whether the equipment step is part of every onboarding.
Whether the Primo AI agent drives the equipment step instead of a human owner.
Whether the Primo AI agent is put on every onboarding ticket.
Whether ordered devices are enrolled in MDM automatically.
Whether Primo suggests SaaS applications for the joiner.
CREATE provisions a new address, EXISTING reuses the one the HRIS carries.
CREATE, EXISTING Steps Primo executes without waiting for an admin to validate them.
EMPLOYEE_INFORMATION, EMPLOYEE_EMAIL, EMPLOYEE_PROVISIONING, EMPLOYEE_EQUIPMENT Per-step overrides of owner, due date and scheduling.
USE_AS_IS, MANUAL_CONFIRMATION Assignee of the onboarding ticket and of every step with no owner of its own. Null means unassigned.
LOW, MEDIUM, HIGH