Your agency has asked for access to Algolia. You don't need to share your password for it. Algolia lets you add them with their own login, choose exactly what they can do, and remove them when the project ends. These are the clicks, checked against Algolia's own help pages in November 2026.
Which role to choose
Pick the narrowest role that lets your agency do the work. Set-up Search, View Search, Features, Crawler and Other is usually the right one.
| Role | What it allows | For an agency |
|---|---|---|
| Set-up Search, View Search, Features, Crawler and Other | Adds records and changes index settings, uses Analytics, A/B testing and Query Suggestions, runs the Crawler and manages API keys. No billing or team access. | Usually the right one |
| Set-up Search, View Search, Billing, Features, Team, Crawler and Other | Every permission section, including billing and adding team members. | If the work needs it |
| View Search | Uses the dashboard search page and views index settings, without changing anything. | If the work needs it |
Add your agency to Algolia
- Sign in to the Algolia dashboard and select Settings on the left sidebar.
- In the Team and Access section, click Team, then click Add Team Member.
- Enter your agency's email address and select your application as the application.
- Under Give them permissions, turn on only these sections: Set-up Search, View Search, Features, Crawler and Other. Then add the team member.
Only the application owner, or a team member with the Team permission, can add team members.
How you both know it worked
Algolia emails your agency an invitation from algolia.com. Once they accept it, they show in your Algolia account's list of people with access, where you can see or change their role at any time.
Remove access when the project ends
- On the API keys page of the Algolia dashboard, find the keys whose description includes your agency's email address. If your site or an extension uses one, switch it to one of the owner's keys first.
- Select Settings, then Team under Team and Access. Open the menu next to your agency's email address and remove the team member.
- Back on the API keys page, delete any other keys your agency created.
Do you have to share your password?
No. Every step above uses Algolia's own invite, so your agency signs in with their own account, your two-step verification stays on, and anything they change is recorded under their name. How to give a developer access without sharing your password covers the other accounts agencies usually ask for.
Doing this for every client?
Agencies can send each client one GetSetKeys link instead of a page like this. It walks the client through Algolia and the other platforms the project needs, and checks that each step is done.