Org Chart Enhancement

Enhancement Requests (new)
1

Is it possible to implement a new enhancement in the Origami Web Part (Org Chart) to arrange officers based on their seniority and reporting hierarchy?

Example below

image
image1191×653 46.9 KB

2

Thank you for posting this suggestion, we have a few clarifications wed like to ask you.
The web part currently reads reporting hierarchy from AD/ Entra ID as a data source.
If we were to implement the enhancement to show users by seniority, where would seniority information come from? And, would that seniority be used instead of Entra ID reporting relationship?

3

We would like to propose an enhancement to allow the filter to be configurable, so that users can select or set the attribute manually, rather than being restricted to the “Manager” attribute only.

4

Thank you for clarifying.
Would it work for you if we stored reporting relationship in a SharePoint list and someone would have to set up reporting in the list in this format (for the first time only):

| Employee1 | Manager1 |
| Employee2 | Manager1 |
| Employee3 | Manager1 |
| Employee4 | Manager2 |
| Employee5 | Manager2 |

Please note these caveats if we take this approach:

  • You’d have to manually enter all employees which might take time depending on the size of the org chart
  • You’d have to manually maintain the updates if anything changes
  • The web part would no longer read from AD/ Entra if it’s reading from the list

Would this solution work for you?

5

Thank you for the suggestion and explanation.

Unfortunately, this approach would not work for us. Our requirement is that the Org Chart continues to read directly from AD / Entra ID as the single source of truth. Manually maintaining reporting relationships in a SharePoint list would introduce operational overhead and data inconsistency, especially as organizational changes occur.

To clarify our intended enhancement:

  • We do not want to replace the existing Entra ID reporting relationship.

  • We would like the Org Chart logic to remain Entra ID–driven, but with additional configurability.

  • Specifically, we are looking for the ability to:

    • Configure which Entra ID attribute(s) are used to determine hierarchy or ordering (e.g. Manager, Job Level, Seniority, Custom Extension Attributes).

    • Allow filtering or sorting logic to be adjusted without manual data entry.

In other words, similar to how solutions like Plumsail Org Chart work(SharePoint Org Chart), the hierarchy and visualization should:

  • Continue consuming data from AD / Entra ID

  • Support customizable hierarchy logic and display rules

  • Avoid any requirement for manual data population or ongoing maintenance

Manual entry would defeat the purpose of using Entra ID as an authoritative directory, so automation and directory-based configuration are essential for us.

Please let us know if this enhancement can be implemented while keeping Entra ID as the primary data source, or if there are alternative approaches within Origami’s roadmap that align with this requirement.

6

Thank you for clarifying that, we will take a look at the possibility of adding additional options to reporting hierarchy by using Entra ID attributes. We will post an update here when ready.

7

May i know the update on this ?

8

Thank you for checking in. In your last response you mentioned that you’d like for the Origami Org Chart to continue reading from the “Manager” field in AD/Entra to determine the reporting hierarchy but you’d also like to use custom attributes from AD to determine the reporting. How would conflict be resolved if the “Manager” field has a different value for reporting hierarchy from your custom field? Can you share a use case (do you require a employee to have 2 managers or other use case)?