Your agency has asked for access to Render. You don't need to share your password for it. Render 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 Render's own help pages in November 2026.
Which role to choose
Pick the narrowest role that lets your agency do the work. Developer is usually the right one.
| Role | What it allows | For an agency |
|---|---|---|
| Developer | Creates, deploys and manages services, datastores and environment groups, with limits in protected environments. Cannot change workspace settings or members. | Usually the right one |
| Admin | Everything in the workspace, including members, billing, login rules and protected environments. | If the work needs it |
| Contributor | Deploys and rolls back services and reads their logs. Cannot see environment variables or connection strings, use the Shell, or create or change most resources. Scale plan or higher. | If the work needs it |
| Viewer | Sees most of the workspace without changing anything. Cannot see logs, environment variables or connection strings. Scale plan or higher. | If the work needs it |
Add your agency to Render
Open Render Dashboard Choose your workspace from the workspace dropdown, then click Settings in the left pane.
- In the Render Dashboard, open the workspace dropdown at the top of the left pane and choose your workspace.
- From the workspace home, click Settings in the left pane and scroll down to Team members.
- Click + Invite members, enter your agency's email address, select Developer from the dropdown and send the invite.
Only an Admin can invite, and a Hobby workspace can't add team members. Pro costs $25 a month plus compute, with unlimited seats: open the workspace dropdown, select Billing, then Update Plan.
How you both know it worked
Render emails your agency an invitation from render.com. Once they accept it, they show in your Render account's list of people with access, where you can see or change their role at any time.
Remove access when the project ends
- In the Render Dashboard, choose your workspace from the workspace dropdown, click Settings in the left pane and scroll down to Team members.
- Open the ••• menu next to your agency's email address and click Remove team member.
- If your agency used a service's deploy hook, open that service's Settings tab, click Regenerate Hook and give the new URL to whatever triggers your deploys.
Do you have to share your password?
No. Every step above uses Render'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 Render and the other platforms the project needs, and checks that each step is done.