{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/09aafca40585467a996426eb975d920b\" frameborder=\"0\" width=\"1608\" height=\"1206\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1206,"width":1608,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1206,"thumbnail_width":1608,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/09aafca40585467a996426eb975d920b-a42436991da63897.jpg","duration":325.419,"title":"Step 1 - Connecting Civic Shout to Engaging Networks","description":"This Loom explains how to connect Civic Shell to an Engaging Networks account using an API key. It first instructs viewers to create a permissions group in Engaging Networks under Admin Account Settings, then grant all permissions across multiple dropdowns (for example, 14 of 14 and 68 of 68) before saving. Next, it guides creating an API user, selecting the permissions group, using a unique email address across the account, setting a display name like CivicShout, and adding CivicShout’s IP address exactly as provided in the CivicShout setup guide (no spaces). Finally, it directs viewers to copy the API key from Civic Shell and move it back to Civic Shell for setup."}