When trying to log in to Filerev with your Google Drive account you might receive an error message such as:
Access blocked: Filerev is not approved by Advanced Protection
This means your Google account uses the Advanced Protected Program, which blocks all third-party access to your Google account, including Filerev.
Turn off Advanced Protection for Gmail Accounts
For standard Gmail (@gmail.com) accounts, you can turn off Advanced Protection by visiting https://myaccount.google.com/advanced-protection/settings and clicking the Unenroll from Advanced Protection button. If you want to continue to use Advanced Protection you can go back to the same link and turn it back on once you have finished using Filerev.
Turn off Advanced Protection for Google Workspace Accounts
For a Google Workspace account the account administrator can whitelist Filerev. This is accomplished with the following steps (also documented by Google).
- Click the following link to go to Security > Access and data control > API Controls > Manage Third-party app access in your admin account.
- Click Configure new app.
- In the Search Box, type Filerev and select the Search button.
- Click the first Filerev entry labeled Web, with a client ID beginning with
31056671523-1cpm8f9e. This is the client used to sign in at my.filerev.com. - On the Scope page, keep All in [your organization] (all users) selected, or choose Select org units to limit access to specific organizational units, then click Continue.
- On the Access to Google Data page, select Trusted, click Continue, then review and click Finish. If your organization prefers to grant only specific services, choose Specific Google data instead. In that case, the selected services must include Drive and Google Sign-in; both are required for Filerev to work.
- Repeat steps 2 through 6 for any other Filerev entries your users need (see the table below). Google requires each entry to be configured individually.
With those steps complete, you will be able to log in to Filerev from a desktop computer.
Every Filerev entry shown in the search results belongs to us. If you prefer to approve only what your users need, this table identifies each one (OAuth client IDs end in
Filerev’s official client IDs
Every Filerev entry shown in the search results belongs to us. If you prefer to approve only what your users need, this list identifies each one (OAuth client IDs end in .apps.googleusercontent.com).
Filerev web app (my.filerev.com). Required for signing in.31056671523-1cpm8f9e3o029iud7aa5qa449ttres3u
Filerev add-on for Google Workspace.31056671523-nikobeui3m3bdvk1p8chffs311qqet5j
Sign-in credential used by the Android app when installed from Google Play.31056671523-8bm2gcnmh95i7rnu8bn551pcrt02m0pe
Sign-in credential used by the Android app when installed from the Samsung Galaxy Store.31056671523-0i96kl5gupjih49i970shvujj56or57a
Sign-in credential used by the iOS app.31056671523-k3l9gtq3b4eot1i3479p9vc861ob0r09
Filerev development and marketplace infrastructure. Safe to approve, but not needed for your users to sign in.31056671523-6jgf4tn95chreqg17kegjj0fnok9hmsa31056671523-1imig1g6dvp4odn0ib4j0vs4guskcr6r31056671523-hqvkhcutsjm506234moqc4fj06415vs8
“Filerev for Google Drive” (app.cleandrive.my.twa). This is the mobile app itself, identified by its app ID instead of an OAuth client. Approving it has no effect on sign-in. It only matters if your organization controls which apps can be installed on managed devices.