# Organization Page

## Purpose of This Page <a href="#purpose-of-this-page" id="purpose-of-this-page"></a>

The Organization page is designed to help you manage the internal and external structure of your company within solarVis. It allows administrators to define organizational units, assign responsibilities, and control access at different levels of the organization.

Using this page, you can:

* Structure how users and projects are distributed across the company
* Define clear ownership and accountability
* Manage access rights and visibility based on organizational roles

This page functions as the **top-level organizational layer**, linking all operational entities, users, projects, and permissions under a unified structure.

## What You Can Do Here <a href="#what-you-can-do-here" id="what-you-can-do-here"></a>

From the Organization page, you can perform the following actions:

* View all organizational units in a single, centralized overview
* Navigate easily between **Partners**, **Teams**, and **Headquarters**
* Create, edit, and manage partner organizations and internal teams
* Access detailed information for each organizational unit, including users and projects
* Monitor how projects and users are distributed across the organization

## Page Structure <a href="#page-structure" id="page-structure"></a>

The Organization page is divided into three main tabs, each representing a different level of the organizational hierarchy:

### Partners <a href="#partners" id="partners"></a>

The Partners tab lists all partner organizations connected to your company. Partners typically represent branches, dealers, resellers, or external organizations that operate under your main company.

Each partner:

* Can have its own users and projects
* Is linked to the headquarters for oversight and governance

### Teams <a href="#teams" id="teams"></a>

The Teams tab displays internal teams used to organize users within your company. Teams are ideal for structuring internal operations such as sales, engineering, or project management.

Teams:

* Group users within the company
* Help assign projects and responsibilities internally
* Improve organization and clarity within the headquarters

> Teams do not function as independent organizations but as internal groupings under the main company.

### Headquarters <a href="#headquarters" id="headquarters"></a>

The Headquarters represents the main company entity and sits at the top of the organizational hierarchy.

The headquarters:

* Owns all organizational data
* Manages global users and permissions
* Has full visibility across partners and teams
* Receives transferred projects when partners or teams are suspended or removed

## Summary <a href="#summary" id="summary"></a>

The Organization page defines how your company is structured in solarVis.

By organizing users and projects under partners, teams, and the headquarters, you can maintain clear ownership, control access levels, and scale operations in a structured way.

This structured approach helps maintain operational clarity while supporting growth and collaboration across multiple organizational levels.

***

## Related Pages <a href="#related-articles" id="related-articles"></a>

* [Partners Page](/configuration/organization-page/partners.md)
* [Teams Page](/configuration/organization-page/teams.md)
* [Headquarters Page](/configuration/organization-page/headquarters.md)

If you encounter any issues, [feel free to contact us.](https://www.solarvis.co/en/company/contact)


---

# Agent Instructions: 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:

```
GET https://docs.solarvis.co/configuration/organization-page.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.