An org chart that manages permissions, with AI employees on it

Friday evening. A sales rep is leaving, not in a blowup, just a better offer elsewhere. On Monday, IT sits down to shut off access: CRM, email, the shared drive, team chat, the accounting system where the rep could view invoices, the customer messaging inbox. They remember half of it and discover the other half through complaints a month later. Meanwhile the rep’s open tasks still carry their name, and nobody knows who should take them.

This is what happens when the org chart is a slide in a deck and permissions live separately inside every app. PRANUS works the other way around: the org chart manages permissions. A person has a seat on the chart, and from that seat the system knows what they’re allowed to do in every service. Remove someone from the chart and access closes everywhere in one step. And on the same chart, right next to people, sit AI employees, each with a seat, working relationships, and a daily report of what they did.

The org chart as a living canvas

In TEAMUS, the org chart is a canvas that shows the whole company: departments and sub-teams at any depth, people, open positions, and AI employees. It’s not a drawing someone updates once a year. Drag an employee’s card to another department and the system offers to process a transfer, with the HR event, the formal order, the paperwork, and a heads-up to payroll.

Relationships that mean something

A typical org chart only knows who reports to whom. But real work also runs across reporting lines. Legal assigns work to finance, and the head of quality signs off on production’s output. So TEAMUS has six kinds of relationships:

Relationship	What it grants
Manages	everything down the line: tasks, oversight, sign-off, visibility
Assigns work	assigning tasks to someone in another department
Oversees	acting as reviewer and signing off on work from outside your team
Collaborates	adding someone to a task, knowing who to ask
Covers for	taking over tasks and permissions while someone is away
Advises	serving as a subject-matter expert for colleagues and assistants

Other services read these relationships. TASKUS task management uses them to decide who you can assign work to. The personal assistant uses them to figure out who to ask. And while a manager is on vacation, the person covering gets their tasks and approvals without anyone passing around passwords.

Permissions in bundles, not one by one

Granting each person access to each app individually is a recipe for chaos. A year later, nobody remembers why an intern can export the customer database. In TEAMUS, permissions come in bundles assigned to departments.

How it works

Each service has its own access levels. In CRM, for example, there’s viewer, operator, manager, and admin. You define a bundle for a department, like “Sales: manager in CRM, operator in customer inboxes, read access to the knowledge base.” Everyone placed in that department gets the bundle automatically. You can also grant an individual a personal level on top, and it shows up as its own line instead of disappearing into a long list.

If someone works in two departments, they get the higher level for each service. Permissions flow automatically into CRM, BUHUS accounting, the CONNECTUS omnichannel inbox, and the MEMUS knowledge base.

You don’t have to start from scratch. There are 16 ready-made department archetypes, including sales, accounting, warehouse, and support, each with a typical permission bundle. Use them as-is or adjust them.

Guardrails against mistakes

• Audit log. You can see who granted what access, to whom, and when.
• Conflicting duties. The system warns you when one person would hold permissions that good practice keeps separate, such as creating a payment and approving it.
• Reconciliation. If permissions somewhere drift from the org chart, reconciliation restores them automatically.
• Structure checks. You can’t accidentally make a department report to its own sub-team. The LOGUS business rules engine checks the structure for loops like that.

Offboard once, access closed everywhere

Back to that Friday departure. In PRANUS it’s a single HR event in TEAMUS, and the system handles the rest:

1. access is removed in CRM, customer inboxes, the knowledge base, accounting, and team chat;
2. the person’s tasks go back to their team’s inbox in TASKUS, where the manager can see and reassign them;
3. customer conversations are handed to a colleague, and the system asks you who;
4. access keys for any AI agents acting on that person’s behalf are revoked;
5. payroll receives the event for the final settlement.

No “don’t forget to close” checklist. The person was set up once, and they’re offboarded once.

It works the same way in reverse. Hiring is also a single event: a seat on the chart, the department’s permission bundle, an invite to the system, plus the employment paperwork and salary set up in accounting. TEAMUS covers 16 HR events, including hiring, transfers, promotions, leave, and termination. Each one updates the structure, generates the right documents for the employer’s country, and notifies payroll in a single action.

History and job descriptions

The TEAMUS org chart remembers the past. You can open it as of any earlier date and see who worked where and reported to whom. Departing employees aren’t wiped from the system. Their history, orders, and documents stay, they simply no longer hold a seat or any access. That matters for audits and for everyday questions like “who handled this client two years ago?”

Every seat on the chart can carry a job description. The AI drafts it based on your structure, including the department, manager, colleagues, and working relationships. The finished description is issued as a document that employees must acknowledge, so a new hire knows from day one what’s expected and who to go to with questions.

AI employees on the org chart

When companies start using AI agents, those agents usually live off to the side in a separate tool, with no clear place in the structure. Nobody knows who’s responsible for them, what they’re allowed to do, or what they’re working on. In PRANUS, AI employees sit on the same org chart as people.

A seat, relationships, a report

• A seat. The support agent sits in the support team, the AI sales rep in sales. You can see at once which department it belongs to and who manages it.
• Relationships. An agent has the same kinds of relationships as people: who it reports to, who it goes to with questions, who it hands complex cases to.
• A report. An agent’s card shows what it’s doing now and what it did today, such as how many conversations it handled and how many questions it escalated to people.

Agents look visibly different from people on the chart, so nobody confuses them with staff. You configure them in AGENTUS, the AI agent console, which holds the role, behavior, tools, budget, and memory. The org chart holds only placement and relationships. One source of truth, no duplicates.

An agent gets only the access it needs

An AI agent’s access is defined by what it’s connected to: which conversation channels it handles, which knowledge bases it answers from, which tools it uses. When an agent acts on someone’s behalf, it gets that person’s permissions and nothing more. Writing to external systems requires a human “yes.”

The Assistentus personal assistant is a special case. It isn’t a separate seat on the chart. It belongs to one employee and works only for them. We explain how to build an agent without writing code in AI agents without code.

The activity map: how the company really works

The org chart shows how the company is designed. The activity map shows how it actually runs. On the same chart you can turn on a layer where arrows show who really assigns work to whom. Arrow thickness reflects the number of assignments, and color shows the share that’s overdue.

This is often where the surprises are. A department head who’s supposed to route everything turns out to assign almost nothing, because the deputy does it all. Or one person is getting work from five departments and has the most overdue tasks in the company. You won’t see that on a slide, but you’ll see it on a living chart.

Where to start

You don’t need to rebuild permissions across the whole company at once. Here’s an order that works:

1. Draw the structure. Departments, managers, people. Not the ideal version, the one you actually have.
2. Apply archetypes. Pick a ready-made permission bundle for each department and adjust where needed.
3. Add cross-team relationships, but only where people genuinely work across departments.
4. Seat your AI employees as they come online.

During a PRANUS implementation, the implementation agent does this with you. It asks questions, builds the org structure and departments, assigns permission bundles, adds employees, and brings any open questions to the executive. For how to fill an empty seat on the chart, read Hiring with an AI recruiter.

Want to see your structure turn into permissions across every service? Book a demo and we’ll map your company together.