One question can reach three people and give three different answers, each of them correct for the person who asked.
Five steps; your rights travel inside the query, into every source it reaches.
Access starts at sign-in. Single sign-on brings the roles your identity system already holds, so a planner who moved from one site to another carries the rights the company gave them, with the change recorded there.
Juno then reads the question the usual way and collects two sets of rules: the rows this person may read, such as plants, categories, business units and suppliers, and the columns their roles allow, such as price, standard cost or a contact.
The rules are built into the query itself. When a question reaches three systems, the same filter goes into each part, so the joined answer carries one scope. A person cleared for two plants receives a total for two plants.
The answer then states what applied. The access line names the scope, and where a role protects a column the answer names the column and the role that holds it, so a reader knows what exists and whom to ask.
The buyer sees two plants and two categories, because that is the purchasing area he owns.
Delta Fasteners delivered 486 lines in your categories last quarter, 36 of them after the date they confirmed, a late rate of 7.4%. Spend came to $1.24M.
| Plant | Lines due | Late lines | Late rate | Spend |
|---|---|---|---|---|
| 1210 Penang | 312 | 26 | 8.3% | $806,400 |
| 1220 Penang | 174 | 10 | 5.7% | $433,600 |
Here are the ten latest lines with the contract unit price beside the price on the order. Two lines carried a price above the contract, both on the September deliveries.
| The person | Rows they may read | Columns their roles allow | The answer to the same question |
|---|---|---|---|
| D. Okafor · buyer | Fasteners and metals at plants 1210 and 1220 | Every purchasing column, the contract unit price among them | 486 lines due · 36 late · 7.4% · $1.24M |
| J. Ridley · supply chain director | Every plant and every category | Delivery and value columns; the price column sits with purchasing | 1,412 lines due · 104 late · 7.4% · $3.86M |
| Delta Fasteners Ltd · supplier partner | The order lines that belong to this supplier | Quantities, dates and their own performance | 1,412 lines due · 104 late · 7.4% |
| A. Novak · data lead | The registration record, with sample values | Table and column names, and the time each was last read | The seven tables behind the answer, with their freshness |
Four chairs, one sentence, four scopes. Each figure is correct for the person who asked it. Showcase estate.
Three chairs, one definition of a late line, three scopes.
1,412 lines were due across four plants, 104 of them arrived after the confirmed date, a late rate of 7.4%. Spend came to $3.86M.
The contract unit price belongs to the purchasing role, so D. Okafor and the category managers hold that column.
1,412 of your lines were due last quarter and 104 arrived after the date you confirmed, a late rate of 7.4%. July was your strongest month at 3.1%.
Quantities, dates and your own performance are in scope for this account. Prices and other suppliers belong to the purchasing roles.
The director covers four plants and every category, so his total is the company total: 1,412 lines and $3.86M. The late rate reads 7.4% in both chairs, because both answers measure the same way over the same confirmed mapping.
Figures agree between chairs because the meaning is shared. Two people comparing their screens find one definition of a late line and one definition of spend, with the difference sitting only in the scope each of them holds.
A supplier partner account reads the rows belonging to that supplier. Delta Fasteners sees its own lines, the dates it confirmed and its own performance, which gives both sides one shared picture of the record.
The same account holds prices and other suppliers outside its scope, and the answer says which parts belong to the purchasing roles. The supplier reads the performance and asks their buyer about the rest.
An answer that names what a role protects is more useful than an answer that stays quiet.
The contract unit price belongs to the purchasing role. Your roles cover delivery performance and spend across every plant, and the rest of the table is complete.
D. Okafor and the category managers for fasteners can share that line with you.
Stating the protected column is a deliberate choice. A reader who receives a smaller table with silence beside it learns little; a reader who is told which column exists and who holds it can act within a minute. Buyers routinely share a price line once they know it was asked for.
One question, one line in the record, whichever chair it came from.
| Time | Who asked | The question | Scope applied | Rows returned | Columns a role protected |
|---|---|---|---|---|---|
| 14:02 | D. Okafor · buyer | Delta Fasteners last quarter, performance and spend | plants 1210 and 1220 · fasteners and metals | 486 | every column allowed |
| 14:06 | J. Ridley · director | the same question | every plant · every category | 1,412 | contract unit price |
| 14:20 | Delta Fasteners Ltd · partner | the same question | order lines of this supplier | 1,412 | spend and price |
| 14:24 | A. Novak · data lead | which tables hold the supplier confirmed date | the registration record | 7 | every column allowed |
Each line holds the time, the person, the question as typed, the scope that applied, the query that ran, the row count and any column a role protected. An auditor reading the four lines above sees why two answers about one supplier differ.
The records sit in the same audit trail as agent actions and approvals, under the retention period your estate sets.
This is what lets a company open ChatLima to hundreds of people. The rules live with the data and the roles, the record lives with the platform, and a review of who read what takes one query.
Showcase estate.
The cancellation work of Wednesday morning put Delta Fasteners in front of three people at once. D. Okafor asked how the supplier had performed in his categories, and read 486 lines with the contract unit price beside them.
J. Ridley asked the same sentence from the director’s chair and read the company total of 1,412 lines and $3.86M, with a line stating that the price column sits with purchasing. Delta Fasteners asked from their own account and read their 104 late lines. All three answers came from one mapping, and all three left one record.
The terms, the sources, the elapsed time and the query beside the answer, and the lineage of a single number.
From your identity system and the roles it holds, brought in at sign-in, together with the row and column rules set on the registered tables. Juno applies both to every answer.
Yes. The filter goes into each part of a question that reads several systems, so a joined answer carries one scope across SAP, Oracle, the planning suite and the lake.
It names the information in business words, names the role cleared for it, and gives the rest of the answer whole. A reader learns what exists and whom to ask.
A partner account reads the rows that belong to that supplier. Their lines, dates and performance travel; other suppliers stay outside the scope of the account.
For the retention period your estate sets, beside the rest of the audit trail. Each record names the asker, the question, the scope, the query and the row count.
Each one builds on the one before it.
Reads your rows in place.
Connect and move ↗One record per real thing.
Master and govern ↗Apps for every decision.
Operate and decide ↗Asks and acts, at your level.
Ask and act ↗Bring two systems and one decision your planners make every week. In the first week we register the data, confirm the mapping with your team, answer your questions in ChatLima and run the first agent at the level you choose.