Repository navigation
Member guide
This guide is for the people the Hub is built for: members of the constituency who sign in to do work, not to administer the platform. It describes what you can do and, where it helps, why the system behaves the way it does. You do not need to know how the Hub is implemented to use it — but knowing the model makes the odd corners less odd.
Register through the sign-in page; an administrator verifies the account before membership features unlock. Verification is a deliberate gate — the constituency's membership is a defined thing, and the platform mirrors that rather than letting anyone self-declare. While you wait, the public site works normally.
Your profile carries your membership track and status. Track is which kind of member you are; status is where that membership stands — pending review, active, lapsed, ended. Several features quietly depend on status: an expired Constituency Work membership, for example, means your seat's votes stop counting in the Council electorate even though you can still sign in. If something you expect to see is missing, your status is the first thing to check.
Each working group has a workspace at /workspace/:slug. Joining a group creates a participation record — a real, dated entry in the system, not just a list entry — which is what later lets the platform answer "who is in this group" authoritatively. If you hold a responsibility in the group (contact point, for instance), that appears alongside your participation as a separate record with its own time window.
Workspaces carry the group's events, resources, decisions and progress. What you can edit inside a workspace depends on your records there: members participate, contact points manage. The interface hides what you cannot use, but the underlying rule is always enforced server-side — a direct link to a page you cannot use will still decline politely.
- Opportunities are submitted for review before they are listed — yours and your organisation's appear under your profile with their review state.
- Events come from groups and bodies; you can add them to your calendar in the standard formats.
- Resources are the shared collection. Material imported from elsewhere keeps its original attribution and review status, and inclusion is a mirror of the source collection — not an endorsement.
Members with the right responsibilities can draft content — announcements, pages, opportunities — which then passes through review before it publishes. Your drafts live under your profile; the review pipeline is described in Content and publishing. The short version: nothing reaches the public site without a second pair of eyes, and that is intentional.
When a decision is presented for consultation you can comment and raise flags; when it reaches a vote, ballots open to the eligible electorate — which may be everyone, or may be the Council seats, depending on the decision's rules. Elections work differently: you request a voting credential, then cast a secret ballot. Your credential proves you are eligible without tying your name to your choice. The full pipeline is in Governance and decisions.
The Hub emails and pushes what matters — review outcomes, decision transitions, group activity you follow — and lets you tune it per category. Mandatory messages (safeguarding, legal, security notices) cannot be switched off; everything else has a toggle in your notification settings, and bulk categories can be silenced without missing the ones that are not optional. Web push needs a browser that supports it and a one-time permission grant.
Your profile fields each carry a visibility choice — members, contacts, or private — and the platform enforces it at read time, not just in the UI. The /member/team/privacy channel exists for exercising data rights: requests there go to the privacy reviewers, not into a black hole.