Get the onboarding settings
Return the company onboarding settings: which steps (email, SaaS provisioning, equipment) every onboarding includes, who owns each of them and when they are due, the scheduling of each step, the default ticket owner, priority and subscribers, and whether the Primo AI agent is put on onboarding tickets or drives the equipment step. These settings shape every onboarding created afterwards, not the ones already open. Read this before updateOnboardingSettings so you can report what changes. For the settings of one onboarding already in flight, use getOnboarding instead.
Authorizations
Use your Primo API key in the Authorization header as Bearer <API_KEY>.
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