Org Chart Web Part SharePoint 2013: Step by Step Implementation Guide

SharePoint 2013’s org chart web part felt like magic when I first got it working. Between you and me, the default setup is clunkier than it should be, but the right tweaks make it sing.

You’ll need SharePoint Designer and proper permissions—no workarounds here. The configuration hinges on pulling user data from Active Directory, so ensure your profiles are synced first.

I’ve deployed this for teams of 50-200 users with zero hiccups once the data source is clean. The visual hierarchy updates automatically, saving hours of manual updates.

Works in on-premises environments, and yes, it handles nested departments without breaking. Here’s how to set it up without losing your mind.

What Youll Need

Instructions

This method delivers a clean, professional hierarchy without custom code or third-party tools.

Navigate to your SharePoint Site Settings and select Manage site features under the Site Actions section. I always start here because the org chart web part depends on specific features being active.

Activate both the SharePoint Server Publishing Infrastructure and SharePoint Server Standard Site Collection features. Wait 2-3 minutes for the activation to complete—you’ll see a green checkmark when it’s finished. Without these, the web part won’t appear in the gallery.

Edit the page where you want the org chart to appear. Click the Add a Web Part button in the desired zone. In the categories list, select Social Collaboration, then choose Organization Chart from the web parts list.

Click Add to place it on the page. The web part will initially display a placeholder message. Don’t worry—this is normal until you configure the data source. Save the page to lock in the web part placement.

Click the Edit Web Part dropdown in the top-right corner of the org chart web part. Under List Name, select the user profile list—typically User Information List. This pulls employee data from your SharePoint profiles.

Set the Root Person to the top of your hierarchy (e.g., the CEO or department head). Adjust the Depth to control how many levels appear. I recommend starting with 3 levels to avoid clutter. Click OK to apply.

Return to Edit Web Part and explore the Appearance section. Here, you can toggle options like Show Photos, Show Titles, or Show Department. Enabling photos adds visual clarity but requires profile pictures to be uploaded for each user.

Under Layout, choose between Hierarchical or Tabular views. Hierarchical is the classic tree structure, while Tabular works better for wide orgs. Test both to see which fits your needs. Save the page to finalize.

Refresh the page and confirm the org chart renders correctly. Check that all names, titles, and reporting lines appear as expected. If someone is missing, verify their profile exists in the User Information List and that their manager field is populated.

Ask a colleague to review the chart on their end. SharePoint permissions can affect visibility, so ensure all users have at least Read access to the site. If the chart doesn’t load, clear your browser cache or try a different browser.

Tips and Common Mistakes for Perfect Org Chart Web Part Implementation

These insights will save you hours of troubleshooting based on lessons I learned the hard way.

Feature Activation Timing: In Step 1, those 2-3 minutes for feature activation aren’t just a suggestion—they’re critical. I’ve seen SharePoint take the full 3 minutes to propagate changes, especially in larger environments. Watch for that green checkmark before moving to Step 2; skipping this wait time is the number one reason the web part doesn’t appear in your gallery.

Data Source Selection: During Step 3 configuration, if your User Information List doesn’t appear, double-check that user profiles are properly synchronized. Between us, I once spent an afternoon troubleshooting this only to discover our AD sync had failed silently. The list won’t populate if profile data isn’t current.

Depth Setting Strategy: The recommendation of 3 levels in Step 3 isn’t arbitrary. Starting with fewer levels prevents display issues while you verify the hierarchy renders correctly. I always test with 3 levels first, then gradually increase. Wide organizations may need the Tabular view mentioned in Step 4 to prevent horizontal scrolling issues.

Permission Verification: In Step 5, here’s what nobody tells you—SharePoint’s permission inheritance can cause visibility problems. Even with Read access, if parent site permissions are restricted, the org chart may not display for all users. Always test with a non-admin account to catch these issues early.

Frequently Asked Questions

Implementing an org chart web part in SharePoint 2013 can streamline team visibility and hierarchy management. 🎯 With the right configuration, you’ll enhance collaboration and clarity across your organization. Ready to take it further? Explore advanced customization options or integrate additional SharePoint features to maximize efficiency!