Rolling out link protection across a team

Adding a new layer of protection should not mean a month of chasing people to install it. Here is a simple way to introduce click-time link protection to a team, from first decision to evidence you can show. It is written for IT and security teams, and for the managers who sign off on them.

Why start with a plan

Link protection works best when it is on every device that matters, switched on without fuss, and visible to the people who run security. A short plan makes sure you get there without annoying staff or leaving gaps. If you are still weighing up whether you need another layer, read why email filters miss phishing in chat apps first.

1. Decide what you want to cover

List the devices and places where your people click links:

• Windows laptops and desktops.
• Android phones, including phones people use for work.
• The browsers your team uses: Chrome, Edge and Firefox.

Decide whether personal phones are in scope. This affects how you roll it out, and what you tell people.

2. Start with a pilot

Choose a small group that reflects how the company works. Include people in different roles, and people who use chat apps a lot, such as sales, support and finance. A free 30-day pilot is long enough to see what actually happens on real devices.

Before you begin, write down two or three things you want to learn, for example: does it install cleanly on our devices, do people understand the warning page, and what kind of risky links do we see?

3. Roll it out centrally

When you move beyond the pilot, install RIEG through your device management tools, so you are not depending on each person to do it. Turn on tamper protection so people cannot switch RIEG off without admin approval.

4. Tell people why

A short message works better than a long policy. Say what it does (“it checks links before they open”), what they will see (“a warning page, with a way to go back safely”), and who to ask for help. Give one example of the kind of message it is built for, such as a fake delivery notice or a fake KYC message.

5. Watch what it catches

Use the admin dashboard to see what was blocked across the team. Look at patterns: which apps the risky links arrive through, and which teams see the most. That tells you where to focus training.

6. Keep evidence

For audits and reviews, use the reports that show what RIEG checked and blocked. They turn “we think we are covered” into something you can show.

A simple rollout timeline

When	What happens
Week 0	Decide devices, pick a pilot group, tell them what to expect
Weeks 1 to 4	Pilot on real devices. Collect feedback and look at what is blocked
After the pilot	Decide, then roll out through your device management tools with tamper protection
Ongoing	Review the dashboard and reports. Use what you see to focus training

Pair it with training

Technology and habits work together. Share a few plain-English guides with staff, such as what phishing is and how to read a link before you click it.

Ready to try it?

Request a free 30-day pilot and we will help you plan it. If you have questions first, talk to the team.