Theo at Northside Studio is rebuilding the Harbor Fitness website, and he has asked Dana for access to her domain, WordPress site, Shopify store and Stripe account. Emailing the passwords looks quickest, but each platform lets Dana invite Theo to sign in as himself, which takes about as long and keeps her password in her hands. This guide is for owners like Dana.
If your developer uses Get Set Keys, one link shows you each of these steps with their email and the right role already filled in.
Send one link insteadWhy an invite is safer than your password
Some access requests still ask for a login or password. No platform below needs one, and an invite is better for you in four ways.
- They get their own login. Your password stays private, and you don't have to change it when the project ends.
- Two-step verification stays on. With a shared password, their sign-ins need a code from your phone, so you either read codes out or switch the protection off. With an invite, codes go to their phone.
- There's a record of who changed what. Changes show under their name. Stripe, for example, keeps 180 days of team member activity in its Security history.
- It's easy to take back. Removing one person takes a minute and doesn't touch your login.
- Developer asks for access
- you invite their work email from your own account
- they accept with their own login and two-step verification
- they work under their own name
- you remove them when the project ends
One link per client, with every step checked. Reserve a founding place
What access does and doesn't let them do
Access is permission to work in your account, not ownership. Stripe says only the owner can transfer ownership, and Shopify doesn't allow store ownership to go to a collaborator at all.
| Platform | What you give | What they can do | What they can't do |
|---|---|---|---|
| GoDaddy | Delegate access, Domains Only | Domain settings such as nameservers and forwarding | See or change your password or Support PIN, manage payment methods, invite others |
| Namecheap | Share Access on one domain | Only the settings you tick | Anything you didn't tick, or SSL certificates |
| WordPress | A user with the Administrator role | Everything, including plugins, themes and other users | Very little: on a single site, it's the top role |
| Shopify | A collaborator account | Whatever the roles you approve allow | Take ownership, get the Administrator store role, use Shopify POS |
| Stripe | The Developer role | Set up the integration, create API keys, refund payments | Invite team members, edit bank details or the payout schedule, change the owner |
WordPress needs the most thought. Administrators can add, edit and delete users, so keep your own Administrator account. If they only edit content, Editor is enough.
Sending this to a client? Send one link instead
The five requests you'll see most
Menu names come from each platform's help pages at the time of writing, and interfaces change.
Domain and DNS at GoDaddy: delegate access
- Sign in and open your Delegate Access page.
- Under People who can access my account, select Invite to Access.
- Enter your developer's name and work email.
- Choose Domains Only, or Products & Domains if they also work on your GoDaddy hosting or email.
- Send the invitation.
They need their own GoDaddy account and must accept within 48 to 72 hours. Transfer access, which lets someone move, delete or sell a domain, is a separate switch in your domain folder settings. Leave it off. Full steps: GoDaddy access, step by step.
Get Set KeysOne link per client
If your developer uses Get Set Keys, their link shows you these GoDaddy steps with their email and Domains Only already filled in, and checks the step off when GoDaddy's invite reaches them.
Send one link insteadLaunching November 2026
Domain and DNS at Namecheap: Share Access
- Go to Domain List and select Manage next to the domain.
- Open the Sharing & Transfer tab and find Share Access.
- Enter their Namecheap username or email in New Manager and select Add.
- Tick only the settings they need, then enter your own Namecheap password to confirm the change.
Namecheap advises against sharing every setting; its own example shares DNS management and keeps contact and nameserver changes with the owner. They need their own Namecheap account and have 7 days to accept. Full steps: Namecheap access, step by step.
A WordPress site: add a user
- In your WordPress dashboard, go to Users > Add User (the label differs slightly on older versions).
- Enter a username and their work email.
- Tick Send User Notification. WordPress emails them a link to set their own password, so you never send one.
- Under Role, choose Administrator if they'll install plugins, themes or updates, or Editor for content only.
- Click Add User.
These steps are for self-hosted WordPress. Your hosting account needs a separate invite. Full steps: WordPress access, step by step.
A Shopify store: approve a collaborator request
Here you give the developer a code, they send a request, and you approve it.
- In your Shopify admin, go to Settings > Users, then Users & permissions (or Users if your store is part of an organization), then Security.
- Click the 4-digit collaborator request code to copy it, and send it to your developer.
- When you get the request email, go to Settings > Users and click the Requests status.
- Open the request and, in the Roles section, edit the suggested role down to the permissions they need.
- Click Accept request, or Reject request if you didn't expect it.
Collaborators must use two-step authentication, and they don't count toward your store's user limit. Full steps: Shopify access, step by step. Agencies can read how collaborator requests work from their side.
Get Set KeysOne link per client
If your developer sends you a Get Set Keys link, it shows you where to find the collaborator request code, and they see each step as you finish it.
Send one link insteadLaunching November 2026
Stripe: invite a team member
- In your Stripe Dashboard, open the Team tab in settings and click Add member.
- Enter their work email.
- Choose a role. Developer is Stripe's role for setting up an integration. Sandbox User keeps someone who only builds and tests out of your live account. View Only is for looking.
- Click Send invites. The invite expires after 10 days.
Developer can still create and refund payments, so switch it to View Only or remove it after the build. Stripe's account checklist is blunt: don't give team members your login credentials. Full steps: Stripe access, step by step, or see which Stripe role to pick.
Skip the back and forth. Let one link walk your client through it
Before you say yes
- Check the email address. It should be the developer's own work address, such as theo@northsidestudio.agency, not a personal inbox you don't recognize or a shared agency login. Shopify's advice works everywhere: confirm you know the person and expected the request.
- Pick the narrowest role. Ask what they need to do and give the smallest role that covers it. In Stripe's words: "Grant the lowest permission required by the user to perform their job." You can raise it later.
- Keep what's yours. Transfer rights, billing and ownership stay with you, and so does two-step verification on your own login.
- You hired this person and expected the request
- The email is their own work address
- The role is the narrowest that does the job
- Transfer, billing and ownership stay with you
- Your own two-step verification is on
- You know how to remove them when the project ends
One link per client, with every step checked. Reserve a founding place
Removing access when the project ends
- GoDaddy: On your Delegate Access page, select Edit next to their name, then Delete.
- Namecheap: Under Share Access, open the Edit drop-down, choose Remove, then Done.
- WordPress: Under Users > All Users, hover over their name and click Delete. Choose Attribute all posts and links to, pick your own user, then Confirm Deletion. The other option deletes their content.
- Shopify: In Settings > Users > Users & permissions, click the collaborator's name and use Remove in the Remove collaborator account section. Then click Generate new code under Security so the old code stops working.
- Stripe: On the Team tab, open the three-dot menu in their row, or click Remove member in their profile. They lose access straight away.
Get Set KeysOne link per client
If your developer used Get Set Keys, a handover link walks you through removing them from each platform when the work ends, one step at a time.
Send one link insteadLaunching November 2026
If a developer insists on your password
Ask which account and why. Every platform in this guide has an invite, so offer that first.
- Never share a sign-in code. Anyone with your password and the code from your phone can sign in as you.
- If a tool really has no second user, set a project-only password, share it through a password manager rather than email, and change it when the work ends. Our guide for agencies, Stop asking clients for passwords, sets out those steps in full.
- If they turn down an invite that exists, ask why. Saving a few minutes isn't worth your two-step verification, your record of changes and an easy exit.
Asked for a password? Ask which platform and why, offer an invite instead, never share a sign-in code, and if there is truly no second-user option, use a project-only password shared through a password manager and change it when the work ends
Get Set KeysOne link per client
On a Get Set Keys link, Porter, the setup helper, answers your questions from each step's own instructions. It never asks for a password and can't mark a step done.
Send one link insteadLaunching November 2026
Doing this for every client?
If you're the developer, a separate request for every platform gets slow. Get Set Keys gives each client one link that walks them through these steps and checks each one is done, so owners like Dana never have to send a password. Porter, the AI setup helper on every link, answers their questions as they go. You can reserve a founding place before it launches in November 2026.