Infor LN User Role and Authorization Matrix Worksheet
Access reviews are easier when roles, functions and conflicts live in one table. This worksheet lets your LN administrator and the business owners walk through who can do what, rate the risk and record the decision for the auditor.
| Role | Business function | Session or area | Access level | Users in role | Risk score (1-5) | Exposure | SoD conflict | Review status | |
|---|---|---|---|---|---|---|---|---|---|
18 | |||||||||
12 | |||||||||
32 | |||||||||
28 | |||||||||
10 |
Role names, sessions and scores are examples. Use your own role and session codes, and define the 1 to 5 risk scale with your auditor before scoring.
Access review help
Optional: we can talk through a repeatable access review for LN that your auditor can follow.
Optional. The tool and every export work without this. No spam.
How to use the matrix
Start from your roles, not from individual users. For each role list the business function it supports, the session or area it touches and the access level. Enter how many users hold the role and a risk score from 1 to 5 agreed with your auditor. Exposure multiplies the two, so a powerful role held by many people rises to the top. Set the SoD column to Possible or Confirmed where a role combines duties that should be separate, and use the review column to record the owner's decision.
- Review roles first, then exceptions on individual users
- Agree the risk scale in writing before scoring
- Record the reviewer and date outside the sheet or add a note
- Re-run after every role change
Segregation of duties basics
The classic conflicts are the ability to create a supplier and pay that supplier, to raise and approve the same purchase order, to receive goods and approve the invoice for them, and to maintain users while also posting transactions. A single role does not need to hold both halves of a pair to cause the problem: a user with two roles can. So review combinations per user as well, and treat the matrix as the first pass. Where a conflict cannot be removed for staffing reasons, document the compensating control, such as a monthly review of the transactions.
Reading the exposure column
Exposure is a ranking aid, not a measure of loss. Sort descending and review the top rows first: these are the roles that are risky and widely held. A role with a risk of 5 and two users, such as a support administrator, may still deserve attention because of what it can do. Pair the numbers with the SoD column, and set a rule such as no Confirmed conflict stays open beyond the next review cycle.
Common mistakes
Reviews often cover only named business roles and skip technical and support accounts, which tend to hold the broadest access. Another mistake is approving access based on job title instead of the tasks actually performed. A third is treating the review as complete once rows are marked Approved without removing the access that was rejected. Always follow decisions through to the actual role or user change, and keep evidence of it.
Frequently Asked Questions
Is this a replacement for an LN security tool?
No. It is a documentation and review aid. It helps you structure decisions and evidence, while the actual authorizations are maintained in LN. For large estates you may want a dedicated access governance tool.
How do I pick a risk score?
Agree a simple scale with internal audit, for example 1 for display only and 5 for the ability to move money or change security. Apply the same scale to every row and write the definitions down.
How often should access be reviewed?
At least annually for most organizations, and more often for high-risk roles. Also review after reorganizations, system upgrades and any role redesign.
Can I paste data from an LN report?
You can type or paste values row by row. Keep your own role and session codes, and verify them against what LN reports before using the sheet for audit evidence.
If access reviews take weeks today, we can discuss how a private assistant could read your LN authorization data and prepare conflict candidates for your administrators to confirm.
Related Tools
Infor LN Go-Live Readiness Checklist
Go or no-go checklist for an LN implementation, upgrade or Baan migration, with critical items flagged.
Infor LN & BaanInfor LN Cutover Runbook Template
Editable task-by-task cutover plan with owners, durations, dependencies and total cutover hours.
Infor LN & BaanInfor LN Change Request Form Template
Fill-in change request form for LN and Baan changes, covering scope, impact, testing, rollback and sign-off.
Infor LN & BaanInfor LN Integration Health Assessment
Score the health of your Infor LN integration landscape across architecture, monitoring, error recovery, EDI, and governance in ten quick questions.
More Infor LN & Baan tools
See all- Infor LN Session and Module Code Reference
- Infor LN Production Order Status and Lifecycle Reference
- Infor LN 4GL Session Script Template
- Infor LN Company and Enterprise Unit Design Worksheet
- Infor LN DAL Hook Review Checklist
- Infor LN Warehousing Order Origins and Types Reference
- Infor LN Table Name and SQL Query Builder
- Infor LN Regression Test Effort Calculator
- Infor LN and Baan Customization Inventory Worksheet