Oversight
Every promise on the other pages is worth what this one is worth.
A vendor can say anything about what they do not capture. The only claim a team can actually check from the inside is a record of who has been looking at them — because they can compare it against the meeting where a manager quoted their week back at them.
So this page exists, and nothing can be left off it.
What is recorded
Four different ways of looking, all of them written down.
Opening somebody else's visit. Pulling the team's week — one row per rep whose plan appeared. Loading the aggregate dashboard — one row per rep whose numbers were rolled into it, even though the dashboard shows nobody individually. And opening a single rep's own numbers.
Each row carries who looked, their role as it was at the time, what they opened, and when. Snapshotting the role matters: somebody promoted next year should not retroactively have been a director when they looked.
- Views of your own data are dropped —
You already know you looked at your own week, and a log full of that is a log nobody reads.
- Background jobs are skipped —
An overnight sweep is not a person and does not belong on a page about people.
- Writing a row can never break a screen —
With the trade-off stated: losing an audit row is bad, and crashing a manager's dashboard because the audit table hiccuped is worse.
- The filter on the page is cosmetic, and says so —
A comment in the product spells it out — the reader can narrow the view for readability, and the design forbids the server omitting anything.
- No addresses are shown —
They are captured for security review and deliberately not rendered, because a raw address on this page is more alarming than useful.
The other half
The manager is told before they look.
Opening somebody else's week retitles the screen and prints it plainly: this view is logged, and the rep will see your name and the week you looked at.
Which changes the nature of the act. Not a prohibition — a manager checking a team's coverage is doing their job — but the difference between checking and watching, made visible to both sides at the moment it happens.
›Can an administrator switch this off?
No. There is no setting for it, and there is no filter on the server side. That is the point — a trust contract with an off switch is a preference.
›Can a manager see the team's access log?
The capability exists and has no screen today, so in practice the audit is the rep's page. Which is the right way round for this feature.
›Is this the same as the platform audit trail?
No. The platform records changes across the whole product. This records reads, of one person's field data, by another person — which almost nothing records anywhere.