> For the complete documentation index, see [llms.txt](https://docs.airops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.airops.com/your-workspace/settings/enterprise-onboarding.md). # Enterprise Onboarding Complete Enterprise onboarding, assign questions, and review suggested answers. Enterprise in-product onboarding brings the information your team needs to provide into one checklist. When AirOps configures onboarding for your workspace, the questions reflect your selected use cases. Overlapping questions appear once, even when the setup covers several use cases. ## How to Complete Onboarding 1. Open your workspace's onboarding checklist. 2. Open a question and provide the requested information. 3. Assign questions to teammates who own the relevant information or integration. 4. Review any suggested answers before accepting them. 5. Complete the remaining questions and review items shown in your checklist. Your AirOps team configures the combination of use cases for onboarding. Contact them if the checklist does not match the work your team plans to do. ## Assign Questions to Teammates Use **Assign to teammate** beside a question to choose a workspace member or someone with a pending invitation. Click **Assign** to save the assignment. You can return to the control to reassign the question or clear its assignment. If you have permission to invite users, you can invite a teammate from the assignment flow, choose their workspace role, and assign the question before they accept the invitation. Pending invitations show **Invite pending**. For example, assign a CMS setup question to the teammate who manages your publishing credentials, while another teammate completes the brand questions. ## Review Suggested Answers AirOps can use sales-call transcripts to suggest answers to questions already discussed with your team. Suggestions appear separately from the editable response and do not silently replace answers you have entered. * **Accept** applies the suggested answer to the question. * **Decline** dismisses the suggestion and leaves your response unchanged. Review a suggestion for accuracy before accepting it. You can also fill in the answer yourself. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.airops.com/your-workspace/settings/enterprise-onboarding.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.