Easy Read summary
A conference website helps people find your event. But you should keep your own list of people who attend. Use your own account. Keep your own data. Do not depend on one big company for everything.
African institutions run serious conferences, workshops and convenings. Too often the visibility layer is rented: an account on a global ticketing platform, a listing that competes with unrelated events, and attendee data that never returns to the institution in a usable form.
There is a better division of labour. A professional body can provide context, credibility and a reviewed listing. A conference platform can provide registration, payment and delivery. The institution should own the account, the brand, the attendee relationship and the record of who attended.
Three questions are worth asking before publishing anywhere.
Who owns the attendee relationship? If the platform controls the only usable mailing list, the institution has rented its audience. Export rights and consent records should be clear before the first registration.
Who controls the listing? A listing should carry the organiser's name, access features, cancellation terms and contact route. If the organiser cannot correct the listing quickly, the platform is not serving the event.
What happens after the event? Recordings, slide decks, certificates and follow-up resources should return to the institution. Attendees should be able to choose what they receive next.
ADRGP publishes its own events and offers approved organisers an account to publish theirs. For conferences that need a dedicated site, organisers can also publish on APublishing Conferences under their own account. The two accounts are separate by design: separate credentials, separate registrations, separate privacy notices.
That separation is not bureaucracy. It is how an institution keeps its audience, its evidence and its reputation as it grows.