Skip to main content

Admin Guide: Approving the Chrome Extension (Recruit Robin)

When a user wants to use the Recruit Robin Chrome extension, your organization may require IT approval first. This article explains which permissions the extension needs, why they are required, and how to safely allow the extension.

Updated over a week ago

πŸ”Ž What does the browser extension do?

The Recruit Robin browser extension allows users to connect their LinkedIn and Indeed accounts to Robin. This enables Robin, always on instruction from the user, to perform actions on their behalf such as:

β€’ finding candidates on LinkedIn and Indeed β€’ sending messages to candidates β€’ enriching profiles and synchronizing them with Robin

The extension helps recruiters find and contact candidates more quickly, without switching manually between different platforms.

βš™οΈ How does the extension work?

Users install the extension through the Chrome Web Store.

Through the extension, Robin can log in to LinkedIn and Indeed on behalf of the user.

After logging in, Robin can search for candidates, enrich profiles and send messages whenever the recruiter requests it.

The recruiter always initiates the action. Robin never performs actions without explicit user permission.

πŸ›‘οΈ How does Robin ensure safety?

Robin is built according to strict privacy and security principles.

β€’ No automatic actions Robin never performs actions unless the user starts or confirms them.

β€’ No storage of login credentials LinkedIn and Indeed login details are not stored by Robin. They are used only once to log in through the extension.

β€’ Encrypted data flows All communication between Robin, the browser extension and external platforms is encrypted.

β€’ Only relevant data is processed The extension reads only the information required for Robin’s functionality. No unrelated browsing history is collected or monitored.

πŸ›‘οΈ Which permissions does the extension request?

Depending on your Chrome policy, you may see permissions such as:

β€’ Reading and modifying data on visited websites Required to identify and enrich candidate profiles on LinkedIn and Indeed.

β€’ Communication with external APIs (Robin) Required to retrieve and synchronize data with the Robin platform.

β€’ Allowing pop ups and redirects Needed for actions such as matches, profile views and login flows.

β€’ Local storage and session management Ensures users do not need to log in repeatedly.

Robin uses these permissions only to support and automate recruitment processes, never for tracking or monitoring.

βœ… How to approve the extension

Option 1 – Through Chrome Enterprise or Google Admin

Log in to the Google Admin Console.

Go to Devices β†’ Chrome β†’ Apps and extensions.

Add the Recruit Robin extension from the Chrome Web Store.

Set the policy to Force install or Allow install.

Assign the policy to the correct OU or user group.

After this, the extension becomes automatically available to users.

Option 2 – Local browser settings (for smaller teams)

If you do not use a central Chrome policy, users can install the extension themselves via:

πŸ‘‰ Chrome Web Store Search for: Recruit Robin

Note: this only works if extension installation is not blocked by policy.

⚠️ Common issues

Extension does not appear in Chrome β†’ Check whether extensions are blocked by policy.

User cannot log in β†’ Check whether pop ups and redirects are allowed for Robin.

Functionality does not work on LinkedIn or Indeed β†’ Check whether the extension has access to those domains.

Security software blocks the extension β†’ Add Recruit Robin as a trusted extension.

πŸ” Privacy and security

Robin follows privacy by design principles.

β€’ No tracking outside the Robin context β€’ No monitoring of browsing behavior β€’ Interaction only with relevant recruitment pages β€’ No storage of LinkedIn or Indeed passwords β€’ All communication is encrypted

Did this answer your question?