> For the complete documentation index, see [llms.txt](https://btwb.gitbook.io/btwb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://btwb.gitbook.io/btwb/admin/gym-setup/editing-organization-details.md).

# Editing Organization Details

This article covers the Edit Details page — your organization's name, handle, email, time zone, and branding — and explains which settings can never change.

### Overview

To open it, click your organization's name at the top of the page and choose **Edit Details** under **Manage**. The page, titled **Edit organization details**, holds your org-level identity. Most of it is freely editable; two fields are permanent.

![The Edit Details page, showing the immutable Country and Currency](https://283006627-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZrefv5JliAQavbeRiIvd%2Fuploads%2Fgit-blob-6566af08ab2a5026d25961eb77f8877a6faf3747%2Fedit-organization.png?alt=media)

***

### What You Can Edit

* **Organization Name** — your display name everywhere clients see you (receipts, emails, invitations). It must be 6–50 characters and not already in use.
* **Organization Handle** — the URL-friendly identifier in your admin and client links: 6–30 characters, using only lowercase letters, numbers, and underscores, and it can't start or end with an underscore. Changing it takes effect immediately — but see the caution below.
* **Organization Email** — the reply-to address for client emails (individual locations can override it for class/appointment emails). Saving a new email also updates the support email on your Stripe account.
* **Time Zone** — the org-wide default; locations carry their own for scheduling.
* **Tax ID Number** (EU organizations only) — your VAT number, shown on invoices issued to your clients. Connect payment processing before adding it.
* **Branding** — the **Logo** (square .jpeg/.png, at least 128×128, under 512KB) used on client receipts and communications. If BTWB created your Stripe account for you (a Stripe Express account, the usual setup), you'll also see **Brand Color** and a **Preview** of a sample receipt with your color and logo.

### What You Can't Edit

* **Country** and **Default Currency** are displayed as plain text because they're **permanent** — they were locked when the organization was created, since your payment processing account is built on them. (If your organization was created without them, you can set them here once; payment processing can't be connected until you do.)

***

### Notes for Admins and Coaches

* ⚠️ **Changing the handle changes some of your URLs.** Your [website embeds](/btwb/admin/programming-and-display/website-embeds-and-public-links.md) (class calendar, Marketplace, and workouts), the Marketplace link, and the appointment self-booking link include the handle and will stop working — copy the new code or link and replace the old ones wherever you've shared them. Bookmarked admin pages need updating too. Self-checkout links and QR codes for plans and documents use IDs, so they keep working.
* Renaming the organization also renames your billing products behind the scenes; no action needed.
* Only owners and full admins can open this page.


---

# 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://btwb.gitbook.io/btwb/admin/gym-setup/editing-organization-details.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.