> For the complete documentation index, see [llms.txt](https://docs.yoov.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yoov.com/yoov-work/admin-management/company-team-settings.md).

# Company/Team Settings

## 1. Contact Settings 

* The system allows you to set permissions to view other employees' address books.
* Operation steps: \
  \[Settings] > \[Client-end Management] > \[Contact Setting]

<figure><img src="/files/VL5l6ZVgoQRT4VJjzadL" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/Num2xBFejal3je9CePdZ" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/FBi5HdfSkRb9aGRDiF24" alt=""><figcaption></figcaption></figure>

## 2. Modify Company/Team Information&#x20;

* The system has the function of modifying company/team information. Allows administrators to transfer account ownership, edit, and log out of the business for the company.
* Operation steps: \
  \[User Center] > \[Organization] > \[Information] > \[Edit]
* Whenever the company's information changes, the company information can also be edited here.

<figure><img src="/files/zvw3JPCrKLGKZuOtTAtq" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/R5S1nx6vazLdflvO4Zf2" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/X1foxBAw8Sq1FYkorkDm" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/mJ5zfiIZMEYSt16lNneM" alt=""><figcaption></figcaption></figure>

## 3. Contract Company&#x20;

* The main company can create multiple contract companies with labor contract relationships and manage in the same account.
* Operation steps: \
  \[Department] > \[Contract Company]
* Click to add a contract company
* Fill in the information of the contract company that needs to be added, and click Confirm to complete.

<figure><img src="/files/ZHFLYTNRXBNrIZyNFeYi" alt=""><figcaption></figcaption></figure>

<div align="left"><figure><img src="/files/AtMGHkbQDRGZs01sQhIl" alt="" width="374"><figcaption></figcaption></figure></div>

## 4. Transfer of Ownership&#x20;

* When the administrator leaves or no longer needs to handle the system, the administrator can select employees to become new administrators in the transfer administrator to maintain system operations.
* Please note: Only company holders can see and use this feature
* Operation steps: \
  \[User Center] > \[Organization] > \[Information]> \[Transfer Ownership]

<figure><img src="/files/ERoPhe1lfE6lFs3JLCmS" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/WwPweSgHf2qcr82cHgzt" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/TJulQXYf8AktOkLkg9Li" alt=""><figcaption></figcaption></figure>

<div align="left"><figure><img src="/files/P63qLMotjA8TzlVOT3Uy" alt="" width="295"><figcaption></figcaption></figure></div>

## 5. Cancellation of Company

* If the company no longer uses the YOOV WORK system, it can log out of the account here. After logging out of the company, the user will not be able to view or manage this company/team data.
* Please note: Only Company holders can see and use this feature
* Operation steps: \
  \[User Center] > \[Organization] > \[Information] > \[Dissolve Company]

<figure><img src="/files/TufEsuHIRuXuIM1uYf3l" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/HfsqOEbSE2DNt0aWv5IQ" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/4q1tGZenztotpgQP1rVb" alt=""><figcaption></figcaption></figure>

<div align="left"><figure><img src="/files/7A2FXqUF2vGBBwLOWR9M" alt="" width="290"><figcaption></figcaption></figure></div>

## 6. Technical support&#x20;

* Administrators can enable technical support and provide specific \[codes] to YOOV staff to help you solve problems.
* Operation steps: \
  \[User Center] > \[Organization] > \[Information] > Technical Support \[codes]&#x20;

<figure><img src="/files/GsxbqlxC9BQb20q5vyeY" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/ubbAEoCet8SwEb0stWgr" alt=""><figcaption></figcaption></figure>

## 7. APP Cover Management&#x20;

* Operation steps: \
  \[User Center] > \[Organization] > \[Banner] > \[Add Cover]

<figure><img src="/files/N8rumpSPokwGAa4Bna6R" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/OujQsidRESyyJrvGoL0j" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/ljyRLiavjmp4Raa2ee3M" alt=""><figcaption></figcaption></figure>

## 8. Operation Log

* The system can be operated by more than one administrator, and the administrator can search for the change records of all administrators in the operation record.
* The operation time, administrator name, IP address, operation object, type and specific operation are displayed in detail for easy query.
* Operation steps: \
  \[User Center] > \[Security] > \[Operation Log]

<figure><img src="/files/38Lb36EKzSZcVw2u6wWG" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/O0yNWm42EcRoh0JA88LG" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.yoov.com/yoov-work/admin-management/company-team-settings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.