> For the complete documentation index, see [llms.txt](https://docs.cloud-halo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloud-halo.io/workspaces/workspace-and-team-management.md).

# Workspace and team management

Workspaces separate customer, tenant, or business-unit data inside Cloud Halo.

Each workspace has its own members, Azure connections, billing state, budgets, alerts, recommendations, reports, and audit events.

## Workspace switcher

Use the workspace switcher in the top navigation to move between workspaces you can access.

Cloud Halo stores your active workspace preference. If a workspace is archived or removed, Cloud Halo falls back to another workspace you can access.

## Workspace settings

Workspace owners and administrators can update workspace details from settings.

Keep the workspace name clear and consistent, especially if your organisation manages multiple customers or Azure tenants.

## Team members

Workspace team management supports:

* Inviting members by email
* Assigning roles
* Changing roles
* Removing members
* Accepting invitations

Invited users should sign up or sign in with the same email address that received the invitation.

## Roles

Typical role expectations are:

* Owner: full workspace control, billing, archiving, role management, and transfer decisions
* Admin: operational management, Azure connections, alerts, reports, and team administration
* Member: day-to-day product usage where permitted
* Viewer: read-only access where permitted

Your organisation may define stricter internal rules for who can connect Azure or manage billing.

## Archive or delete workspace

Workspace owners can archive a workspace when it is no longer needed.

Before archiving, review:

* Active billing or trial state
* Azure connections and stored Service Principal credentials
* Open invitations
* Scheduled reports
* Team access

Archiving removes the workspace from normal switching and product workflows. Keep a remaining active workspace available for users who have access to more than one workspace.


---

# 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.cloud-halo.io/workspaces/workspace-and-team-management.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.