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

# 비밀번호 변경하기

## 이 글에서는

스티비 로그인 시 사용하는 비밀번호를 변경하는 방법에 관해 알아봅니다.

***

스티비 로그인 시 사용하는 비밀번호를 변경하는 방법은 아래와 같습니다.

1. 화면 오른쪽 위 \[워크스페이스 이름] 클릭
2. \[내 정보] 클릭
3. \[비밀번호 → 변경하기] 클릭
4. 현재 비밀번호와 새로운 비밀번호를 입력하면 변경이 완료됩니다.

<figure><img src="https://468498824-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FeAMHRdY4ATDXfWZWQs3p%2Fuploads%2Fb5Tb0RDmRjsPko4QuEHx%2F%EB%B9%84%EB%B0%80%EB%B2%88%ED%98%B8%20%EB%B3%80%EA%B2%BD%ED%95%98%EA%B8%B0.png?alt=media&amp;token=f9c78d23-9e0a-4162-9232-07a9a7c4d5cb" 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://help.stibee.com/user-workspace/profile/password.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.
