> 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/bevica-knowledge-base/your-guide-to-the-knowledge-base.md).

# Your Guide to the Knowledge Base

**Why this matters.** You get faster answers when know where to look and search the right area first. You also avoid mistakes when you validate AI output.

### Summary

* Use [**Documentation** ](/documentation/readme.md)for day-to-day Bevica how-tos.
* Use [**Bevica Select**](/bevica-select/readme.md) for in project assistance, training agendas and data migration templates.
* Use [**API Reference**](/api-reference/readme.md) for technical integration work.
* Use [**Roadmap & Releases**](/roadmap/bevica-roadmap.md) to plan upgrades, release notes and testing. See Microsoft training agendas and videos.

### Where to start (by topic)

#### Documentation

Use this when you need to do something in **Dynamics 365 Business Central** with **Bevica**.

Typical reasons:

* Configure setup (number series, posting groups, dimensions, approvals).
* Run daily processes (policies, claims, billing, renewals, postings).
* Fix a user problem (permissions, missing actions, validation errors).
* Understand a report or reconcile totals (entries, ledgers, registers).
* Follow a checklist (month end, year end, upgrade testing).

Example questions:

* “How do I manage a sales order?”
* “Why can’t I see **Actions > Post** on this page?”
* “Which entries update when I post?”

#### Bevica Select

Use this when you are implementing or changing how you work.

Typical reasons:

* Define scope, roles, and responsibilities for the project.
* Plan training (agendas, exercises, role-based enablement).
* Prepare data migration (templates, mapping, cutover steps).
* Align on process design before you configure in Business Central.

Example questions:

* “What data do we need for go-live?”
* “Which roles need training, and when?”
* “What’s the recommended order for migration and validation?”

#### API Reference

Use this when you are integrating Bevica or Business Central with another system.

Typical reasons:

* Look up endpoints, payloads, and auth requirements.
* Validate field names, types, and required values.
* Troubleshoot integration errors with concrete request/response details.

Example questions:

* “Which endpoint creates a policy?”
* “What does this error code mean?”
* “Which fields are required for this POST?”

#### Roadmap & Releases

Use this when you plan a Wave update or need to understand what's changed.

Typical reasons:

* Review release notes and great new features.
* Understand impact on your processes, reports, and integrations.
* Assign owners for testing, training, and comms.
* Track deprecations and deadlines.

Example questions:

* “What's changed in the latest release?”
* “Do we need to retest posting or integrations?”
* “Is any feature being removed soon?”

### How to get answers (Search + Ask AI)

Use the header bar for fast answers.

1. Use **Search** when you know the keyword or feature name.
2. Use **Ask** when you want a short explanation or a starting point from the AI Agent.
3. Use **Customer Portal** when you need to log a case or check case updates. A login is required.

#### Ask: how to get a good answer

Give the AI enough context to match your query and scenario.

Include:

* Your goal. Say what you’re trying to achieve.
* The Business Central page name, include the business area and key words..
* The exact action you chose.
* What you expected versus what happened.

Avoid:

* Customer data, credentials, or personal information.
* “It doesn’t work” with no steps or error text.

Examples you can copy:

```
In Bevica, how do I [goal]?
I’m on the [page name]. I chose [Actions > ...]. I expected [X], but got [Y].
```

```
I get this error when I post: “[paste error text]”.
What does it mean, and what should I check first?
```

{% hint style="warning" %}
AI answers can be incomplete or wrong.

* Open the linked pages and validate key steps and UI labels.
* AI can’t see your Business Central tenant, permissions, or data.
  {% endhint %}

{% hint style="danger" %}
Don’t paste customer data, credentials, or personal information into **Ask AI**.
{% endhint %}

### For integrators (optional)

This Knowledge Base can be used as a **Model Context Protocol (MCP)** server.

An MCP server lets AI tools query the Bevica Knowledge Base as a trusted source. You connect an MCP‑compatible assistant to this server, and it can search and retrieve relevant pages to answer questions.

Only connect customer-safe content and sources.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://kb.bevica.com/bevica-knowledge-base/your-guide-to-the-knowledge-base.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.