Security and Permissions

This section explains how access to Production Scenarios can be controlled and what security considerations should be taken into account when configuring and using the app. Production Scenarios extends standard Business Central manufacturing processes by introducing Process Types, Production Scenarios, and scenario-driven planning and production behavior, so permissions should be assigned according to the user’s operational role.

Permissions

Following permission sets can be assign to users.

• (BRIPSC_BASIC) - Prod. Scenarios - Basic - This set grants users full access to all features and functionalities within the app. Users with this permission set can perform all operations within the app, including creating, updating, and deleting records. This set is ideal for users who need complete control over production scenarios and resource management.

• (BRIPSC_READ) - Prod. Scenarios - Read - This set restricts users to view-only access. This permission set allows users to view data but prevents any modifications. It is designed for roles that require information access without the risk of altering data

Data Retention and Privacy

Data Storage

Production Scenarios stores its operational and configuration data directly in the Microsoft Dynamics 365 Business Central database. Production Scenarios stores operational manufacturing configuration data, including:

• Process Types
• Production Scenarios (Item, Variant, Location, Process Type, Starting Date)
• Production definitions such as:
  • Production BOM
  • Routing
  • Family-related data (Family flag and Family No.)

This data is stored within standard Business Central tables and is used during:

• Planning Worksheet
• Order Planning
• Production Orders

The app does not introduce a separate external storage layer for production data.

Privacy Compliance

• Production Scenarios does not introduce personal data processing or user-sensitive data storage
• The app focuses on manufacturing configuration and operational data
• No PSC-specific privacy mechanisms (such as anonymization or masking) are defined

As a result:

• Data privacy compliance is governed by:
  • Microsoft Dynamics 365 Business Central standards
  • Customer-specific governance and compliance policies

Security Best Practices

To ensure secure and reliable use of Production Scenarios:

• Restrict access to setup
  • Limit creation and modification of Process Types and Production Scenarios to authorized users
• Control default scenarios
  • Only one default scenario is allowed per Item + Variant + Location
  • Incorrect default configuration can affect automatic planning behavior
• Validate changes carefully
  • Changes to Process Type can impact:
    • BOM selection
    • Routing selection
    • Family behavior in planning and execution
• Protect production consistency
  • Scenario changes are restricted once production has started (posted entries exist), ensuring traceability and data integrity
• Align with Business Central security model
  • Ensure PSC permissions are consistent with roles managing:
    • Manufacturing setup
    • Planning
    • Production execution

Supported Editions

This app supports the Essential and Premium editions of Dynamics 365 Business Central.

Supported Countries

All countries where Microsoft Dynamics 365 Business Central is available.

Supported Languages

Dutch, English, French, Portuguese.