Skip to main content

IT Team's Guide to Flo (University Admins)

How to ensure Flo will work for your interviewers when on firm computers or firm networks.

Written by Annie Cox

Flo is widely used by law schools and law firms to conduct virtual interviews and virtual networking events.

Flo handles scheduling, candidate management, and interview logistics. Interviews take place on video powered by Zoom — hosted on Flo's own Zoom account and embedded directly in the Flo interview page.

To ensure a seamless experience for students, interviewers, and administrators, we recommend your university's IT team review the following requirements before your interview program.

What Flo Does Not Require

  • No software to install on university devices.

  • No Zoom license or Zoom account for your university, and no changes to your Zoom tenant.

  • No administrator consent and no browser extension.

  • Users access their interviews through Flo, never Zoom.

Browser & Device Requirements

Please ensure that:

  • Users access their interviews through their Flo interview link. The interview opens in their web browser on the Flo page — there is nothing to download, install, or sign in to.

  • Google Chrome is recommended. Internet Explorer is not supported.

  • Cameras, microphones, and speakers are enabled and working, and the browser is allowed to request camera and microphone access on florecruit.com.

  • The browser is permitted to display embedded content from zoom.us, which is how the interview window is delivered.

Note: If a user experiences trouble in the browser, they can move that call to the Zoom desktop app from the meeting's own "Copy invite link" menu. This is intended as a fallback for an individual experiencing an issue and is not the expected way to join an interview. IT does not need to prepare devices for this option.

Firewall & Network Configuration

If your university restricts outbound traffic, your IT team should ensure the following are permitted:

Allow

Why

florecruit.com

The Flo application itself, including the interview page.

source.zoom.us

The interview window loads from here when the page opens. If this is blocked, the interview will not start.

*.zoom.us and Zoom's published IP ranges

Audio and video. Prefer domain rules over fixed IP lists.

Outbound TCP 443 and UDP 8801–8810

UDP carries the audio and video. It is often closed by default.

Please also make sure Zoom traffic is excluded from SSL/TLS inspection and deep packet inspection — Zscaler, Netskope, and Palo Alto all need Zoom on their bypass list — and that it is not routed back through a central proxy.

For complete requirements, see Zoom's official network firewall guide:

We also recommend allowing camera and microphone access for florecruit.com and confirming that users can open their Flo interview links from their browser.

Test Your Setup

After completing the recommended configuration, we encourage your team to schedule a test call with Flo Recruit before your interview program begins.

For the best results, we recommend having at least two participants during the test:

  • One person connected to the university's network.

  • One person connected from an external network.

A member of the Flo team will facilitate the test and help identify any connectivity issues.

Email Communications

Whitelist the following email domains:

  • @floevents.email

  • @florecruitnotifications.com

These domains are used to send important communications, including interview schedules, portal links, reminders, and last-minute updates.

To help ensure reliable email delivery, whitelist the following sending IP address:

149.72.33.196

The reverse DNS (PTR) record for this IP address is:

o1.ptr1593.floevents.email

Security

Why partner with Flo Recruit? We prioritize security.

[Read more about Flo Recruit Security here.]

Working Over VPN

Video traffic that is forced through a university VPN is the most common cause of poor call quality. The recommended fix is for your IT team to split-tunnel Zoom traffic so audio and video travel directly rather than through the VPN concentrator.

If a user is having trouble mid-call and IT support isn't immediately available, disconnecting from the VPN for the duration of the interview usually resolves it. The guide below walks through that.

Attachment icon
Did this answer your question?