> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/kb/appmixer-studio-features/changing-a-password.md).

# Changing a password

[Once you start a free trial with Appmixer](https://www.appmixer.com/pricing), you will be provided with unique credentials – Username, API URL and Password. Username and API URL can't be changed for technical reasons. Password, on the other hand, can.

We made changing a password as simple as it gets. Log into Appmixer Studio and click on the little Profile icon in the right upper corner.

![Click on the "Profile" icon](https://660555879-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Meyy9fJyhzsrd3q4-5N%2F-MlG88-tjmiTcWJRPM34%2F-MlGCa4YpR_KEhJXmRBz%2Fgif-password-1.gif?alt=media\&token=7fb1065d-a654-434c-9b82-766797d22d53)

Next, click "Change Password" and wait for the window to appear.

![Click on "Change Password"](https://660555879-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Meyy9fJyhzsrd3q4-5N%2F-MlG88-tjmiTcWJRPM34%2F-MlGD07Y24fKeqIAKbeg%2Fgif-password-2.gif?alt=media\&token=9e0bd98b-5fea-4dea-9b32-3a0940037fa4)

Now, you'll need to provide your old password as well as the new one. By clicking on the "Submit" button, your new password will be saved.

{% hint style="warning" %}
Note that if you change your password in the Appmixer Studio, the changes will apply to Backoffice and SDK Demo(s).
{% endhint %}


---

# 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.appmixer.com/kb/appmixer-studio-features/changing-a-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.