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

# 워크스페이스 정보 변경하기

워크스페이스 설정에서 워크스페이스 이름과 타임존을 관리할 수 있습니다.

대시보드 상단의 톱니바퀴 아이콘 > 설정 > '워크스페이스' 탭에서 확인하세요.

![](https://2738466581-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLHRZjjknm5KdNgPtDsbl%2Fuploads%2FhQLQ1FzdyXJismsg93W1%2F%E1%84%89%E1%85%B3%E1%84%8F%E1%85%B3%E1%84%85%E1%85%B5%E1%86%AB%E1%84%89%E1%85%A3%E1%86%BA%202026-11-12%20%E1%84%8B%E1%85%A9%E1%84%92%E1%85%AE%201.56.12.png?alt=media\&token=106d1646-191a-4d2b-bb11-1ae3f6bbe334)

## 워크스페이스 이름 변경하기 <a href="#change-workspace-name" id="change-workspace-name"></a>

#### Step 1. 편집 버튼 클릭

연필 모양의 `편집` 버튼을 클릭하면 워크스페이스 이름을 변경할 수 있습니다.

> 최초의 워크스페이스 이름은 가입한 이메일 계정에 설정된 이름 정보로 설정됩니다.

![](https://2738466581-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLHRZjjknm5KdNgPtDsbl%2Fuploads%2Fgit-blob-901bbc892f102ba5e5f1666ed7b477bdfdec9f0d%2F8482c60-workspace-manage-name-edit1_3a5f27a8893bbfcc.png?alt=media)

#### Step 2. 새로운 워크스페이스 이름 입력

변경하고자 하는 워크스페이스 이름을 입력하고, `수정하기` 버튼을 클릭하면 변경이 완료됩니다.

![](https://2738466581-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLHRZjjknm5KdNgPtDsbl%2Fuploads%2Fgit-blob-ef077c561e458e6d2962c48cd1cc68a2023b9cef%2F32b31dc-workspace-manage-name-edit2_d35102e1758ca54b.png?alt=media)

##

## 워크스페이스 타임존 변경하기 <a href="#change-workspace-timezone" id="change-workspace-timezone"></a>

워크스페이스의 기준 시간대를 설정합니다. (기본값: Asia/Seoul)

#### Step 1. 변경하기 버튼 클릭

'타임존 설정' 항목의 \[변경하기] 버튼을 클릭합니다.

<figure><img src="https://2738466581-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLHRZjjknm5KdNgPtDsbl%2Fuploads%2FkcDF8eq6DOyN2QaZ3iW1%2F%E1%84%89%E1%85%B3%E1%84%8F%E1%85%B3%E1%84%85%E1%85%B5%E1%86%AB%E1%84%89%E1%85%A3%E1%86%BA%202026-11-12%20%E1%84%8B%E1%85%A9%E1%84%92%E1%85%AE%201.56.12%20%E1%84%87%E1%85%A9%E1%86%A8%E1%84%89%E1%85%A1%E1%84%87%E1%85%A9%E1%86%AB.png?alt=media&amp;token=8a0f747d-c6d4-436e-9a92-8ab398263278" alt=""><figcaption></figcaption></figure>

#### Step 2. 타임존 (시간대) 선택

원하는 타임존을 선택하고 \[저장하기] 버튼을 클릭하면 변경이 완료됩니다.

<figure><img src="https://2738466581-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLHRZjjknm5KdNgPtDsbl%2Fuploads%2Fs5LRZVOSJa6XMfHRCTBs%2F%E1%84%89%E1%85%B3%E1%84%8F%E1%85%B3%E1%84%85%E1%85%B5%E1%86%AB%E1%84%89%E1%85%A3%E1%86%BA%202026-11-12%20%E1%84%8B%E1%85%A9%E1%84%92%E1%85%AE%202.01.30.png?alt=media&amp;token=630b8a97-07d2-431f-80dc-a0305bc61679" alt=""><figcaption></figcaption></figure>


---

# 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.hackle.io/workspace/change-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.
