-
Notifications
You must be signed in to change notification settings - Fork 0
feat: consider access-control gating for cost_incurred activity events #839
Copy link
Copy link
Closed
Labels
prio:lowNice to have, can deferNice to have, can deferscope:smallLess than 1 day of workLess than 1 day of workspec:apispec:securityDESIGN_SPEC Section 12 - Security & Approval SystemDESIGN_SPEC Section 12 - Security & Approval Systemtype:featureNew feature implementationNew feature implementationv0.5Minor version v0.5Minor version v0.5v0.5.3Patch release v0.5.3Patch release v0.5.3
Description
Context
The cost_incurred activity event exposes model names, token counts, and per-call USD costs in its description field. This data is visible to all users with OBSERVER role or above via GET /api/v1/activities.
Question
Should cost/financial data be gated behind a higher role (e.g., MANAGER/CEO) rather than OBSERVER? This is a design decision, not a code bug.
Options
- Gate
cost_incurredevents behindrequire_write_access(manager/CEO only) - Strip model name and exact cost from descriptions for observer-role users
- Keep current behavior and document that cost data is visible to observers
Source
Found during PR #832 review (security-reviewer agent).
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
prio:lowNice to have, can deferNice to have, can deferscope:smallLess than 1 day of workLess than 1 day of workspec:apispec:securityDESIGN_SPEC Section 12 - Security & Approval SystemDESIGN_SPEC Section 12 - Security & Approval Systemtype:featureNew feature implementationNew feature implementationv0.5Minor version v0.5Minor version v0.5v0.5.3Patch release v0.5.3Patch release v0.5.3