2
KH
Permission model

Visibility follows the org chart

There is no separate permissions system to maintain. Who can see whom is derived entirely from the reports_to lines in Odoo — so access stays correct the moment the org changes.

Source of truth
reports_to
Personas
3
Mapped people
10

Visibility by persona

what each persona can see
AW
Individual
e.g. Ahmed Wael
Own work visible
Direct team hidden
Whole org hidden

Sees only their own signals, scores, and plan. Nobody is judged against peers they can't see.

KH
Manager
e.g. Khaled Hesham
Own work visible
Direct team visible
Whole org hidden

Sees their own work plus everyone who reports to them — exactly the reports_to subtree, nothing wider.

OS
Executive
e.g. Omar Shouman
Own work visible
Direct team visible
Whole org visible

Sees org- and unit-level rollups. Drill-downs into individuals are read-only and always logged.

How a chain derives access

a real reporting line

Each person above another in this chain can see everyone below them — and no one to the side. Read the arrows as “reports to”.

HM
Hussein Mohieldien
CEO
sees 4 below
AA
Ahmad Alfy
CTO
sees 3 below
OS
Omar Shouman
Cloud & AI Director
sees 2 below
KH
Khaled Hesham
AI Manager
sees 1 below
AW
Ahmed Wael
Senior AI Engineer
sees own work only

Who-sees-whom rules

Downward only

You see your reports and their reports — never your manager's other branches or your peers.

Team rollups

Managers get aggregate team scores; individual drill-down is explicit and logged.

Org is aggregate

Executives see unit-level portfolio health, not a feed of every person's day.

No lateral access

Same-level colleagues cannot see each other's signals or scores by default.

Two-way visibility

Anyone viewed is notified; the access log records viewer, scope, and duration.

Auto-reconciles

Change a reporting line in Odoo and visibility updates on the next sync — no manual grants.