Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
SharePoint org charts are one of those “small page element, big clarity” features. Done right, they give employees an instant view of reporting structure—without hunting through emails, PDFs, or outdated org posters.
This guide shows multiple ways to create and publish an org chart in SharePoint, starting with the native Org Chart web part workflow (when your tenant supports it), then covering reliable alternatives like Visio, Power BI, Power Apps, and third-party web parts.
As an Amazon Associate I earn from qualifying purchases.
By the time you’re done, you’ll know what prerequisites must be true, exactly where to click in SharePoint, and what to fix when the chart is empty, broken, or inaccurate.
What an Org Chart in SharePoint Actually Means
When people say “Create Org Chart in SharePoint,” they typically mean one of two things: an interactive org chart embedded into a modern SharePoint page, or a diagram (image or interactive file) placed on a page for viewing.
Popular on Amazon
The key difference is data automation. Interactive web-part solutions usually pull hierarchy data from Microsoft 365 identity data (like manager relationships), while diagram-based approaches (Visio) require manual updates.
Prerequisites (So the Chart Can Build Correctly)
Org charts depend on a hierarchy source. The most common source is Entra ID (formerly Azure AD) where each user has a Manager attribute and often a Department or Job title. If your hierarchy data is missing or inconsistent, the chart will be empty or incorrect.
Prerequisites checklist
- Microsoft 365 tenant with SharePoint Online (for modern-page embedding and most web parts).
- Entra ID manager data set correctly for each user in the chain you want to display.
- Permissions: you need permission to edit the SharePoint page and to view the people data used by the org chart.
- A modern SharePoint page (org chart web parts are typically supported on modern pages, not classic pages).
Verify manager data in Entra ID
At minimum, ensure the manager field is populated for relevant users. For best results, keep job/department metadata consistent so filters and labels (if available) behave predictably.
If you’re using a web part that reads from user profile/hierarchy data, also make sure any required directory sync has completed.
Method 1: Build an Org Chart Using the SharePoint Org Chart Web Part
This is the closest thing to a “native” experience: add an Org Chart web part to a SharePoint page and configure it to display the hierarchy.
Because availability varies by tenant and product updates, you’ll first confirm whether the web part exists and what data source options it offers.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsCheck availability and permissions
In many tenants, the org chart web part is discoverable inside the web part catalog. If it’s not present, you can still use alternatives (Visio, Power BI, Power Apps, or a third-party web part).
- Use a user account with permission to Edit the SharePoint page.
- If you’re unsure about web part availability, ask your SharePoint admin whether an “Organization chart / Org chart” web part is allowed for your site.
Add the web part to a modern SharePoint page
- Go to your SharePoint site.
- Open the page where you want the org chart.
- Click Edit (top-right) to enter edit mode.
- Click the + (Add a web part) button.
- In the search box, type Organization chart or Org chart.
- Select the Organization chart web part.
Select the data source and hierarchy settings
When the web part loads, you’ll typically see configuration controls for the hierarchy scope (for example: “Show reports for” or “Starting user” / “Root node”), plus formatting options.
Use the available selectors to choose where the chart begins. Common options look like:
Also popular on Amazon
- Root person (the CEO, your department head, or a specific manager)
- Depth (how many levels down the chart shows)
- Filters (often by department or job group, if supported)
If the org chart is based on Entra ID hierarchy, the chain depends on the Manager attribute being set correctly. If you see only isolated nodes, manager links are usually the cause.
Style, size, and interaction options
Many org chart web parts provide controls for how much space the chart uses and how it behaves when users click nodes.
- Layout: tree orientation (left-to-right vs top-to-bottom), node spacing
- Node content: show name only vs name + title + department
- Readability: scaling, font size, and maximum columns
For large teams, prefer fewer levels (depth) to keep the page usable on laptops and mobile.
Publish and test
- Verify the chart renders correctly: click a few people nodes to confirm details appear (if supported).
- Check that it loads for a standard user account (not just your admin).
- Click Publish (top-right) if you enabled draft/publishing.
If the chart doesn’t load for certain users, permissions or directory access rules may be blocking the underlying data.
Method 2: Use Microsoft Visio (Diagram First, Then Embed)
If you need a guaranteed visual that never “breaks” due to hierarchy sync delays, Visio is a stable approach. It’s also ideal when you want strict control over layout and labeling.
Create the org chart in Visio
- Open Visio and start a new file.
- Create an org chart using org chart shapes (depending on your Visio version, you may find templates for organizational charts).
- Populate names, titles, and reporting lines manually or via data import if your setup supports it.
For readability, group by department sections and keep the root node centered. In org charts, clutter is the enemy—show only levels employees actually need.
Publish to SharePoint (file + embed)
- Upload the Visio file to a SharePoint document library (for example, Shared Documents or a dedicated Org Charts library).
- Create or edit a modern SharePoint page.
- Use the Files or Document web part to display the Visio file, or embed a preview image.
For best results, also export a static PNG/PDF version so users can view it even if the interactive Visio preview isn’t available to them.
Common limitations of diagram-based org charts
- Updates require a manual refresh process (unless you automate Visio generation externally).
- Charts don’t automatically reflect Entra ID changes the way hierarchy-based web parts may.
- Large charts can become hard to maintain visually.
Method 3: Power BI Organizational Chart Visual (Interactive via Embedded Report)
Power BI’s org chart visual can generate an interactive hierarchy based on your data model. This is a strong option if you already use Power BI and want a clean, filterable experience.
Prepare data for the hierarchy
At minimum, you need columns that link each person to their manager. A common structure is:
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Also popular on Amazon
| Column | Example value | Purpose |
|---|---|---|
| PersonName | Ana Rivera | Node label |
| PersonId | e3f2c9… | Stable key |
| ManagerId | 91aa0b… | Parent/manager relationship |
| Title | Engineering Manager | Optional node info |
| Department | Engineering | Filtering/grouping |
You can source this from Entra ID exports, HR systems, or a curated table maintained by HR/IT.
Create the Power BI visual
- Open Power BI Desktop.
- Load your hierarchy data into a table.
- Create or select the organizational chart visual.
- Map the fields: node labels (person name), parent relationship (manager id) and optional fields (title/department).
Pay attention to the “root” behavior. Most visuals expect a chain where top-level nodes have blank or null manager values.
Embed the report on a SharePoint page
- Publish the report to the Power BI service.
- Open your SharePoint site and create/edit a modern page.
- Click + and add the Power BI web part.
- Choose the published report and the specific page/visual you want.
- Save and publish the SharePoint page.
Make sure the audience has access to both SharePoint and the Power BI workspace/report. If not, the web part will show blank or “not authorized.”
When this method is the right call
- You need filters (department, location, title).
- You already maintain a trusted HR hierarchy dataset.
- You want consistent visuals across devices with interactive drill behavior.
Method 4: Custom Org Chart with Power Apps (If You Need Advanced Logic)
Power Apps is the best route when you need custom workflows: editing nodes, role-based visibility, approvals, or automated updates from multiple sources.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Data model options (Entra ID vs Lists vs Dataverse)
- Entra ID: easiest for “read-only” identity hierarchy, but not designed for frequent HR edits.
- SharePoint Lists: simple setup; good if your org changes are moderate.
- Dataverse: more structured; better for enterprise-grade governance.
Most teams build a “People” table and a “ReportingLines” relationship so the UI can enforce rules cleanly.
Build the canvas app screen
- Create a canvas app in Power Apps.
- Design a screen that displays nodes and draws connections (implementation varies by your control strategy).
- Implement hierarchy traversal based on manager-to-employee relationships.
- Add search (by person name) and filters (department/location).
This is more work up front, but it’s flexible when you need features a standard org chart web part can’t provide.
Publish to SharePoint
You can embed or link to the Power App from a SharePoint page using standard embedding/links supported by Microsoft 365. In practice, most teams add a button and a preview/link for the app.
Confirm that users’ Power Apps permissions align with your desired read access.
Free tools Windows power users keep installed
One-click scans. No signup required.
Maintainability and governance notes
- Define who updates the source data (HR, IT, department admins).
- Set owner and review cadence (for example, monthly checks or after org events).
- Log changes if you support editing.
Method 5: Third-Party Org Chart Web Parts
Third-party org chart web parts can fill gaps when the native experience isn’t available in your tenant, or when you need features like deeper expand/collapse, better visuals, or custom templates.
Also popular on Amazon
How to evaluate an org chart web part
- Data compatibility: does it read from Entra ID, SharePoint lists, or a custom dataset?
- Permissions: does it respect SharePoint audience targeting?
- Mobile layout: can users still read it on an iPhone or iPad?
- Performance: does it throttle or simplify for large hierarchies?
- Support and update cadence: check the publisher’s release history (for example, via Microsoft AppSource listings).
Practical install checklist
- Confirm the web part works on your SharePoint plan (Online vs Server).
- Verify you can access it by name in the web part picker.
- Test with a small subset of your org first (10–50 users) to validate manager links.
- Validate rendering speed and page load time.
If you can’t test in a staging environment, take a snapshot of the page structure before adding it so you can roll back quickly.
Troubleshooting: Org Chart Won’t Build or Looks Wrong
When an org chart fails, it’s almost always data quality, permissions, or missing configuration. Use the steps below to narrow down the cause fast.
Chart is empty
- Verify the web part’s root person/starting node is set (blank root commonly results in no nodes).
- Check Entra ID manager relationships for the expected chain. If the root has no direct reports (according to the directory), you’ll see nothing.
- Confirm your account can view the underlying people data used by the org chart.
- Wait for sync/propagation windows after manager changes (directory updates aren’t always instant).
Wrong reporting lines
Wrong lines usually means the manager chain in the hierarchy source doesn’t match the organization’s real structure.
- Pick 2–3 employees and compare their manager values in Entra ID (or your source dataset) against what HR believes is correct.
- Look for multiple manager assignments, outdated manager records, or swapped reporting lines.
- Confirm that the chart depth is high enough to show the chain you expect.
Names show up but manager chains break
This is typically caused by a partial hierarchy. For example, Employee A might have a manager set, but Employee B (the supposed manager) might be missing a manager link or has incomplete metadata.
Fix by ensuring every intermediate node has correct reporting data, not just the leaves.
People appear multiple times or duplicates
- Check if your hierarchy source includes duplicates due to aliases or stale accounts.
- If you’re using a Power BI data table, verify uniqueness on the key field (for example, PersonId).
- In diagram approaches, ensure you didn’t reuse the same person node shape multiple times without a consistent naming rule.
Web part is missing entirely
If you can’t find “Organization chart” in the web part picker:
- Confirm you’re editing a modern page.
- Check whether the web part is restricted by admin policy or isn’t enabled for your tenant.
- Try searching with alternate keywords: Org, Organization, or the publisher’s exact name if it’s a store app.
If the web part can’t be enabled, use Method 2 (Visio) or Method 3 (Power BI) as dependable substitutes.
Recommended Free Tools
Performance issues with large orgs
- Reduce chart depth (fewer levels) and consider filtering by department.
- Split a huge chart into multiple pages (one per division) rather than one all-company diagram.
- For Power BI, limit the number of nodes by using filters or incremental data loads where possible.
Security, Governance, and Data Accuracy
Org charts are identity data, so treat them like sensitive employee information. A chart that’s visible to everyone can still expose internal reporting relationships that some teams restrict.
Who can view the hierarchy
Decide whether your org chart should be broadly visible or limited. In many setups:
Also popular on Amazon
- Use SharePoint page permissions (audiences/groups) to restrict access.
- Ensure the org chart data source (Entra ID hierarchy, Power BI dataset) aligns with the same audience controls.
How to keep hierarchy data current
Manager changes happen constantly. To keep the chart accurate, set a routine:
- After HR updates, validate manager relationships for affected departments.
- Set an internal owner (often HR Ops or IT) for directory hierarchy quality.
- Schedule a review cadence (for example, monthly for stable orgs; weekly for rapidly changing teams).
Audit and change control
If you build a custom app (Power Apps) or maintain a dataset (Power BI), keep a clear audit trail of hierarchy changes. That helps when employees report that “my manager changed but the org chart didn’t.”
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCommon Mistakes (That Waste Hours)
- Setting only leaf employees’ managers while leaving intermediate nodes incomplete.
- Choosing a root node that doesn’t have direct reports (or using an outdated CEO/department head account).
- Using classic pages when the org chart web part supports modern pages only.
- Forgetting permissions—you can build it as an admin and still have it fail for real users.
- Overloading the chart with too many levels, making it unreadable on iPhone and iPad.
FAQs About Create Org Chart in SharePoint
Can I create an org chart in SharePoint without Entra ID manager data?
Yes. If you can’t rely on Entra ID hierarchy, use Visio (manual), Power BI (from your dataset), Power Apps (from Lists/Dataverse), or a third-party web part that supports custom data sources.
Why does the org chart show my team but not the chain above me?
Most org chart solutions show either a configured depth or a root-based slice. Increase depth, or reconfigure the starting/root person to include managers above you.
How long does it take after changing a manager in Entra ID?
Directory and hierarchy-driven web parts don’t always reflect changes instantly. Expect a propagation window that can vary by tenant and sync cycles. If it’s been more than a day, re-check manager values and permissions.
Will the chart respect access controls?
It depends on the method. SharePoint audience permissions typically control page access, while the underlying data source (Entra ID hierarchy or Power BI dataset) can add additional constraints. Test with at least one non-admin account.
Recommended Free Tools
What’s the best method for a very large org?
Split into departmental charts and limit depth. For interactivity and filtering, Power BI often performs well when paired with targeted filters. For simplicity, a Visio diagram per division is predictable and easy to publish.
Bottom Line
If your tenant supports it, using the SharePoint Org Chart web part is the fastest way to create an interactive org chart that stays aligned with Entra ID hierarchy data. When that’s not available or when you need strict control, Visio and Power BI are dependable alternatives.
The right choice comes down to how often the org changes, who owns hierarchy updates, and whether you need interactive drill-down vs a stable visual. Get the data and permissions right first, then publish the chart on a modern SharePoint page for maximum usability.
