When a client won't give you access, and how to get a yes

Why clients put off granting access, how to ask so they say yes, what to send them, and how to follow up politely when a request stalls.

5 min readReviewed October 2026

You sent the access request a week ago. Dana at Harbor Fitness replied "will do", and nothing has arrived since. It's easy to read that as a no, but a stalled request usually has a simpler cause: the client is uneasy about what they're handing over, unsure where to click, not the person who can do it, or just busy. Each has its own fix, and the right message turns "will do" into a finished invite. Here's how to tell which one you're facing, what to send, and how to follow up without straining the relationship. Role names below match each platform's help pages at the time of writing.

Get Set Keys sends your client one link with each invite, your email and the right role already filled in, sends reminders on its own, and checks each step is done.

Send one link instead

Why clients put off granting access

They're worried about security

To a business owner, "give us access to Stripe" can sound a lot like "give us your bank account". The worry is fair, and the answer is that an invite isn't the keys to everything. It gives you your own login with a role the client chooses, while they keep ownership, their password and the power to remove you.

Specific limits reassure more than general promises:

  • Stripe's Developer role can't invite team members or add and edit bank account details (Stripe).
  • In App Store Connect, an App Manager can be limited to the apps you work on (Apple).
  • In Google Play Console, the client can set an access expiry date when they invite you, so your access ends on its own (Play Console Help).

It also helps to say what each invite is for. "App Store Connect, so we can manage the app's App Store information and deliver new builds" is easier to agree to than a bare platform name, and it matches how Apple describes the App Manager role (Apple).

Put all of this in the request itself rather than waiting to be asked. If the client wants more detail, How to give your web developer access without sharing your password is written for them.

They don't know where to click

"Can you give us admin access to the website?" leaves the client guessing which company, which screen and which role, and vague tasks get put off. Name the platform, the menu, the role and your address, and link the exact clicks, such as the steps for App Store Connect, Stripe or Cloudflare.

They aren't the account owner

Your contact often isn't the person who set the account up. It may belong to a co-founder, a former employee or a previous web company, and only some roles can invite anyone at all.

Roles at a glance
PlatformWho can send the inviteWhere they do it
App Store ConnectThe Account Holder, an Admin or an App ManagerUsers and Access
Google Play ConsoleThe account owner or an adminUsers and permissions
StripeAn Administrator, IAM Administrator or Super AdministratorThe Team tab in Settings
CloudflareA Super Administrator with a verified emailThe Members page
Shopify collaborator requestsThe store owner or a user with the Administrator roleSettings, then Users

If your contact isn't on that list, ask one question: who set this account up? Then give them steps they can forward to that person, with your email and role written in, so nothing gets lost along the way.

They're busy

Access is a short task with no deadline unless you give it one, so it slides behind everything that has one. Give each request a date and say what it unblocks. "We need this by Thursday to start the build on Monday" gets done. "When you get a chance" doesn't.

How to ask so they say yes

The request that gets a quick yes is specific, small and clearly safe.

  • Lead with what they keep: ownership, their password and the ability to remove you whenever they like.
  • Ask for the smallest role that does the job, and name it. A client who reads "App Manager for the Harbor Fitness app" knows exactly what they're agreeing to.
  • Give one named address, such as theo@northsidestudio.agency, and use it everywhere.
  • Put everything in one message, ordered by what unblocks work first.
  • Mention expiry. App Store Connect invitations expire 3 days after they're sent (Apple), so ask for that one on a day you can accept it. What to do when an invite expires covers the rest.

Ask for this

  • An App Manager invite to theo@northsidestudio.agency for the Harbor Fitness app, by Thursday
  • The Stripe Developer role for the same address, so we can connect payments
  • One message with every request and a date for each

Not this

  • "Can you give us admin access to everything?"
  • "Send over the logins when you get a chance"
  • Five separate emails, one per platform

Skip the back and forth. Let one link walk your client through it

What to send them

Here's a message Theo at Northside Studio might send. It names the platform, the role and the date, and it answers the security question before Dana has to ask it.

Hi Dana, to start the app build on Monday we need two invites from you by Thursday. Both give us our own login with a limited role. You keep ownership and your password, and you can remove us at any time.

  1. App Store Connect: in Users and Access, invite theo@northsidestudio.agency as App Manager for the Harbor Fitness app. Apple's invite expires after 3 days, so Thursday morning is ideal. Steps
  2. Stripe: in Settings, open the Team tab and add the same address with the Developer role. It can't invite anyone else or change your bank details. Steps

If a screen looks different from the steps, send me a screenshot and I'll point you to the right button.

If that screenshot does arrive, When a client can't find the setting walks through the usual reasons.

One link per client, with every step checked. Reserve a founding place

If they send a password instead

Sometimes a client who wants to help replies with their password. Thank them, don't use it, and ask them to change it, then send the invite steps again. Explain that the invite is quicker in the long run. Apple requires two-factor authentication or two-step verification for everyone who signs in to App Store Connect (Apple), and a sign-in on a new device or the web can need a code from the owner's devices (Apple Support). Working from their login can mean asking them for codes. With an invite, the codes come to you.

Sending this to a client? Send one link instead

When to escalate, politely

If the request still hasn't moved after a reminder, step up gently. The aim is to protect the client's launch date, not to win an argument.

How it goes
  1. Resend the steps with a date and what's waiting on them
  2. Offer a short call to do it together while they share their screen
  3. Ask who else can send it: the owner, an admin or whoever set the account up
  4. Tell the project sponsor what's blocked, in one neutral line
  5. Confirm the new timeline in writing

A few lines that keep it friendly:

  • "I know it's a busy week. Would a short call tomorrow help? We can do it together."
  • "If someone else looks after the Apple account, I'm happy to send them the steps directly."
  • "Without App Store Connect access by Friday, the launch moves back a week. If we can sort it this week, we keep the original date."

Whatever you agree, put the new date in writing, with the reason, so nobody is surprised later.

Doing this for every client?

Get Set Keys gives each client one link that walks them through every access step, with your email and the right role filled in, and checks that each one is done. Porter answers their questions straight away and passes anything it can't answer to you. You can reserve a founding place before Get Set Keys launches in November 2026.

Sources

  1. Add and edit users (App Store Connect Help)
  2. Role permissions (App Store Connect Help)
  3. Sign in to your developer account (Apple Developer Account Help)
  4. Two-factor authentication for Apple Account (Apple Support)
  5. Edit access to apps (App Store Connect Help)
  6. Add developer account users and manage permissions (Play Console Help)
  7. User roles (Stripe Documentation)
  8. Start a team (Stripe Documentation)
  9. Manage account members (Cloudflare Fundamentals docs)
  10. Collaborator accounts (Shopify Help Center)

Platforms change their screens often. Every step here was checked against these official pages in October 2026.

Send one link instead of this guide.

Get Set Keys walks your client through each step and checks it is done. Ten founding places, launching November 2026.

Reserve a place

Step by step, per platform