Pathix reads the logic inside your plugins, flows and scripts, and the roles around them, so you can ask what writes a column, who can change it and what breaks if it changes.
Each answer raises the next question, so a single column can take you from what writes it to what changed since the last scan.
The platform tracks what components declare. Most writes live inside plugin code, flow definitions and form scripts.
WHICH RAISESThirteen components write it. Which people and integrations are able to?
Write access can arrive through a role, a team, a business unit or the manager hierarchy, and no single screen adds those up.
WHICH RAISESAnd if it changes, what depends on it? Credit limit's readers end after one hop in the demo environment, so Ep. 03 follows a longer chain.
Reads hide in more places than writes: a view's filter, a plugin that fires when the value changes, a flow that copies it somewhere else.
WHICH RAISESBack to credit limit. A release went in on Thursday, and on Friday the values started changing.
Each scan is compared with the one before, down to a single privilege grant or a role that moved from Local to Global.
We asked four AI models what reads or writes one column. Without Pathix, none of 36 runs found all 47 components. With the Pathix MCP connected, all 12 did.
Demo environment · a test column built for this benchmark · 2026-10-20
Pathix answered from a scan that ran before the benchmark. Its time is not in any run's time.
A read-only metadata scan of your environment that reads the logic inside the components: compiled plugins, flow definitions, workflow XAML and scripts.
How it works →A plugin, a person, a site. Nine more episodes, each starting from a different kind of subject.
Built to survive a security review. Self-hosted in your own Azure subscription, scanned by a read-only application user. It reads metadata, never business records.
Security →Your data →A 30-minute walkthrough on a pre-scanned demo environment. No access to your tenant, nothing to install.