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

# Organization Settings

Settings is the administrative hub of your ITOC360 workspace. Here, you can manage your organization's profile, invite new team members, verify domains, and track your subscription and invoices.

#### Accessing Settings

Open **Settings** in the left sidebar. Settings has these tabs: **Profile**, **Security**, **Notifications**, **Organization**, **Team**, **Billing** and **Preferences**.

This page covers the **Organization**, **Team** and **Billing** tabs.

#### 1. Organization

This tab holds the core identity of your workspace and your membership in it.

* **Organization logo** and **Organization name:** The name is shown in the sidebar and in invitations. Only the organization owner can change these; click **Save changes** after editing.
* **Transfer ownership:** The owner can make another member the owner of the organization.
* **Leave organization:** Removes you from the workspace. You lose access to its alerts, incidents and settings right away, and you're removed from its teams, schedules and escalation policies. To come back, someone has to invite you again. The owner can't leave; they need to transfer ownership or delete the organization first.
* **Delete organization:** Shown to the owner only. Removes the organization for everyone: members lose access and pending invitations are cancelled.
  * ***Warning:*** This action cannot be undone.

#### 2. Team

This tab lists your invitations and verified domains. To see who's already in the organization, go to **Management → Users**.

**Invitations**

The list shows everyone invited to join the organization, with their **Email**, **Role**, **Status**, who invited them (**Invited by**), when (**Invited**) and when the invitation **Expires**.

* **Invite members:** Enter each person's email address and pick a role. Use **Add another** to invite several people at once. You can also use the **Invite** button in the top bar. See [Roles & Permissions](https://docs.itoc360.com/users-and-access-management/roles-and-permissions.md) for who can invite.
* **Resend invitation** and **Revoke invitation:** Use the **⋯** menu on a pending or expired invitation.

**Verified domains**

Verified domains control who can join. Once you add a domain, only people with an email address on your verified domains can join. With no domains, anyone you invite can join.

* **Add domain:** Enter your company's domain name (e.g. `acmecorp.com`).
* **Edit domain** and **Remove domain:** Use the **⋯** menu on a domain. If you remove the last domain, anyone you invite can join again.

#### 3. Billing

The **Billing** tab shows your subscription inside the app.

* **Subscription:** Your current plan and its status, the price, the number of seats, the total, and when the plan renews or ends.
* **Usage limits:** How much of your plan you're using, such as seats, alert sources and escalation policies. To move to a smaller plan, your usage has to fit within its limits.
  * ***Pro Tip:*** Check your seats before inviting new members to make sure you have room.
* **Invoices:** Your past invoices, with their date, amount and status.

Users who can manage billing (Admins by default) also see these buttons under **Subscription**:

* **Change plan:** Switch to another plan or change the number of seats.
* **Manage billing:** Opens our secure customer portal (powered by Stripe), where payment methods and billing details are managed. If a payment has failed, this button reads **Update payment method**.
* **Cancel subscription:** Cancels the plan at the end of the current period. Until then, you can undo it with **Resume**.


---

# 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.itoc360.com/users-and-access-management/organization-settings.md?ask=<question>&goal=<user_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.
