Get your council started

Setting up the council, adding your first schools, and inviting your team.

Set up the council

The first time you sign in you are asked to create the council: "Welcome — let's set up your council". It takes about a minute, and you become the council administrator.

You are asked for the council name, your own name, and optionally a first cluster — a group of schools you want to report on together. You can add more clusters later.

The getting-started checklist

Your council home page carries a Getting Started checklist. Each item turns itself green from the state of the programme — there is nothing to tick:

Once any school in the council has recorded a check-in, the checklist has done its job and the panel is hidden. It does not come back, so from then on use the Usage Report to see who has started and who has not.

It advises starting with 2–3 pilot schools rather than the whole network. That is deliberate — it lets you fix the process before you scale it.

Add a school

1. Choose Add School.
2. Enter the School Name and pick Primary or Secondary.
3. Tick any Clusters the school belongs to. This is optional — a school can be in several clusters, or in none.
4. Optionally add the School Administrator — a name and an email. As the form says: "We'll email them a sign-in link right away — you can also do this later from the school's page."

Enter both the name and the email, or leave both blank.

Adding the school administrator here is the fastest route: they set the school up themselves, including classes and the staff-room poster, and you do not have to.

Invite your council team

Under Council Team, enter an email and choose a role:

• Admin — full access, including adding schools and issuing API keys.
• Viewer — dashboards and the schools list, read-only.

As the card puts it: "Admins have full access. Viewers can see dashboards and the schools list, read-only."

Invited people are emailed a sign-in link. Give reporting and analysis staff Viewer unless they need to change things — it is the lower-risk default.

Clusters

A cluster groups schools for reporting — by area, by catchment, by programme phase. Clusters give you the Cluster dashboard, with a school league table and a combined mode mix.

A school can belong to any number of clusters, or to none, so the same school can sit in a geographic area and a programme cohort at the same time.

Manage them from Clusters in the council menu:

• Create a cluster, and rename it later. A cluster can carry an Irish name alongside its English one; anyone reading the app in Irish sees it wherever the cluster is named.
• Choose which schools are in it from the cluster's own page — or set a school's clusters from that school's page. Either side does the same thing.
• Delete a cluster. Its schools leave the cluster but are not deleted: they keep their data and stay on the council dashboard. A cluster that still has challenges cannot be deleted — the message names them, so end or move those first.

What to do first, in order

1. Add two or three pilot schools, each with its school administrator.
2. Let them import classes and print their posters.
3. Confirm journeys are arriving — the checklist's last step turns green and the panel then disappears.
4. Set your branding and privacy notice — the notice produces the public link that goes on a permission slip.
5. Then add the rest of the network.

If a colleague cannot get in

They will see "Your account isn't set up yet" and "Ask your council's active-travel coordinator to add you." Invite them from Council Team using the email address they are actually signing in with.

A teacher who lands there does not need an account at all — the same page points out "You only need your school code — no account required."

Still stuck? Email our support team.