Org policy can hide the usage-pattern and skill-token views that read your local transcripts.
What's wrong with this entry?
Two new org-policy keys, allow_usage_transcript_scan and allow_skill_doctor_transcript_scan, control the "Usage patterns" and "Skill token counts" views. Both views are built by reading the session transcripts saved locally on the machine, so accounts under HIPAA-regulated org policy see an explanation in place of the data. Whether you get the views is decided by the account's server-supplied policy document, not by any local setting or anything in the bundle.
- The text shown in place of the breakdown is "Not shown for HIPAA-regulated organizations: this breakdown is built by scanning the session transcripts saved on this machine."
allow_usage_transcript_scanis the key behind the user-facing "Usage patterns" label, andallow_skill_doctor_transcript_scancovers "Skill token counts".- Both keys sit in the org-policy tables alongside the existing hipaa and zero-data-retention restrictions
allow_heap_dumpandallow_send_file, and are always paired with each other. - The policy resolver treats an unknown or unfetched policy map as allowed, so the default is that the views appear, except that both keys are force-denied when the compliance-taint check holds.
Not shown for HIPAA-regulated organizations: this breakdown is built by scanning the session transcripts saved on this machine., allow_usage_transcript_scan
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.236
Extra-usage panel now shows for team and enterprise accounts
Both mention usage limit
-
v2.1.236
Wrap-up hint near the usage limit is now per-plan and once per window
Both mention usage limit
-
v2.1.236
Visible notice when approaching the 5-hour usage limit
Both mention usage limit