> For the complete documentation index, see [llms.txt](https://help.hippoly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.hippoly.com/administration/workspace-administration/workspace-name.md).

# Workspace name

The Workspace name is used together with the [Workspace type](/administration/workspace-administration/workspace-type.md) to identify the workspace throughout Hippoly. It appears in notifications, system-generated documents such as Minutes, and anywhere the workspace needs to be clearly referenced. In most cases, the Workspace name is the same as your organisation’s name.

<figure><img src="https://2368761383-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5A8sAk8EwFvZz8ID3yYR%2Fuploads%2Ft4PYOEsp0MCYjsnwVbQ1%2Fworkspace-settings-name.png?alt=media&amp;token=d20fa1fe-8453-4f31-8e36-7fed5bbba0e5" alt=""><figcaption></figcaption></figure>

## Change name for the workspace

{% hint style="info" %}
**Note:** In some regions, Hippoly can automatically retrieve organisational data from public records. If your workspace is connected to a public record, you will not be able to see this setting or update the Workspace name manually.
{% endhint %}

{% stepper %}
{% step %}
Navigate to `Settings` in the main menu.
{% endstep %}

{% step %}
Expand the **Workspace name** section.&#x20;
{% endstep %}

{% step %}
Enter the new name in the input field.
{% endstep %}

{% step %}
Click the **Save** button.
{% endstep %}
{% endstepper %}


---

# 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://help.hippoly.com/administration/workspace-administration/workspace-name.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.