Most events are a date and a registration form. A ministry’s ONE BIG event of the year is a different thing: it has stages, an agenda of breakouts people choose between, a command centre on the day, and a public page of its own. That is the Flagship Event capability. It was Impact’s `summit` alone until 2026-10-10, which is why a newly provisioned ministry’s attendee app opened on four empty screens.
Open the tenant and switch Flagship Event on.
It needs the WEBSITE app, because the event gets a public page. A Full tenant is born with it; a Light one is not, the same as the newsletter — so a Light ministry that runs a conference needs this switch, and a Full one that runs none can turn it off in a click.
Ask what they call it, and type it under Name & address.
Summit, Conference, Gathering, Retreat: the admin’s headings, its menus and the public page all read their word. Set it here so they are never reading "Flagship Event" — which is accurate and reads like a placeholder. They can change it themselves afterwards in their own Settings, and theirs wins over this.
Set its address in the same dialog.
The slug the public page lives at — /summit, /conference. A blank or an address the platform cannot use falls back to /flagship, so it is refused here rather than saved and ignored.
Rebuild that site.
THE ADDRESS NEEDS A DEPLOY and the name does not. The router resolves the slug once at bootstrap, so until the site is rebuilt the page is still at the old address while every heading already says the new word. Tell the ministry that, or they will report it as a bug.
THE PLURAL IS GUESSED. A ministry that fills in only the singular gets it with an "s" — right for Summits, Conferences, Gatherings and Retreats, wrong often enough that there is a second field for it. Check it with them rather than leaving it.
Impact keeps saying Summit with nothing in its Web Config at all. The word resolves in three steps — what the ministry typed, then that build’s own word, then the generic floor — and the middle step is what stops Impact’s own site reading "Flagship Event" the day the field was added.
BOTH ENDS OF THAT CHAIN WERE MISSING UNTIL 2026-10-10. The platform read webConfig.flagshipEventName in eight places in the admin and nothing anywhere WROTE it, and the manifest carried no word either — so every ministry but Impact read "Flagship Event" with no way to change it. The ministry’s own Settings field and this console’s came in together; if you meet a build older than that, the generic is why.
It was an EXTRA until 2026-10-10 and is now a FEATURE, and those are read opposite ways round: an extra is off unless a record says true, a feature is ON unless a record says false. The platform therefore still falls back to the old `extras.summit` for any ministry whose record has not been written yet, which is what stops the switch handing a flagship event to every ministry alive. Do not drop `summit` from the extras list until that migration is live.