CSV and SharePoint List Sources
Org Chart reads one SharePoint list or one .csv file that you control, as the signed-in user. There is no Microsoft Graph use, no directory wiring, and no HR system connection.
The source must already be a flat list or CSV that contains the people and relationship data you want rendered. The product does not join multiple HR exports, manage positions, render vacancies, or apply interim-manager rules.
SharePoint list
Under Data, set Data source type to SharePoint list. Pick Data source (list) and a View. The view's filter, columns, and item limit apply before the chart sees rows. A reader only sees people their SharePoint permissions allow.
Manager lookup — SharePoint list only is available on lists. It is the format used by the Zenpo Employees starter template and by compatible lists whose Manager column points at rows in that same list.
CSV file
Under Data, set Data source type to CSV file. Pick a Document library in this site and a CSV file.
.csvonly — not XLSX, not TXT.- First row must be headers.
- File-level delimiters are comma or semicolon, detected automatically. That is the column delimiter for the file. It is not the manager-ID separator inside a cell. Manager-ID cells support comma, semicolon, or pipe. See Map Person ID and Manager ID.
- CSV never offers Manager lookup — SharePoint list only. Use one of the four ID-based formats.
Refreshing the data means replacing the file in SharePoint. The web part reads whatever the file contains when it loads.
File rules and CSV error strings are on Use an HR System (HRIS) CSV Export with Zenpo Web Parts.
Source size
The cap is 5,000 source rows. A larger source is refused, not truncated. The message is This roster contains more than 5000 people. Refine the source or use a smaller organizational scope. Repeated-row relationship formats can contain more rows than unique people, so a file of 5,001 relationship rows is refused even if it describes fewer people.