With EHQ’s various visibility options targeting stakeholder groups is as easy as pie.

The aim of most consultations run with EHQ is to reach and engage with as many community members as possible. While more does not equal better, reaching out to as many people as possible is a legitimate goal. But there are also those consultations that are just targeted at a selected few. This might be a group of stakeholders, a community panel or people from within your organisation only.

Limit project access based on email domain

EHQ offers a ‘visibility’ option, in which admins can choose who is allowed to view and contribute to a project. This filtering can be based on a person’s email domain. So for example you can set up a protected projects that is only available to your colleagues who have the same email domain as you (e.g. @bangthetable.com). 

We like the idea of EngagementHQ administrators running internal projects and consultations for three reasons:

1. EHQ might be new to your organisation, or it has been around for a while, but not everybody is fully on-board yet. By setting up an internal consultation your colleagues can familiarize themselves with your new platform in their own time.
2. While point 1 might get their ideas going about how EHQ can be used for other projects, they will be able to experience the site as if they were a participant. This will help them not only if they ever to run their own projects, but they will be able to give you good feedback on the site as a whole.
3. It is great for the administrator as you can test and get to know the visibility option in a safe environment. Before potentially setting up protected projects with your external stakeholders, you can see how protected projects work in EHQ.