Security and Permissions

Permissions

Upon installing the app, all users will be assigned Basic Permission by default:

(BRIRCP_BASIC) - Recipe Instructions - Basic: Allows the user to create, read, delete, and print Recipes.
(BRIRCP_READ) - Recipe Instructions - Read: Allows the user to read Recipes only.

Data Storage

All Recipe Instructions data is stored inside the customer’s Dynamics 365 Business Central tenant database. No external or separate database is used by the app.
The app stores functional data required to define, manage, and use recipes, including:
- Recipe master data, such as recipe headers, recipe lines (instructions, BOM‑related lines, routing‑related lines), and general instructions.
- Recipe version data, including version structures and starting dates used to control recipe validity over time.
- Recipe configuration references, such as links to Items, Production BOMs, Routings, and their respective versions.
- Document attachments linked to recipes (for example, work instructions, quality procedures, or regulatory documents), stored using standard Business Central document handling.
Recipe‑related setup (such as the Recipe Nos. number series) is stored as standard Manufacturing Setup data within Business Central.

Privacy Compliance

Recipe Instructions operates entirely within the customer’s Business Central environment, using standard pages and processes.
Access to recipe data is fully governed by Business Central permissions, including the permission sets delivered with the app (for example, Recipe Instructions – Basic and Recipe Instructions – Read).
Where recipes are linked to production orders, recipe visibility remains subject to the user’s role and permissions.
Recipe Instructions does not transmit recipe data outside the tenant and does not perform any background data collection beyond standard Business Central usage.

Data Archiving

Recipe Instructions does not require a separate archiving mechanism to function correctly.
Recipes and recipe versions remain available as long as they are retained within the standard Business Central data lifecycle.
Versioning allows historical recipes to remain accessible for traceability, auditing, and compliance, even after newer versions become active.
Any long‑term data retention, cleanup, or archiving strategy should follow the customer’s Business Central governance policies, since the app relies entirely on standard BC storage.

Security Best Practices

Use permission sets by role: Assign Recipe Instructions – Read for users who only need to view recipes (for example, shop floor users), and Recipe Instructions – Basic only to users responsible for maintaining recipes.
Limit recipe maintenance rights: Restrict recipe creation, editing, and version management to a small group (typically R&D, engineering, or process owners).
Rely on versioning instead of overwriting: Use recipe versions to introduce changes while preserving historical instructions. This supports traceability and reduces execution risk.
Control master data dependencies: Since recipes depend on certified Production BOMs and Routings, ensure BOM and routing changes follow proper approval processes before they are used in recipes.
Use production integration for controlled execution: When recipes are linked to production orders, operators always reference the correct recipe and version, reducing the risk of outdated instructions being used.

This app supports Premium edition of Dynamics 365 Business Central.

All countries where Microsoft Dynamics 365 Business Central is available.

English, Dutch, French, and Portuguese.

Last updated on Apr 28, 2026