Friday, 3 July 2026, 10:59 AM
Created by: Ruvenss G. Wilches
The chart is only as good as your Team Management data. Before you build, make sure staff have correct job titles and profile photos, and that people who have left are deactivated. Good source data means a good chart with zero extra effort.
Place the most senior person first, near the top of the canvas, then add the next level below them and connect the lines downward. Working top-down keeps the layout readable and makes the reporting lines obvious.
The app models a standard single-manager hierarchy: each person reports to exactly one supervisor. If someone genuinely has two managers, choose the primary one for the reporting line and rely on team tags to express the secondary relationship.
Reporting lines show the vertical hierarchy; teams show the horizontal one (departments, squads, projects). Turn on “Show teams” so people can see both at once, and manage the membership in the Teams module rather than trying to encode it in the chart.
When someone leaves, deactivate them in Team Management — do not try to keep the chart tidy by hand. The app removes deactivated people automatically and reconnects their reports to the next supervisor up, so the hierarchy never breaks.
Positions and reporting lines are only stored when you click Save. After a reorganization, save so that every employee sees the new structure from their profile.
Grant the “Design & edit the company organigram” permission only to the people who should shape the structure (typically administrators and HR). Everyone else still sees the finished chart from their own profile, which is usually exactly what you want.
Leave breathing room between cards, avoid crossing lines where possible, and use the Fit button to check the whole chart at a glance. A chart people can read is a chart people will use.