🚧 Why Organizational Structure in IFS Cloud Matters — Even If You’re Only Using One Company

Clarification:

Thanks all for the feedback! Just to clarify — the scenarios were meant to show how Org Levels support things like reporting segmentation, workflow alignment, and analytics filtering.

They don’t directly enforce security or financial postings — those are managed through Permission Sets, Organization Units, and Scope configurations in IFS Cloud.

That said, the scenarios I shared above are still valuable when testing User Permissions in combination with Org Levels, especially for understanding structure and planning alignment.

Unfortunately, I can’t edit the original post directly, so I appreciate your understanding and wanted to provide the clarification here.

Diving deeper:

Organizational Levels (as defined in the Graphical Org Structure) don’t control security access by themselves. Instead, they play an important supporting role in the overall design and governance of the system, particularly in:

• Workflow routing (e.g., approvals based on reporting lines)

• Structuring responsibilities for aligning security and roles

• Analytics filtering (e.g., dashboards scoped by department or business unit)

• Governance alignment that supports scalability and audit readiness

While Org Levels won’t restrict access directly, they do help establish a clear, scalable foundation that can guide how responsibilities and roles are assigned as your system grows.

It’s generally a good practice to define them early — but if it’s not a priority right now, it’s still something worth revisiting later as your organizational structure evolves.

One more clarification that I meant to clarify before. With the Diving Deeper, it really should be the following. Thank you for your patience on this:
 

Organizational Levels (as defined in the Graphical Org Structure) don’t directly enforce Role-Based security in IFS Cloud. Security enforcement is handled through Permission Sets, Projections, and Scope configurations.

That said, Org Levels are far more than just a visual reference — they play a valuable role in the overall design and structure of the system, especially when it comes to:

• Structuring responsibilities for planning and aligning security roles
• Analytics filtering (e.g., dashboards scoped by department or business unit)

So while Org Levels won’t restrict user access by themselves, they help establish a clear, scalable foundation that informs how roles and responsibilities are assigned across the organization over time.

All in all, it's good general practice to define them early. If you're not ready to implement them now, it's totally fine to move forward without them — but I’d recommend revisiting it down the road as the organization scales or processes mature.