> For the complete documentation index, see [llms.txt](https://docs.coreway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coreway.com/coreway-hr/create-a-company-team.md).
# Create a Company/ Team
Create a new Company/ Team for the first time
**Operation steps:**
1. Please click "Create Company/Team."
2. Enter the create team page, select the industry, and click "Next."
3. Fill in "Company/Team Name," select "Country/Region," and click "Complete."
4. Enter the page to select applications to activate, choose WORK, click "Activate Now," and enter the YOOV homepage.
5. After activation, you can see a beginner's guide pop-up on the homepage. Follow the four steps in the pop-up to complete the basic configuration: Organization Structure, Application Backend, Enterprise Applications, Subscription Management. Each step will also have corresponding guidance to help you complete each setup.
6. After finishing each step, the task status will be checked as completed. If you close the window and want to view it again, click "Beginner's Guide" in the lower right corner. The beginner's guide will disappear from the lower right corner of the homepage once all steps are completed.
---
# 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.coreway.com/coreway-hr/create-a-company-team.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.
