Zenpo Org Chart FAQ
Direct answers for Zenpo Org Chart. For CSV file rules and error strings, see Use an HR System (HRIS) CSV Export with Zenpo Web Parts. For structure semantics, see Hierarchy models.
Does Zenpo Org Chart connect to Microsoft Graph, Azure AD or my HR system?
No. It reads a SharePoint list or a CSV file that you control, as the signed-in user. There is no Microsoft Graph use, no directory wiring, and no connection to any HR system.
Can I build the chart from a CSV instead of a SharePoint list?
Yes. Store a .csv file in a document library in the same site, then choose CSV file as the data source type. The first row must be column headers. Comma and semicolon delimiters are detected automatically. CSV only — not XLSX, not TXT.
Can I use a Workday, ADP, SAP SuccessFactors or PeopleSoft export?
Yes, as a CSV file you export and store in SharePoint yourself. That is an HRIS CSV export workflow, not an HR system connection. Zenpo's column detection recognizes the header-naming patterns those exports commonly use, so employee-key and manager-key columns are usually proposed for you. This is column-name recognition only. Zenpo does not connect to, authenticate against, or synchronize with any HR system.
How do I describe who reports to whom?
Two ways. A Manager (lookup) column that points at rows in the same people list, or an ID + ParentID pair of key columns. CSV sources always use ID + Parent ID.
What makes someone appear at the top of the chart?
Anyone whose manager is empty is a top-level person. In ID + Parent ID mode, a blank Parent ID, or the values NO_MANAGER or -1, also means "no manager."
With Root person on Auto-detect top, the charted tree is the top-level person with the most people beneath them. Other top-level people appear in Unassigned.
Some people are missing from the chart. Where are they?
There are three causes. Check in this order.
- The chart draws one tree at a time. Valid top-level people outside the charted tree are listed by name in the Unassigned strip. Choosing a Root person does the same for everyone outside that branch.
- Rows with a structural problem are skipped and reported in Data issues: a row that reports to itself, or rows in a circular reporting loop.
- Rows the web part never received: the selected View filter and item limit apply first, and a reader only sees rows their SharePoint permissions allow.
See Fix Data Issues and Missing People.
Why did one branch break off as a separate root?
Because the manager it points at is not among the loaded rows. Often the manager's row is filtered out by the selected view. The person and their whole branch still render, as another root. The Data issues panel reports manager {key} not found — branch kept as a separate root.
Can someone report to two managers?
Yes. Use a multi-value manager column, or list several keys separated by commas or semicolons in the Parent ID cell. The first is the primary position where their own reports hang. The additional position renders as a leaf marked ⇄.
Can I export the chart as an image?
Yes, when PNG export is on, from Full tree mode. The export always draws every branch expanded, whatever is collapsed on screen. A very large chart can be refused: This chart is too large to export as an image. Set a Root person in the property pane to export one branch at a time. Setting a Root person is the remedy.
How large a roster can it handle?
Up to 5,000 people. A larger source is refused rather than truncated. A notice appears above 3,000 people. Charts read best at up to about 500 visible nodes. This Help does not promise that a 5,000-person chart will expand or export quickly.