{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/6480b32bdfbf4e6f8bc92aa3b84bcccc\" frameborder=\"0\" width=\"2228\" height=\"1671\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1671,"width":2228,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1671,"thumbnail_width":2228,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/6480b32bdfbf4e6f8bc92aa3b84bcccc-0028e2b87b806b99.gif","duration":407.315,"title":"Granular RBAC Scopes for Telemetry Data","description":"This Loom explains how to set up granular RBAC scopes for telemetry data sources, including managing, viewing, and restricted access. It describes three telemetry scopes: managing data sources with full add, edit, remove, and query abilities (including restricted ones), and view telemetry with the ability to query unrestricted sources, while restricted requires narrower permissions. The Loom shows that each telemetry source is configured separately with no inheritance, and that access can be set via custom roles or team-based RBAC, with warnings addressed in team permissions. After a source is marked restricted, a standard user receives a permission error when querying it via Ask Incident, and the settings drawer can show who can grant the access."}