Getting Information Out of SRM | Civio Engage Knowledge Base [Skip to content](#main) [ ![Civio Engage Knowledge Base](/civio-light.svg) ](https://engage.knowledge.civ.io) [Product documentation](/articles) [Release notes](/releases) [Roadmap](/roadmap) [ Support portal ](https://engage.knowledge.civ.io/portal/login) Toggle navigation [Product documentation](/articles) [Release notes](/releases) [Roadmap](/roadmap) [Support portal](https://engage.knowledge.civ.io/portal/login) 1. [Home](/) › 2. [Product documentation](/articles) › 3. [Stakeholder Management](/articles?category=16) › 4. Getting Information Out of SRM Getting Information Out of SRM ============================== Updated 4 weeks ago · 3 min read Search Search This article covers the ways to get information back out of SRM: the dashboard, spreadsheet exports, the lists themselves, and the API. 1. Build your dashboard ----------------------- SRM ships with a pre-built home dashboard, so you can start from that and change it. Click **Add new widget** to add, and drag to rearrange. Fifteen SRM widgets are available. Four of the most used: Widget What it answers **Stakeholders Needing Attention** Stakeholders with high influence and negative sentiment. **Issues Needing Attention** What is open and going nowhere. **Stakeholder relationship health** The whole register bucketed **Critical / At risk / Watch / Healthy / Strong**. **My Tasks** Your own open tasks. ![An SRM home dashboard showing the Stakeholder relationship health chart, the two needing-attention tables and a task list](https://engage.knowledge.civ.io/storage/Igar0dQYlUqLdEjzTrzshxj6FCCyxYtDvsdaHNmF.png) **Stakeholder mapping** plots your register across influence and interest levels as a bar chart, a line chart or a table. The rest are counts, tables and recent-activity lists for each record type. See [Reporting in SRM](/articles/reporting-in-srm) for the full set. Widgets follow the same team scoping as everything else, so two people on different teams see different numbers on the same dashboard. 2. Pull an export ----------------- 1. Open the list you need: **Stakeholders**, **Organisations**, **Initiatives**, **Interactions** or **Issues**. 2. Narrow it with search and **Filter** until it shows exactly what you want in the report. 3. Open **Additional options** and choose **Export**. The export matches what is on screen, filters and search included, so filter first. Custom fields get a column each. If you want everything, clear the filters. For one record's full history rather than a table, use **Export activity** at the top of its timeline. 3. Work the lists at scale -------------------------- Three controls do most of the work on a long list: - **Filters**: every list has its own set. On stakeholders that includes organisation, initiative, group, relationship owner, all three scores, team, and one filter per custom field. - **The column selector**: switches on the columns you need. **Group(s)**, **Owner(s)**, **Team** and your custom fields are all available but off by default. - **Bulk actions**: tick rows and change them together. **Change scores** after a round of engagement, **Edit associations** to put a cohort in a group, **Set team** after an import. The pattern is always the same: filter, check with a column, then act. [Filtering, columns and bulk updates in SRM](/articles/filtering-columns-and-bulk-updates-in-srm) covers each list's options. 4. Report back on what changed ------------------------------ Two things in SRM record what came of the feedback you collected: - **The initiative timeline**: every interaction, issue and task across a programme, in date order. - **Issue resolution summaries**: when you resolve an issue, the summary and the date are captured on the record and on the timelines of everyone linked to it. On the public side, [Closing the Feedback Loop](/articles/10221452631567-Closing-the-Feedback-Loop) covers reporting back to your community. 5. Use the API -------------- If another system needs SRM data, or you want to read or load records in bulk, use the API. It covers stakeholders, organisations, initiatives, issues and interactions, and each one can be listed, read, created, updated and deleted. Requests use the same tokens and follow the same permissions as the rest of the Civio Engage API, so an integration only sees the records its account can see. Setup and authentication are covered in [Working with the Civio Engage API](/articles/working-with-the-civio-engage-api). Where to go next ---------------- That is the series. From here: - **Bringing existing lists in**: [Getting your stakeholder data into SRM](/articles/getting-your-stakeholder-data-into-srm) - **Letting people add themselves**: [Capturing stakeholders from a survey](/articles/capturing-stakeholders-from-a-survey) - **Adding your own fields**: [Custom fields for SRM records](/articles/custom-fields-for-srm-records) - **Sorting out access**: [Teams in SRM](/articles/teams-in-srm) and [SRM Roles](/articles/srm-roles) - **Connecting another system**: [Working with the Civio Engage API](/articles/working-with-the-civio-engage-api) And if something is not behaving as described here, [Getting support and tracking your requests](/articles/getting-support) is the way to raise it. Was this article helpful? ------------------------- Your feedback helps us prioritise what to rewrite. Yes No [ Back to Stakeholder Management ](/articles?category=16) On this page ### Still need help? Raise a request in the support portal and track it to resolution. [ Submit a support request ](https://engage.knowledge.civ.io/portal/login) Submit a support request through the [support portal](/portal) or email . © 2026 [Civio](https://civ.io) [Privacy Policy](/articles/privacy-policy) [Terms of Use](/articles/terms-of-use)