Skip to content

Consents ​

A consent is a yes or no answer. A member gives it to a specific piece of wording. The club keeps the date, the version and the name of the person who gave it. This record is an audit trail. It is not a preference. A member must accept some consents to use the app. A member can change the answer to other consents at any time. Some consents belong to RunClub HQ. You cannot change them. The other consents belong to your club. You can write them in your own words. This page covers how to set up consents, where members give them, and how to read the audit trail.

Who can do this?

Only Club Admin can edit your club's consents, from Settings → Consent management. Anyone who can open the record of a member in the admin panel can see the consent history of that member. See Members and households. Members give and review their own consents from the member app.

How consents work ​

A consent belongs to one of three categories. The category decides when a member sees the consent:

CategoryShown
RegistrationJoining the club: the Agreements step of the joining wizard, or the welcome flow for a member we imported
SubscriptionThe Agreements step of the subscription wizard. Required consents only
GeneralProfile → Consents, to active members. Not tied to any particular step

Every consent is either required or optional. A member must accept a required consent to continue. A member can turn an optional consent on or off from their profile at any time. A member cannot withdraw a required consent from the profile after giving it. The product blocks the attempt. It does not accept the withdrawal silently.

You cannot edit one consent. It is the acknowledgement that your club uses RunClub HQ and how RunClub HQ handles personal data. It belongs to RunClub HQ and applies everywhere. It does not appear in your settings. Everything else is yours: your Privacy Policy, your Constitution, your Code of Conduct, anti-doping, photography and marketing. Each one starts in words that we drafted. You can change the words.

Set up your club's consents ​

Your club does not start with an empty list. When we set up your club, we created six ready-made agreements. They are the consents listed above, without the consent that RunClub HQ owns. Each agreement is active. Members see each agreement as described. Find the agreements in Settings → Consent management. You do not build them from scratch there.

Settings → Consent management, listing the club's six consents with their category, required and active status

Settings → Consent management: every agreement your members see, and whether it is required

To make a consent your own:

  1. Open the consent from the list. Choose Edit.
  2. Change the Display Label. Members see it as the heading. Change the Description. This is the full text, in a rich editor. To add club details automatically, use a merge tag from the list below.
  3. If you need to, change Category, Required Consent, Active or Display Order.
  4. Choose Preview to see the consent as a member reads it. Do this before you save.

Editing a consent definition, with the rich-text description and the merge tags panel

Editing a consent: the exact wording a member will read

Reset to Default

To restore the original wording of RunClub HQ, choose Reset to Default. This button shows only on a consent that you edited. It shows only when there is something to reset.

You can use these merge tags in the label or description:

TagFills in
Your club's name
/ The member who reads the consent
Your contact email from Settings → Branding
, , The matching link from Settings → Branding, if you have set one
RunClub HQ's own address
Today's date

Change wording that members have already agreed to ​

  1. Open the consent. Choose Edit.
  2. Change the Display Label or the Description to the new wording.
  3. Raise the Version, for example from 1.0 to 2.0. Save the consent.

Each consent that a member gives keeps its version. When you raise the version, the consent history of a member shows which wording the member agreed to.

The product does not ask members to agree again

A member who has not yet given the consent reads the new wording. A member who agreed to the old wording does not see the new wording again. The product has no in-app request to agree again today. If everyone must agree to the new wording, message members directly.

Your club may not need every consent. For example, your club may not need photography or anti-doping. Switch off each consent that you do not use.

  1. Open the consent from Settings → Consent management. Choose Edit.
  2. Turn off Active. Save the consent.

Members no longer see that consent when they join, renew or open Profile → Consents. It no longer counts as required. Consents that members gave before stay on their records, so the trail is complete. To start asking again, turn Active back on.

You cannot switch off the consent that RunClub HQ owns. It is not in your list. It applies at every club.

Switch off, do not delete

You cannot delete most of the consents that your club started with. You also cannot delete a consent that a member has answered. Switch the consent off instead. This does the same job and keeps the history.

What members see ​

Members review everything they have agreed to, and turn optional consents on or off, in Profile → Consents in the member app. A required consent shows there too, but it is locked. A member cannot untick it. Withdrawal of a required consent is a question about membership. It is not a settings change.

The member app's Consents page, showing given agreements and a toggle for an optional one

Profile → Consents: what the member agreed to, and what the member can still change

When a household manager registers a junior, the product records the consent against the junior's own record. The product names the household manager who was typing as the person who gave the consent. The Given By column on a member's consent history shows this for anyone who did not consent for themselves.

Email preferences and mailing-list opt-outs are different. They are not consents. They have no versions. They are not part of this audit trail. See Communications for those.

Open the record of any member. Choose the Consents tab. It lists every consent that the member has been asked for. For each consent it shows whether the member gave it, when, by whom, and its version. If the member withdrew the consent, it also shows when.

This is the audit trail. The general activity log does not include it. A consent is a current state with its history attached. It is not a stream of events.

The roster (Members → All Members) has a Consents column. It shows whether the required registration and subscription consents of a member are in place. Use the Missing Required Consents filter to find any member who has a required consent missing.

Medical and emergency information ​

There is no separate consent for sharing the medical details of a member in an emergency. The reveal-with-reason system protects that information. Your Welfare Officer uses it. The system logs every look against a reason, whether or not the member has agreed to anything else. See the Welfare officer playbook for how it works.

Troubleshooting ​

A member keeps landing back on the agreements step ​

A member gives each consent once. When the member signs in, the product does not ask for a consent that the member already gave. If someone keeps seeing the Agreements step, they have not finished it. They leave the step without submitting. The next time they sign in, the product sends them straight back to finish it. It does not show a new copy of the step.

A member cannot withdraw a required consent from their profile. The product refuses the change. The checkbox is locked, so the member cannot try. This is what required means. If a member no longer agrees to something required, that is a conversation about their membership. It is not a setting to change.

This is expected today. It is not a fault. See the warning under Change wording that members have already agreed to above.

See also ​