Skip to content
EventConsultant
EN
Virtual and hybrid delivery

How to protect access links to a virtual event

The joining link went to members, and someone asks what stops it being forwarded to the industry.

Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.

The short answer

Protecting access links means deciding four things. How attendees prove they registered, how many people can use one link, who holds the host and speaker links, and when every link stops working.

Security settings differ by platform and plan. Put the questions to your platform supplier and a qualified IT or security adviser. Do not tell attendees about a security level that nobody has confirmed.

Four kinds of link, four different risks

Link typeWho holds itMain question
Attendee linkRegistrantsIs it one link for everyone, or does each registrant receive their own? What happens if it is forwarded?
Speaker and panellist linkSpeakers, moderatorsDoes it give extra powers such as sharing a screen? Is it sent only to the individual?
Host and producer linkOrganiser and platform operatorWho holds it, and is it ever pasted into a shared chat or document?
Replay linkRegistrants or the publicDoes it stay open after the event, and who can pass it on? See replay access plan.

Choices to make with your platform supplier

  • Registration first: attendees join only through a registration step, or a link is sent to a list.
  • A holding area where an operator admits attendees, if the platform offers one and a person is available to do it.
  • A passcode, and whether it is sent separately from the link.
  • Whether the platform can restrict the number of devices per registrant.
  • How the operator can remove someone and block them from returning.
  • Whether each choice is available on your plan. Ask the supplier to point to the vendor documentation.

Handling links in practice

  1. List every link type and the person who holds each. Keep the host link out of email threads with many recipients.
  2. Send attendee links only to registered addresses, and send the speaker link individually.
  3. Decide how late arrivals are checked if a holding area is used, and put a person on that task in the run-of-show.
  4. Agree when links are deactivated after the event and who does it.
  5. Check with your privacy owner what attendee data the registration step collects and who may see it.

What to leave to specialists

Whether the platform's controls are strong enough for your content, such as a members-only briefing with confidential material, is for the platform supplier and a qualified IT or security adviser to answer. The organiser asks clearly and records the answers.

Worked example · Fictional example

A members-only briefing on a regulatory update

Fictional organisation and figures, for illustration only.

Persatuan Pengurus Dana Pencen Fiktif plans an online briefing for about 300 members. The secretariat wants only members to attend.

It asks the platform supplier which registration and admission options its plan includes. Each member gets an individual link, only the producer holds the host link, and one person admits attendees from a holding area. The IT adviser reviews the setup the week before. After the event the links are closed and the replay goes only to the members' list.

Use this yourself

Access-link security questions

Send to your platform supplier and IT or security adviser, and record the answers. The RFP completeness checker can help turn them into a complete supplier request.

  1. What registration and admission options does our plan include? Please point to the vendor documentation.
  2. Can each registrant receive an individual link? What happens if it is forwarded?
  3. Is a passcode or holding area available, and who operates it during the session?
  4. How are speaker, host and producer links issued, and how can they be changed if one is shared by mistake?
  5. How can an operator remove an attendee and prevent them returning?
  6. Does the platform show who joined, from which device and for how long, and who can see that data?
  7. When do links stop working after the event, and can we set that date?
  8. What does the replay link allow, and who can share it?
  9. Who on our side holds host access, and who is the backup?
  10. Has an IT or security adviser reviewed the settings for the sensitivity of this content?

Use the free tool: Event RFP completeness checker

Handle it in-house, or bring in help?

Your team can usually handle this when

  • The event is open to the public and content is not sensitive.
  • Your platform supplier already advises on settings.
  • Registration and joining are handled by one trusted person.

Outside planning help earns its fee when

  • The session has members-only or confidential content.
  • Several suppliers, speakers and committees hold links.
  • A sponsor, regulator or committee has asked for written assurance on access control, and the questions need routing to the right specialists.

Need the access arrangements coordinated?

A conference project lead can list the link types and holders, put these questions to your platform supplier and IT adviser, and record the agreed arrangements in the run-of-show and joining guide. The specialists you appoint keep platform settings and security advice. Share your brief on WhatsApp and we will reply with which level of support fits and what it would cover.

Discuss your plansOpens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.Project support →

Questions organisers ask

Is a passcode enough?

It adds a step, but passcodes are often pasted next to the link. Ask the platform supplier and your IT adviser whether other controls suit the sensitivity of the content.

Should speakers use the same link as attendees?

Check with the platform supplier how roles are assigned. Speaker links usually carry extra permissions, so send them individually and not to a group.

Who should have host access?

As few people as the session needs, with a named backup. Record who holds it and change it if someone leaves the project.

Related resources

Content record: Written by the EventConsultant team to our editorial rules. Sources are listed on pages that rely on them.