0
Allow me to define which roles or teams have access to session replays
Source: getsentry/sentry#127205 · opened by @aellett
Problem Statement I've turned on session replay and I'm trying to roll it out to our team, but the current permissions scope makes that a little tedious. Turned on hasGranularReplayPermissions at the org level and selected a list of users for the replayAccessMembers list, but I'm worried that that's going to get cumbersome to manage as we grant more access. I'd like to be able to grant/remove access to certain groups of people all at the same time, instead of just one at a time. Solution Brainstorm It seems to me like it would make sense to be able to grant access to replay data to a particular team or user role through the mechanism that I'm currently using to grant access to individual users. Eventually, I'd love to be able to manage access to this data remotely through some type of okta integration or something, so that if a member of my team needs to have access removed (if they move to a different team, or we judge that their access window is…
No pledges yet. Be the first to back this.
Comments
Similar requests
Show total match count on Replays list page
0 votes · 0 comments
Namespace collision between Session Replays and FileBlobs prevents S3 Lifecycle Management
0 votes · 0 comments
Inbound filter for session replay
0 votes · 0 comments
Add a new endpoint to add/remove a member from `replayAccessMembers`
0 votes · 0 comments
Crash-free session and user metrics should break down by environment and release rather than requiring project separation
0 votes · 0 comments
No comments yet.