{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/0f45b9d205c14d7eb2f2479d96a30dc2\" frameborder=\"0\" width=\"1280\" height=\"960\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":960,"width":1280,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":960,"thumbnail_width":1280,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/0f45b9d205c14d7eb2f2479d96a30dc2-c16a5fd601083cc2.gif","duration":127.637,"title":"Fixing JSM Space Access Permissions","description":"This Loom explains why a user may not be able to access JSM features in a Jira Cloud space. In Space settings under Access, the viewer should confirm that the user (example Cassie) has a JSM license assigned by an admin and also has an appropriate role in the specific space. It notes that having only the license may not be enough if the role configuration differs. To troubleshoot, the viewer should check Space permissions and verify the role, such as Service Desk Team, includes the needed permission, and compare with roles like Space Agent."}