Getting started
Configuration wizard
- Open configuration wizard
- Data source
- Views and filtration
- Design
- Templates
- Custom code
- General
- Reset configuration
HTML templates
JavaScript framework
Additional resources
- Video: Introducing Plumsail Org Chart
- Data caching
- How Org Chart pulls data from AD On-Premises
- Exclude disabled users in On-Premises
- Make sure that SharePoint has enough data
- Configuring profiles sync in On-Premises
- Exporting properties to a directory service
General
- Version history
- Licensing details
- Data protection and security
- Custom code security measures
- Billing and subscription management
Printing & Reports
- Printing organizational structure
- Generate multi-page PDF report
- Export to CSV and analyze in Excel
- Custom styles for printed Org Chart
Microsoft Teams
Display different types of employees
- Display dotted-line managers (SharePoint list)
- Display dotted-line managers (Entra ID)
- Display dotted-line managers (User Profiles)
- Display dotted-line managers (Excel/CSV)
- Display assistants (SharePoint list)
- Display assistants (Entra ID)
- Display assistants (User Profiles)
- Display assistants (Excel/CSV)
- Display vacancies
Filter and order boxes
Customize boxes and styles
- Format boxes conditionally
- Customize box HTML template and CSS styles
- Display awards and conditionally format Org Chart
- Create an Org Chart with two root managers
- Change Org Chart skin
- Localize Org Chart
Show specific user on load
- Drill down to specific box using URL parameter
- Drill down to current user by default
- Drill down to manager of user from URL by default
Manage web part size and scale
- Open Org Chart in full-screen mode on load
- Make Org Chart use full page width
- Automatically scale boxes to fit visible area
Other examples
Generate organization structure report in SharePoint and Microsoft Teams
Note
For the versions earlier than 4.x.x (including on-premises ones), please follow this instruction.
You can generate a simple and clear organizational structure report using Org Chart.
Such reports can be useful for internal informational purposes or as part of your company’s compliance with ISO 9001 or other quality management standards.
Create multi-page report
Open a site page that contains the Org Chart web part, then in the upper-right corner click the More menu and select Generate report.
Then you can:
choose the person to start the report from (optional);
specify the number of levels to collect;
select the paper size;
switch the report to landscape orientation (portrait is used by default);
enable alphabetical page sorting (by default, pages follow the hierarchy from top to bottom).
With these settings, Org Chart collects all managers starting from the selected person (or from the root ID by default) up to the specified level and places each manager with their direct subordinates on a separate report page. When the report is ready, click Download.
The generated report starts with the *Table of Contents*, making it easy to navigate large structures.
You can see all managers at the specified levels along with page numbers for their charts. All items are clickable.
Each report page contains one person and their direct subordinates. You can also use a link to navigate to the person’s supervisor.
If you are using the dynamic Modern skin that depends on the SharePoint theme, the generated report will match your theme color.
Customize footer and header
You can customize headers and footers of a generated report. The result will look like this:
Let’s review this example. Add the following code to the JavaScript step of the configuration wizard:
api.config.reportHeader = "{{Metadata.RootItemName}}{{#if Metadata.Properties.Department}} -
{{Metadata.Properties.Department}}{{/if}}{{#if Metadata.Properties.JobTitle}} - {{Metadata.Properties.JobTitle}}{{/if}}";
api.config.reportFooter = "{{Metadata.RootItemName}}{{#if Metadata.Properties.JobTitle}} -
{{Metadata.Properties.JobTitle}}{{/if}} - Reports to {{Metadata.RootItemManagerName}}";
You can use tokens like {{Metadata.Properties.JobTitle}} to access properties of a user.
JobTitle is an internal name of a user profile property or a SharePoint list column, depending on the Org Chart data source.
The example also uses an if block: {{#if Metadata.Properties.Department}} - {{Metadata.Properties.Department}}{{/if}}. This lets you check if the value is not empty and display it only when it is set.
You can skip api.config.reportFooter initialization if you only need to add information to the header.
Note
For a complete overview of exporting Org Chart in different formats and platforms, see this blog post. It applies to both SharePoint and Microsoft Teams.