Understanding Organization Structure

Organization structure in CLUE helps you match the system to the way your company already works. It lets you group teams, assets, and projects by division, region, yard, or another business unit so access, reporting, and planning stay organized.

‍

Hierarchy Levels

CLUE’s Understanding Organization Structure article says the platform supports up to 3 levels of sub-organizations. A common setup is:

• Level 1 - regions or major divisions
• Level 2 - districts or departments
• Level 3 - yards or local offices.

If your team wants a more visual way to review the org tree, Organization Hierarchy and Sub-Organizations is the best next article to open because it shows the structure as a tree and table view.

‍

Why Structure Matters?

A clear organization structure does more than keep names tidy. In CLUE, it affects what people can see, how data rolls up, and how work is managed across the business.

Teams usually use it for:

• Permissions - limit access to the right division or area
• Reporting - roll up data by region, division, or sub-organization
• Dispatch - keep resources aligned to the right operating area
• Billing and cost tracking - organize costs by division.

If you are setting this up mainly for user access, Understanding Permissions and Roles fits naturally here because roles and org structure work together to control what users can see.

‍

Setting Up Structure

Set up the hierarchy in Company Settings, then build the sub-organizations from the top down. Keep the layout close to your real business structure so it is easier to manage later.

To set it up:

• Go to Admin > Company Settings
• Open Organization Structure
• Click Add Sub-Organization
• Enter the division or sub-organization name
• Set the level
• Choose a parent organization if needed.

If your team is using the newer org chart view, CLUE also has an Organization Hierarchy and Sub-Organizations page that covers managing the structure from a visual tree.

‍

Assigning Users and Assets

After the structure is in place, assign people, assets, and projects to the right part of the hierarchy. This is what makes the structure useful in day-to-day work.

A normal setup includes:

• assigning each user to their home division or sub-organization
• updating assets with the correct owning division
• placing projects inside the right part of the organization.

If you are doing this as part of user setup, Managing the People Directory is the right place to handle user records. If you are organizing fleet records, Editing Asset Information and Creating a New Project are the natural next steps.

‍

Tips

Keep the structure simple and only add levels you really need. CLUE’s guidance says it is best to match your existing reporting structure and plan the layout before rolling it out, because hierarchy changes can affect permissions and visibility.

A few good rules to follow:

• keep the hierarchy as simple as possible
• match the structure your team already uses for reporting
• plan the layout before you start assigning users and assets
• review permissions after setup so people only see the right data.