> 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/permissions-and-security/bevica_permissions.md). # Bevica Permissions Recommended permission sets and access patterns for common Bevica roles. Bevica comes with default Permission Sets. These allow you to manage what your Users have or don't have access to in the software. The majority are created and managed by Microsoft, others exist to manage installed Extensions. The ones listed below manage access to Bevica specific functionality. {% hint style="warning" %} **Prerequisites** Users have been created. Understanding how Permission Sets are created, modified and applied to Users. For more information on creating Users, see [Create Users According to Licences](https://docs.microsoft.com/en-us/dynamics365/business-central/ui-how-users-permissions). For more information on managing permissions, see [Assign Permissions to Users and Groups](https://docs.microsoft.com/en-us/dynamics365/business-central/ui-define-granular-permissions). {% endhint %} ### Permission Sets Bevica has a number of permission sets that should be used in conjunction with other permission sets in the software. {% hint style="info" %} To see the specific details behind any permissions set, navigate to it and select **View All Permissions**. {% endhint %} ### Bevica There are two **Super User** Bevica permission sets. We recommend using **TVTB SUPER** as **BEVICA ESSENTIALS** may become obsolete in the future. * **TVTB SUPER** - gives Users complete access to all Bevica data. No further Bevica permission sets are required if a user is assigned this set. For Super Users, this permission set should be used in conjunction with the **SUPER** permission. * **BEVICA ESSENTIALS** - gives Users complete access to all Bevica data. No further Bevica permission sets are required if a user is assigned this set. For Super Users, this permission set should be used in conjunction with the **SUPER** permission. ### Duty There are three permission sets that control access to core Bevica related data. * **BESS DUTY SETUP** - assign this to Users who are setting up Bevica in the system, change Duty rates or control finance posting setup * **BESS DUTY EDIT** - assign this to all other users who create and manage Manifests. * **BESS DUTY VIEW** - assign this to all other users who view items or process inventory. ### Private Reserves There are three permission sets that control access to private reserve data. * **BESS PRES SETUP** - assign this to Users who need complete access to Private Reserve data. (**BESS DUTY SETUP** is also required) * **BESS PRES EDIT** - assign this to users who manage Private Reserves on a day-to-day basis (**BESS DUTY VIEW** is also required) * **BESS PRES VIEW** - assign this to users who need to see Private Reserve information. ### Unpaid Reserves There are four permission sets that control access to unpaid reserve data. * **TVTB UPR VIEW** - assign this to Users who just need to view unpaid reserve information. * **TVTB UPR SORDER** - assign this to Users who can only apply unpaid reserves to sales orders. * **TVTB UPR EDIT** - assign this to Users who manage unpaid reserve information. * **TVTB ALL VIEW** - this gives Users full Bevica Super permissions but only view access to unpaid reserves. To assign this to a User make sure they don't have **TVTB SUPER** or **BEVICA ESSENTIALS** and assigned them this permission set instead. You will also need to give users the **D365 JOBS, EDIT** permission set. ### Marketing There are two permission sets that control access to Item marketing related data. * **BESS MK SETUP** - assign this to Users to set up item marketing codes, i.e. Region, Subregion, Classification codes etc... * **BESS MK VIEW** - assign this to users who view items and related information. ### Other Features Other related Bevica features have their own permission sets, see: * [Bevica Third Party Warehouse Integration permissions](/documentation/integration/bevica_warehouse_integration/bevica_third_party_warehouse_integration_permissions.md) * [Distribution Costs Management permissions](/documentation/guides/permissions-and-security/distribution_costs_management_permissions.md) * [Bevica Excellar / Commission permissions](/documentation/guides/permissions-and-security/bevica_excellar_commission_permissions.md) {% hint style="info" %} These Bevica Permission sets cannot be changed but can be copied to create new ones. These can then be changed as required, i.e. a number of permission sets can be combined into one or permissions split into multiple for more granular access to the system. {% endhint %} ### Other Permission Sets In addition to the above permission sets, there are the permission sets that would typically be given to a user if they are not a super user. Note that these are not definitive lists, users may need additional permission sets depending on the transactions they need to process and the functionality that has been configured. **Sales Order Processing** * D365 Basic * D365 Customer, Edit **or** D365 Customer, View * D365 Item, Edit, **or** D365 Item, View * D365 Sales Doc, Edit **or** D365 Sales Doc, Post * D365 Sales **Purchase Order Processing** * D365 Basic * D365 Vendor, Edit **or** D365 Vendor, View * D365 Item, Edit **or** D365 Item, View * D365 Purch Doc, Edit **or** D365 Purch Doc, Post **Sales Ledger** * D365 Basic * D365 Acc. Receivable * D365 Customer, Edit **or** D365 Customer, View * D365 Journals, Edit **or** D365 Journals, Post **Purchase Ledger** * D365 Basic * D365 Acc. Payable * D365 Vendor, Edit **or** D365 Vendor, View * D365 Journals, Edit **or** D365 Journals, Post **Finance (includes banking, currencies, VAT, G/L budgets and financial reporting)** * D365 Dim Correction * D365 Finance * D365 GL Review * Local **If they are using Assembly Orders, also consider:** * D365 Assembly, Edit * D365 Assembly, Setup * D365 Assembly, View **Other permission sets to consider:** * Edit in Excel * Excel Export Action * Shopify Admin --- # 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/documentation/guides/permissions-and-security/bevica_permissions.md?ask=&goal= ``` `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.