1
Open FoodSoft Licensing Setup
In Business Central search, open FoodSoft Licensing Setup and confirm the portal URL matches the onboarding details supplied by LeXurey.
FoodSoft help
Configure secure module access in Business Central
FoodSoft includes a shared licensing, feature-control, and diagnostics layer. Use this guide to set up a new environment and understand an access decision.
Before you begin
Microsoft Dynamics 365 Business Central online, version 28.0 or later.
The FoodSoft Core Administrator permission set.
A FoodSoft environment registration and credential issued by LeXurey.
Allow HttpClient Requests enabled for FoodSoft Core in Extension Management.
Configure FoodSoft
2
Store the integration credential
Choose Set Integration Credential and paste the environment credential issued by LeXurey. Business Central stores it in encrypted module-scoped isolated storage.
3
Refresh the current user's entitlements
Choose Refresh Entitlements and confirm the message says a user-bound signed snapshot was verified.
4
Enable a licensed module per company
Open FoodSoft Company Features, enable the licensed module in the current company, and assign that module's separate Business Central permission set.
What the signed decision controls
FoodSoft verifies the portal's RS256 signature and checks tenant, environment, installation, app, version, current user, key, and time bindings. Licensing never adds a Business Central permission.
What leaves Business Central
A refresh sends the Microsoft tenant ID, environment name, FoodSoft app ID/version, installation ID, and current user object ID. It does not send transactions, prices, contacts, or documents.
Snapshot expired or no access?
Open FoodSoft Feature Diagnostics as the affected user. Check subscription status, company enablement, effective access, and the displayed reason. If the snapshot expired, return to FoodSoft Licensing Setup and refresh it.
Do not send the integration credential or compact entitlement JWS to support.
Need FoodSoft support?
Include the app and Business Central versions, affected feature, diagnostic reason, company enablement state, and last refresh time.
admin@lexurey.com