One Setup, Multiple Org Chart Views for Different Audiences

When an organization needs more than one view of its structure, a second file can feel like the quickest solution. It also creates another copy to update, share, and secure.

The safer design is to keep one employee dataset and define the views each audience actually needs. The goal is not to expose every field everywhere. It is to make the right context available without asking HR to maintain several competing versions.

Start with one source and explicit views

Treat the employee dataset as the source and the chart as a view of that data. A simple source might include employee ID, name, title, department, manager ID, location, and optional profile context. Each audience then gets a documented slice of those fields.

The exact fields depend on your privacy rules and the capabilities of your tools. Write the matrix down before you build the views so access decisions do not get made ad hoc. This is a governance matrix, not a promise that every vendor supports field-level filtering. HumanMap’s current workflow provides map-level access controls and separate maps from shared employee data; verify the current plan and permissions before promising per-field visibility.

One dataset with multiple views can reduce duplicate maintenance, but it does not remove governance. Someone still needs to own the data, review permissions, and decide what happens when a person joins, leaves, or changes teams.

What Each Audience Actually Needs

What each audience needs:

The Board / Leadership View

Purpose: Strategic oversight, headcount planning, organizational review.

Shows: Leadership team, department heads, headcount per team, open positions, reporting lines to the CEO. Consider including tenure data so the board can spot concentration risk (teams where everyone is new, or where one tenured person holds all the context).

Hides: Individual contributor details, personal interests, contact information for non-leadership roles. No Slack handles, no hobbies, no project-level detail.

Access: Restricted to the people who need it. Use the access controls your tool provides and review the list before each board or planning cycle.

The Employee View

Employees need an org chart for navigation, collaboration, and discovery. This view can show the team structure plus the optional context people have chosen to share, such as skills, interests, location, or current projects. Make it easy to find, then ask employees which fields actually help them answer real questions.

The External / Partner View

The external view serves clients, vendors, auditors, or new contractors who need basic orientation. It shows names, titles, and departments, possibly with a direct contact for their point of entry. Keep it simple. Use anonymization if needed, and apply the sharing and expiration policy required by your organization.

The Hiring / Recruiting View

Recruiters can use this view to show the team a candidate would join: the specific team, its manager, and the peers they would work with. Optional interests or working context can add useful detail, but only include information approved for that audience.

Test the views with a realistic change

Use a small scenario before you publish anything. Imagine a 120-person team preparing for a reorganization:

1. One manager changes, one person leaves, and one new team is created.
2. Update the source dataset once, then check which views should change.
3. Ask a leader, an employee, and an external-facing colleague to complete one lookup each.
4. Confirm that each person sees enough context for the task and none of the fields they should not see.
5. Record the time, questions, and permission failures. Those observations become your maintenance baseline.

This test is more useful than promising a fixed time saving. A single-source workflow may reduce duplicate editing, but it still needs review after real changes and it may not fit teams with complex access rules.

Getting From Multiple Files to One System

If you are currently in the “three files on the desktop” situation, use a safe consolidation path:

1. Inventory every version in shared drives, email attachments, slide decks, and team spreadsheets.
2. Map each version to an audience and record which fields it exposes.
3. Choose the canonical dataset and document its owner and review triggers.
4. Build the views, then test each one with someone from that audience.
5. Archive the old files, update shared links, and keep a record of what was retired and why.

The hidden cost audit helps you measure the work before and after the change. If the source data is already in a spreadsheet, the import workflow gives you a practical starting point.