A business role wizard
Start with a name and familiar activities. Use role templates or clone a draft to adapt a role design to the next requirement.
Lumi Permission Studio for Business Central
Design Business Central roles around the work people do.
A clearer way to plan permissions in Business Central. Turn business responsibilities into roles with visible dependencies, explicit company scope and a permission plan you can review.
For Business Central administrators, partners and business role owners.
BUSINESS ROLE
Customer Coordinator
Maintain customers. View item information.
Where and who
- Company
- Demo Trading
- Recipient
- Alex Morgan
- Assignment type
- Individual user
Company scope and recipients are explicit parts of the role plan.
Choose business activities
Selecting Create/Edit automatically includes View.
Permission plan
3 capabilitiesNo business activities selected.
- Company
- Demo Trading
- Recipient
- Alex Morgan
A role plan with contextCapabilities, dependencies and assignment intent.
01 Business language first02 Dependencies in view03 Reviewable access decisions
From requirements to roles
The job is clear.
Make the access plan clearer.
A business owner knows what a job needs to do. An administrator needs to understand the technical permissions behind that request.
Lumi Permission Studio connects those conversations. Define the activities a role needs, see the supporting dependencies, and review its permission contributions and intended assignments in one guided workflow.
“Our Customer Coordinator needs to maintain customers and view items at Demo Trading.”A fictional business requirement
The role design workflow
Six steps.
One explainable role.
Move from a business request to a role draft that administrators and role owners can discuss together.
- 01
Name the role
Give the job a business name and description. Start from a role template when useful.
Customer Coordinator - 02
Choose companies
Select where the role applies, or explicitly choose all companies.
Demo Trading - 03
Choose business areas
Focus the catalogue on the Sales, Purchasing or Inventory activities you need.
Sales + Inventory - 04
Select capabilities
Choose View, Create/Edit or Post activities where available. Required dependencies appear automatically.
Create/Edit → View - 05
Choose recipients
Plan assignments for individual users, security groups or both, within the selected company scope.
Users + security groups - 06
Review the role
Inspect the requested capabilities, supporting permissions and proposed assignments together.
A reviewable permission plan
Permission planning, with context
See the choices.
Understand the permissions.
Bring responsibilities, supporting grants and assignment intent into the same conversation.
Visible dependencies
Required supporting capabilities are included automatically. See why View accompanies Create/Edit, and why Post depends on both.
Companies and recipients
Make company boundaries explicit. Plan access for individual users, Microsoft security groups or both.
Permission sources and comparisons
Inspect the sources behind permission contributions. Compare role designs and review conflict messages and assignment changes.
A role everyone can discuss
Customer Coordinator.
From intent to review.
At Demo Trading, this role needs customer maintenance and item information. The supporting choices stay visible to the role owner and administrator.
Explore the interactive role planSELECTED ACTIVITYCustomers Create/Edit
Automatically includes
REQUIRED DEPENDENCYCustomers View
ADDITIONAL ACTIVITYItems View
Review today. Understand the next change.
A role evolves.
Keep the decisions visible.
Role comparisons and permission explanations make changes easier to discuss. Review how a role design differs, trace the supporting grants and keep company and recipient choices in view.
The maintenance framework includes snapshots, drift detection and explicit rebuilds, giving administrators context for the next role review.
Review the permission plan
Inspect capabilities, supporting grants and assignments.
Understand the sources
See what contributes to the role and why.
Compare the next change
Discuss role differences with the business owner.
Initial business catalogue
14 capabilities.
Six familiar business areas.
Selected activities across Sales, Purchasing and Inventory. Create/Edit is one combined capability; Post applies to Sales Orders and Purchase Orders.
Customers
ViewCreate/Edit
Sales Quotes
ViewCreate/Edit
Sales Orders
ViewCreate/EditPost
Vendors
ViewCreate/Edit
Purchase Orders
ViewCreate/EditPost
Items
ViewCreate/Edit
Dependencies follow Create/Edit → View and Post → Create/Edit → View.
Business Central permissions
Permission set configuration,
explained through the role.
Business Central permission set configuration starts with the work a person needs to do. Lumi Permission Studio connects that requirement to business capabilities, supporting permissions and a proposed assignment plan.
A useful permission plan answers four questions: what does the role contribute, why is each dependency included, which companies are in scope, and who should receive it?
Role-based access planning gives those decisions context. Connect job responsibilities to permission sources, company boundaries and recipient choices in Microsoft Dynamics 365 Business Central.
Explore our Business Central servicesLumi Permission Studio
Bring clarity to your
next role conversation.
Tell us how you approach Business Central permissions and what your teams need to do.
Discuss Lumi Permission Studio
Send your enquiry securely through our website.
Privacy & Cookies
Questions, answered
A clearer view of
Business Central access.
What is Lumi Permission Studio?
Lumi Permission Studio is a Business Central extension for drafting business roles and reviewing the capabilities, supporting permissions, companies and recipients behind them. It connects business responsibilities to a permission plan that an administrator can inspect.
How does it help with permission set config in Business Central?
Start with a role’s business responsibilities, select companies and capabilities, choose users or security groups, then review the permission contributions and assignment plan. This structured workflow helps administrators explain how the role’s requirements connect to Business Central permission sets.
Who is it for?
Business Central administrators and partners, working with finance and operations role owners who define job responsibilities. Role owners describe the work; administrators review the access decisions.
Can I choose companies and security groups?
The workflow includes explicit company selection and assignment planning for individual users, Microsoft security groups or both. The role’s company scope applies to the selected recipients.
How are required dependencies handled?
Required supporting capabilities are included automatically and remain attached while the parent activity needs them. Create/Edit includes View. Where Post is available, it includes Create/Edit and View.
What can I review in a role plan?
Review the selected capabilities, supporting permission contributions, their sources, the company scope and proposed recipients. Role comparisons help explain what changes between one design and another.
Which business activities are in the initial catalogue?
There are 14 capability entries across Customers, Sales Quotes, Sales Orders, Vendors, Purchase Orders and Items. Create/Edit is a combined activity. Post is included for Sales Orders and Purchase Orders.