> For the complete documentation index, see [llms.txt](https://kb.bevica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.bevica.com/documentation/guides/getting-started-and-navigation.md).

# Getting Started & Navigation

Get productive in Business Central with Bevica. Learn navigation, search, inspection, and performance tips.

This section covers the basics of getting around Bevica and finding what you need fast.

### What you’ll get from this section

* Learn how Role Centres, search, and **Explore All** fit together.
* Personalise pages and lists to match how you work.
* Use inspection and navigation tools to troubleshoot and trace data.

Use these pages when you’re getting started, or when you need to get orientated on a new environment.

### Next steps

* Learn how to navigate your way round the software in [Introduction to Business Central](/bevica-select/bevica_select_training/bevica_select_training_-_introduction_to_business_central.md)
* After that go to [Role Centres](/documentation/guides/getting-started-and-navigation/role_centres.md).
* Then set up your workspace in [Personalising your views](/documentation/guides/getting-started-and-navigation/personalising_your_views.md).
* When you need technical context, use [Page Inspection](/documentation/guides/getting-started-and-navigation/page_inspection.md).
* To trace postings and drill into ledgers, read [Find Entries (Navigate)](/documentation/guides/getting-started-and-navigation/find_entries_-navigate.md).
* For reusable filtered lists, see [SmartLists](/documentation/guides/getting-started-and-navigation/smartlists.md).
* If pages feel slow, check [Understanding & Improving Performance](/documentation/guides/getting-started-and-navigation/understanding_and_improving_performance.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://kb.bevica.com/documentation/guides/getting-started-and-navigation.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.