> For the complete documentation index, see [llms.txt](https://docs.phocassoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.phocassoftware.com/basics/favorites/set-a-favorite-as-your-default-view.md).
# Set a favorite as your default view
Replace your default view in Analytics or Financial Statements with a favorite that contains the information you want to view immediately.
When you access a database in the Analytics or Financial Statements module, the layout and contents of the grid is the default view set up by your organization. You can change this view to meet your own needs, by setting a default view. Then, whenever you access the database, you see the data you need straight away, in your preferred view.
Default views are created from favorites. When you go to set your default view, you will see a list of the favorites you have saved, along with any that have been shared with you.
1. Ensure you have [saved the view as a favorite](/basics/favorites/view-and-save-favorites.md).
2. In Analytics or Financial Statements, click the blue arrow in the top bar and select **Set default view**.
3. Select the favorite you want to set as your default view and click **Save**.
To remove a default view, select the **Use Standard View** option.
---
# 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.phocassoftware.com/basics/favorites/set-a-favorite-as-your-default-view.md?ask=&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.
