> For the complete documentation index, see [llms.txt](https://docs.doku.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.doku.com/changelog/july-2024/new-navigation-doku-dashboard.md).

# New Navigation - DOKU Dashboard

Simplified Access, Enhanced Experience

The DOKU Dashboard has undergone a major upgrade, featuring a streamlined navigation system designed for effortless access and management of all your DOKU products.&#x20;

#### **Key Benefits:**

* **Centralized Product Management:** Easily activate and manage all DOKU products from one location.
* **Streamlined Navigation:** Save time and focus on your business with simplified navigation.
* **Future-Proof Design:** Seamlessly integrate upcoming DOKU products and services.
* **Enhanced User Experience:** Enjoy a smooth, intuitive, and visually appealing interface.

<figure><img src="https://2961485474-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5XrPPWlRNNTQG72DaVGd%2Fuploads%2F8a5XeqnuSNcJS9D3ZLNj%2FWhatsApp%20Image%202024-07-31%20at%2010.57.45.jpeg?alt=media&amp;token=c71ed031-c912-49df-9e1c-9473d14573da" alt=""><figcaption></figcaption></figure>

#### **Navigation Changes:**

| Menu                   | Old Navigation                      | New Navigation                     |
| ---------------------- | ----------------------------------- | ---------------------------------- |
| Business Info          | Account menu                        | Settings menu -> Account           |
| Bank Account           | Account menu                        | Settings menu -> Finance Settings  |
| Service                | Account menu                        | Settings menu -> Account           |
| Approval               | Account menu                        | Settings menu -> Account           |
| Team Management        | Account menu                        | Settings menu -> Account           |
| Activity Log           | Account menu > Team Management menu | Settings menu -> Team and Security |
| Document               | Account menu > Business Info menu   | Settings menu -> Account           |
| API Keys               | Integration menu                    | Settings menu -> Account           |
| Settlement Settings    | Setting menu                        | Settings menu -> Finance Settings  |
| General Ledger         | Homepage                            | Reports menu -> General Ledger     |
| Checkout Page Settings | Settings                            | Settings menu -> Accept Payments   |

We are confident that the new DOKU Dashboard navigation system will empower you to manage your DOKU products with greater ease and efficiency. Stay tuned for further updates as we continue to innovate and expand our suite of financial solutions!


---

# 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.doku.com/changelog/july-2024/new-navigation-doku-dashboard.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.
