# Infor LN SoD and Authorization Model Deep Dive

> Source: https://netray.co/resources/infor-ln-authorization-model
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Knowledge Base

## Short answer

Infor LN SoD (segregation of duties) explained: how LN roles, session authorizations and company security work, and how to build a SoD conflict matrix.

## Category

infor-ln

## Content

**Intro:** Infor LN SoD (segregation of duties) is built on the LN authorization model, so the two are best understood together. The Infor LN authorization model controls who can access which sessions, data, and functions across the enterprise. LN's security is multi-layered: session authorization determines form access, company authorization controls entity-level visibility, and function-level authorization governs specific operations within sessions. A well-designed authorization model enforces least-privilege access while minimizing the administrative overhead of managing hundreds of users across multiple companies.

**Sections:**

#### Authorization Layers and Role Design

**Body:** LN authorization operates at three layers: session access (which forms a user can open), data authorization (which records a user can view or modify), and function authorization (which operations a user can perform within a session). Roles aggregate these permissions into manageable units. Design roles around business functions, planner, buyer, warehouse operator, rather than departments, to create reusable permission sets that map cleanly to job responsibilities.

**Bullets:**

- Define roles around business functions with documented session access lists and permission boundaries
- Use session authorization groups to manage large sets of related sessions as a single permission unit
- Implement company-level authorization to restrict users to the legal entities they work with
- Configure function-level authorization for sensitive operations: cost visibility, price overrides, and master data changes

#### Segregation of Duties Implementation

**Body:** Audit compliance requires segregation of duties (SoD) in LN. Critical SoD conflicts include: creating vendors and processing payments, entering and approving purchase orders, posting journals and managing the chart of accounts. LN's authorization model supports SoD enforcement through role exclusion rules, but these must be configured explicitly. Build a SoD conflict matrix during implementation and validate it against role assignments regularly.

**Bullets:**

- Build a SoD conflict matrix mapping incompatible function combinations for your industry and audit requirements
- Configure role exclusion rules in LN to prevent assignment of conflicting roles to the same user
- Generate monthly SoD violation reports and remediate any conflicts within a defined SLA
- Document SoD control evidence for auditors including role definitions, exclusion rules, and violation reports

#### Authorization Lifecycle Management

**Body:** Authorization models degrade without lifecycle management. Users accumulate permissions as they change roles, temporary access becomes permanent, and new sessions get deployed without proper authorization configuration. Implement a closed-loop process: HR-triggered provisioning, role-based assignment, periodic certification, and automated deprovisioning. Track all authorization changes in an audit log that satisfies regulatory review requirements.

**Bullets:**

- Integrate user provisioning with HR processes so role assignments change automatically with job changes
- Require manager approval for all role assignments and document the business justification
- Conduct semi-annual authorization certification where managers review and confirm each user's access
- Maintain a complete authorization change log with timestamps, approvers, and business justifications

**Cta:** Strengthen your LN security, our consultants design audit-ready authorization models for manufacturers.

**Faq:**

#### What is SoD in Infor LN?

**Answer:** SoD means segregation of duties: no single user should hold two incompatible duties, such as creating a vendor and releasing payment to that vendor, or entering and approving the same purchase order. In Infor LN you enforce this through how you design roles and authorizations, so that incompatible session and function combinations are never granted to one user.

#### How do you check SoD conflicts in Infor LN?

**Answer:** Start from a conflict matrix that lists incompatible duty pairs for your audit scope, map each LN role to the sessions and functions it grants, then compare every user's combined roles against the matrix. Do this at role design time and again on a schedule, because access drifts as people change jobs. Check whether your Infor licence includes a governance and risk tool for automated conflict analysis; if not, the same review can be run from exported authorization data.

#### Who should own SoD reviews for Infor LN?

**Answer:** Business owners should certify who needs which access, while IT and internal audit supply the data and test the controls. Keep evidence of the matrix, the reviews and any approved exceptions, since auditors usually ask for all three.

## Related Slugs

- infor-ln-domain-administration
- syteline-security-roles-best-practices
- infor-ln-session-programming-guide

## Search terms

Infor LN SoD, segregation of duties Infor LN, Infor LN authorization, LN security model, LN role-based access, Infor LN permissions, LN audit compliance

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json