> For the complete documentation index, see [llms.txt](https://docs.dynalogic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dynalogic.com/birds-document-warehouse-product-overview/d365-finance-and-operations/security-and-permissions.md).

# Security & permissions

## Viewing the Raptor 'dinosaur' button

To be able to see the Raptor 'dino' icon on a page, the following privilege is required:\
***To view Ex Arte Raptor document list***

{% hint style="warning" %}
If a user with this privelege still does not see the 'dino' icon while other users do, verify if the setting 'Enable document handling' is turned on in the user's preferences (System administration > Users > Users > User options > Preferences).
{% endhint %}

## Required Security Roles for the Raptor Service Account

Raptor uses a dedicated service account, linked to a Microsoft Entra ID app registration, to export data from Dynamics 365 Finance & Operations (D365 F\&O).

### Minimum Required Duties

The service account must be assigned the following duties:

* **View Document Entity Data for Data Management**
* **View Document Entity for Data Management (Extension)**

{% hint style="warning" %}
These duties provide access to all standard D365 F\&O data entities.
{% endhint %}

If your integration uses custom data entities, the service account requires additional permissions:

* Assign the **View** privilege for each custom data entity that needs to be synchronized.
* If an integration creates or updates records, also assign the **Maintain** privilege for the corresponding data entities.

If your implementation only requires a limited number of data entities (for example, when using the Kickstart solution), a standard duty is available that can be extended with project-specific data entities.

### Ex Arte Raptor Core Data Entities

The **Ex Arte Raptor Core Data Entities** duty grants access to the core entities required for document synchronization, including:

<details>

<summary>Included document-synchronization entities</summary>

* Sales order packing slip headers
* Ledger journal headers
* Project invoice headers
* Vendor invoices, invoice lines, purchase links, and product receipt lines
* Customer transactions, including free-text invoices and quotation journals
* Production order attachments

</details>

### Ex Arte Raptor Data Entities

The **Ex Arte Raptor Data Entities** duty provides access to the business master data required for synchronization, including:

<details>

<summary>Included business master data</summary>

* Vendors, prospects, customers, and contact persons
* Projects
* Purchase order headers
* Sales order headers
* Products and released products
* Sales agreement headers
* Purchase agreement headers
* Production orders
* Return order headers
* System users
* Expenses

</details>

### Ex Arte Raptor Input Data Entities (View and Maintain)

The **Ex Arte Raptor Input Data Entities** duty provides both **View** and **Maintain** permissions for imported data entities, including:

<details>

<summary>Included imported-invoice entities</summary>

* Ex Arte imported invoice headers
* Ex Arte imported invoice lines
* Ex Arte imported invoice header fields
* Ex Arte imported invoice line fields
* Ex Arte imported invoice purchase links

</details>

### Summary

Assign only the duties and privileges required for your implementation. Additional **View** and **Maintain** privileges should be granted only for the custom data entities used by your integration, ensuring both secure and efficient synchronization.


---

# 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.dynalogic.com/birds-document-warehouse-product-overview/d365-finance-and-operations/security-and-permissions.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.
