> For the complete documentation index, see [llms.txt](https://docs.zingy.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zingy.ai/dashboard/overview.md).

# Overview

When you sign-in to your Zingy account, you are automatically led to the Zingy Dashboard.

The Zingy Dashboard allows you to:

* Manage your Apps

  Use the [**Apps**](/dashboard/apps.md) tab to create, edit and delete your Apps.
* View and Edit your account profile

  Use the [**Account Profile**](/dashboard/account-profile.md) option in the Settings menu to view and edit your profile.
* Manage members *(Feature coming soon).*

  Add/remove members to your account.
* View Invoices

  Invoices are available in the [**Invoices section**](/dashboard/billing-view-invoices.md) when you use the Billing option from the Settings menu.
* Manage [**Payment Methods**](/dashboard/billing-payment-methods.md)

  View the payment method being used to charge your Zingy account. You can also Add or remove payment methods.
* View [**Subscription Information**](/dashboard/billing-subscription.md)


---

# 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.zingy.ai/dashboard/overview.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.