Systems and permissions
Which environments and records are in scope? Does the work need read access, configuration changes or transaction processing? Who approves the accounts, permissions and access period?
Engagement planning
ERP work needs clear decisions about accounts, environments, data and change approval. We use these questions to scope the engagement with your system owners and security team.
Book a callWhich environments and records are in scope? Does the work need read access, configuration changes or transaction processing? Who approves the accounts, permissions and access period?
Which sign-in and credential-sharing methods does your team approve? Who provisions accounts, manages authentication requirements and removes access when the work ends?
Can the work stay inside your environment? If extracts or sample files are needed, what may they contain, where may they be stored, how may they be transferred and when should they be returned or removed?
What test environment is available? Who accepts the test results and authorizes a production change? What are the change window, recovery steps and stop conditions?
What activity records does the project require, and which systems can provide them? Who reviews exceptions, receives an access or data-handling concern and coordinates the response?
Who receives the configuration records and operating instructions? Who confirms that temporary access is removed and that working files are handled as agreed?
The engagement scope should identify the responsibilities of your team, Lumina ERP and any other providers involved. Bring your access requirements and review process into the assessment so the plan can account for them.
For information about this website, read the published policies. Discuss project-specific access and data requirements during the engagement assessment.
Tell us which ERP and environments are involved, who owns access approval and what your review process requires.
Book a call