Technical/Troubleshooting Guide

Have more questions? Submit a request

A guide to setting up FlashAcademy in school and resolving the most common technical issues, covering device requirements, domain allow listing, device permissions, logins and microphone problems.

How to Ensure FlashAcademy Is Set Up and Accessible in School

Device Requirements

FlashAcademy requires an active internet connection.

iPhone and iPad

iOS 15 or later with at least 2GB RAM (available on the Apple App Store).

Android Devices

Android 7 (Nougat) or later with at least 2GB RAM (available on Google Play Store).

Windows Computers

FlashAcademy is available through a browser at web.flashacademy.com (or edu.flashacademy.com for staff).

Supported browsers (Windows 7 SP1 or newer):

  • Chrome 57+

  • Firefox 52+

  • Edge 85+
    Note: Internet Explorer is not supported.

Apple Mac Computers

FlashAcademy is accessible via browser on macOS (OS X Yosemite 10.10+).

Supported browsers:

  • Chrome 57+

  • Firefox 52+

  • Edge 85+
    Note: Safari is not fully compatible; we do not recommend using it with the Web App.

Google Chromebooks

FlashAcademy works on Chromebooks with at least 2GB RAM using Chrome version 57+.


Domain Allow List (Whitelisting)

To prevent access issues caused by school firewalls, ensure the following domain is on your network's allow list (sometimes called a whitelist):

  • *.flashacademy.com

Use our Network Access Checker to confirm FlashAcademy is accessible on your network.

Schools using Securly or other web filtering: If your school uses a management or filtering system such as Securly, or any other centralised web filtering, you must add *.flashacademy.com to that system's global allow list.

The domain must be allowed globally, for all users. Allowing it only for students, or for specific student groups or policies, will not work and FlashAcademy will not load. We have seen this with a number of schools, so please check the setting with your IT team or filtering provider.


Device Permissions

Apple Devices:

  • Camera

  • Microphone

Android Devices:

  • Camera

  • Microphone

  • Storage

Permissions can be managed individually on each device or via your MDM platform (e.g., Meraki).


Troubleshooting

Domain Allow List

Ensure all required domains are on your allow list to prevent access issues. If your school uses Securly or another centralised web filter, *.flashacademy.com must be on the global allow list, not just a student-only policy (see Domain Allow List above).

Device Setup

  • Confirm all device permissions are enabled.

  • Keep devices and the FlashAcademy app updated.

Login Details & Password Resets

  • Student usernames: Teacher Dashboard > Students

  • Passwords are not visible but can be reset from the same area.


Microphone Access Troubleshooting

Before adjusting browser settings:

  • Confirm the microphone is plugged in.

  • Ensure it isn’t physically muted.

  • Test it in another app to verify it works.

Check Device Settings

Windows:
Settings > Sound > Input → select microphone → test input level.

Mac:
System Settings > Sound > Input → select microphone → check input meter. (On macOS Monterey and earlier, this is under System Preferences.)

Browser Permissions

Chrome:
Settings > Privacy & Security > Site Settings > Microphone
→ Allow FlashAcademy; remove blocked entries.

Edge:
Settings > Cookies & Site Permissions > Microphone
→ Ensure FlashAcademy is allowed.

Firefox:
Settings > Privacy & Security > Permissions > Microphone
→ Adjust or remove site permissions.

Additional Tips


Still Having Issues?

If you're still having problems after following this guide and clearing your cache, please email support@flashacademy.com with the following information so we can investigate:

  • Device: the make and model of the affected device(s).
  • Access method: the browser and version, or the app version, being used.
  • Who is affected: whether it's all staff and students or only a few. If only a few, please include their usernames.
  • Screenshots: any relevant screenshots, including error messages.

Once we have this, we can pass it to our development team to investigate further.

Articles in this section

Was this article helpful?
0 out of 0 found this helpful