Skip to content
Let ideas be heard and improvements last.
Gemy

Bringing the organisation into the system: unit, title, role and person

In brief

The hierarchy is the company's data, not the code's. What to watch for order, naming and delegation when moving the unit tree, roles and people into the system.

23 October 2026 · 1 min read

Sample company · demo dataOrganisation chart: units and owners
Organisation chart

The system knows no organisational layer, title or role by itself; the company builds them all. It may be plant–department–line or region–store.

Four concepts

  • Unit: a node in the tree (plant, department, line — you name it).
  • Title: the person's job title.
  • Role: a responsibility used in flows (e.g. unit owner, quality approver).
  • Person: an employee in a unit; can hold several roles.
Sample company · demo dataOrganisation screen: the layers the company defines
Organisation screen

Why is a role separate from a title?

Approval flows bind to roles, not titles. When someone changes title or leaves and the role is given to someone else, the flow goes to the right person automatically.

Sample company · demo dataRoles and permissions: system roles and the company's own roles
Roles and permissions

The organisation chart is drawn from this structure; the role distribution screen shows roles left empty.

You may copy and share this article with attribution (Gemy, https://www.gemydigital.com/en/blog/organizasyonu-sisteme-tasimak).

Related posts

Cookies

Essential cookies are needed for the site to work. Analytics cookies load only if you allow them; declining is as easy as accepting. You can change your choice at any time via the footer link.

Cookie policyPrivacy notice