Onboarding details
Request only missing information, scoped to an authorized platform.
After the platform is authorized, the assistant can discover and retrieve available fields with the MCP tools. These operations require an active, non-blacklisted authorization.
| Field | Source / handling |
|---|---|
first_name, last_name, email | Current profile, unless a platform-specific value exists |
phone | Optional; no new SMS verification requirement |
company, job_title | User-provided platform-specific values |
All are string fields. Tool metadata marks them optional; the platform may still need a value to finish its own onboarding. Phone is marked sensitive, not automatically verified. Never invent a value or infer that a stored phone was verified.
Request missing values
- Call
list_onboarding_fields({ projectId }). - Call
retrieve_onboarding_details({ projectId, fields }); inspectmissing. - Call
request_onboarding_detailsfor only the missing fields. - Ask the user to open My/Mobile Approvals and provide the values.
- Retrieve the details again after the user submits; do not assume a request means consent.
Equivalent pending requests are reused. Replies require the owning user; repeated completion is idempotent. Values are encrypted and bound to user, project and field. Revocation or blacklisting blocks further retrieval and replies.
Do not request passwords, payment details, government identifiers or unrelated data. Submitted values are limited to 500 characters each. Onboarding details are not automatically added to OIDC tokens or authorization webhooks.