NSA graphic about reviewing system access as employee roles change.

Who Still Has Access? A Year-End Review of Users, Permissions, and System Ownership

Your business has likely changed since January.

Employees have joined the organization, moved into new positions, or taken on additional responsibilities. Outside partners may have supported projects. Reports, integrations, and scheduled processes may have been added along the way.

Have the accounts, permissions, and responsibilities supporting those activities kept up?

As distributors prepare for another year, reviewing system access provides an opportunity to bring the technology environment back into alignment with the way the business operates today.

Start With Who Can Sign In

An active account should have a clear purpose and an identifiable owner.

That sounds straightforward, but accounts can be overlooked as employees leave, temporary assignments end, or projects move into a different phase.

Begin by reviewing the people and organizations with access to your ERP and connected business systems.

Consider questions such as:

  • Are accounts for former employees still active?
  • Do temporary users or outside partners still require access?
  • Are there duplicate accounts that need investigation?
  • Can each account be connected to a current business need?
  • Are account changes consistently included in employee departure procedures?

An unfamiliar or inactive account deserves investigation before changes are made. Some accounts support integrations, scheduled tasks, or other business processes, and disabling them without understanding their purpose can interrupt operations.

The review should establish what each account does, who owns it, and whether it remains necessary.

Check Whether Permissions Match Current Responsibilities

An employee may still need access to the system while no longer needing every permission associated with a previous role.

A purchasing employee who moves into sales, for example, may retain access that was appropriate for earlier responsibilities. Someone temporarily covering another position may continue to hold additional permissions after that assignment ends.

Over time, those changes can become difficult to track.

Review permissions with department leaders and the people responsible for administering your systems. Confirm that employees can perform their current work and that broader access has a documented business reason.

Pay particular attention to permissions involving administrative settings, sensitive information, and activities that your organization expects different people to perform or approve.

The right access structure should support employees while maintaining appropriate oversight.

Look Closely at Shared Accounts

Shared logins can seem convenient, especially in busy operational environments. They can also make it harder to determine who performed an action or to remove one person’s access without affecting others.

Identify where shared accounts are being used and why.

Could individual accounts better support the work? Does the application offer a suitable approach for shared workstations? Who is responsible for managing credentials and reviewing access?

For accounts that must remain shared or serve a technical purpose, establish clear ownership and appropriate controls.

A shared account should still have someone accountable for how it is maintained and used.

Review Who Owns the Work Behind the Scenes

System access is only part of the picture.

Distributors also depend on reports, integrations, scheduled jobs, and other processes that may receive little attention until something stops working.

A report may be delivered from an employee’s account. An integration may depend on credentials established during implementation. A scheduled process may still be monitored by someone whose responsibilities have changed.

For each critical process, confirm:

  • Who is responsible for it?
  • What account or credentials does it use?
  • Who receives failure notifications?
  • Where is the supporting documentation?
  • Who provides backup coverage?

This review can help prevent a routine personnel change from becoming an operational disruption.

Coordinate Changes Across the Business

Access decisions work best when business leaders and technical administrators review them together.

A department manager understands what employees need to accomplish. An administrator understands how permissions, accounts, and connected systems support those activities.

Bringing those perspectives together helps avoid removing necessary access or leaving unnecessary access in place.

Plan changes carefully, document decisions, and confirm that affected employees and processes can continue working as intended.

For distributors using Infor CloudSuite Distribution, include connected applications in the discussion. Reviewing the ERP alone may leave important access points or dependencies unexamined.

Turn a Year-End Review Into an Ongoing Practice

An annual review provides a useful checkpoint. Clear procedures for new employees, role changes, departures, and outside access help keep the environment current throughout the year.

Establish who requests changes, who approves them, and who confirms that they have been completed.

Document ownership of critical processes and revisit that ownership when responsibilities change.

These practices can reduce uncertainty and make it easier to support the business as it evolves.

Keep Your Systems Aligned With Your People

Technology works best when access and responsibilities reflect the organization using it.

A year-end review can help distributors identify overlooked accounts, outdated permissions, and gaps in ownership before those issues create unnecessary work.

NSA Computer Exchange works with distributors to evaluate and optimize their Infor and supporting technology environments.

To discuss how your systems can better support your team heading into the new year, contact NSA at solutions@nsacom.com.

 

Search for Solutions, Webinars, Nuggets and Other Helpful Resources