Client access request email templates: ask, follow up, nudge

Copy-ready emails for asking a client for access: a first request, a friendly follow-up and a last nudge, plus the one-link version.

6 min readReviewed October 2026

The access request is often the first real task a client does for your project, and a clear one gets done in a single sitting. Below are three short emails you can copy: a first request, a friendly follow-up and a last nudge. Each uses placeholders like [Client name] and [Platform], and each comes with a note on why it works. At the end, you'll see how one setup link replaces the list of instructions altogether.

Get Set Keys turns this request into one link per client: each platform's steps with your email and the right role filled in, and every step checked when it's done.

Send one link instead

What every access request needs

Whatever the wording, a request is easy to finish when it has one named work email (such as theo@northsidestudio.agency), the role in the platform's own words (App Manager in App Store Connect, Domains Only at GoDaddy, Developer in Stripe), one line on where to click, a date, and an easy way to get help. Not sure which role to ask for? The client access checklist covers each area, from domains to app stores.

Checklist
  • One named work email for every invite
  • The role for each platform, in the platform's own words
  • One line on where to click
  • A date, ideally a weekday
  • An easy way to get help
  • No passwords or sign-in codes

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

Template 1: the first request

Send it within a day of kickoff, while the project is fresh.

Subject: [Project name]: [number] quick invites to get us started

Hi [Client name],

Thanks again for [the kickoff call]. To start building, we need access to [number] of your accounts. Each one is an invite you send from your own account, so your password stays with you and you can remove us at any time.

Please invite [your work email] to:

1. [Platform]: [role]. [Where to click]
2. [Platform]: [role]. [Where to click]
3. [Platform]: [role]. [Where to click]

Could you send these by [day, date]? Some invites expire within a few days, so a weekday when we can accept them straight away works best.

If a screen looks different from what I've described, reply with a screenshot and I'll point you to the right button.

Thanks,
[Your name]
[Agency name]

For the [Where to click] lines, these match each platform's help pages at the time of writing:

App Store Connect: App Manager. In Users and Access, click the add (+) button under People, enter our name and email, choose App Manager, click Next, select the app if a list appears, then click Invite.

GoDaddy: Domains Only. On your Delegate Access page, select Invite to Access, enter our name and email, choose Domains Only, then select Invite.

Stripe: Developer. In Settings, open the Team tab, click Add member, enter our email, choose Developer, then click Send invites.

The full steps live on the App Store Connect, GoDaddy and Stripe pages.

Why it works

  • It opens with the reason, so the list reads as the first step of the project rather than admin.
  • It tells the client what they keep: their password, and the power to remove you.
  • Each line carries the platform, the role and the clicks, so nothing needs a reply, and a screenshot beats describing a screen.

Template 2: the friendly follow-up

Send it two or three working days later, and only about what's left.

Subject: Re: [Project name]: [number] quick invites to get us started

Hi [Client name],

Thanks for the [Platform] invite. It worked, and we've already started on [task].

Just [number] to go: [Platform] and [Platform]. The steps are in my email below. [Platform]'s invite expires [time] after it's sent, so if you send it on [day], we'll accept it the same day.

If it's easier, we can do them together on a short call. Would [time option 1] or [time option 2] suit you?

Thanks,
[Your name]

Why it works

  • Thanks and progress come first, so it reads as an update, not a chase.
  • It names exactly what's left, with a reason for the timing and no pressure.
  • Two call times are easier to say yes to than "let me know".

Template 3: the last nudge

Use it when one platform is still missing and it's starting to hold up the work. Keep it to a single ask.

Subject: [Project name]: one thing before [milestone]

Hi [Client name],

We're ready to [next milestone, for example upload the first test build], and the only thing still missing is [Platform] access.

If you can invite [your work email] as [role] by [day], we'll stay on track for [date]. If that day doesn't suit, tell me what does and I'll adjust the plan.

Or I can call and we'll do it together. It only needs whoever manages your [Platform] account, and a few clicks.

Thanks,
[Your name]

Why it works

  • One ask, tied to the milestone it's holding up, so the client sees why it matters now.
  • The delay becomes a shared plan with a new date, not blame.
  • It still asks for an invite. If a client offers their password to save time, thank them and resend the steps. Stripe's own account checklist says not to give team members your login credentials.

Ask for this

  • An invite to theo@northsidestudio.agency as App Manager
  • GoDaddy delegate access with Domains Only
  • A Stripe team invite with the Developer role
  • One date and an offer to help

Not this

  • "Just send me the login"
  • "Read me the code from your phone"
  • A bigger role than the job needs
  • "Whenever you get a chance"

Sending this to a client? Send one link instead

Templates help, but each new client still means rewriting the list, and the replies arrive in separate threads. With a Get Set Keys setup link, the first email shrinks to this:

Subject: [Project name]: one link to give us access

Hi [Client name],

Here's one link with everything we need to start: [setup link]

It walks you through [number] short steps in your own accounts, with our email and the right role already filled in. You never share a password, and each step is checked off once it's done. If you get stuck, ask on the page: the setup helper answers from the step you're on, and anything else comes straight to us.

Could you work through it by [day, date]?

Thanks,
[Your name]

Here is what the link takes off your plate:

  • The instructions. Each platform's steps appear on the link, with your email and the role filled in.
  • The checking. Each step is confirmed by a one-click sign-in where the platform allows it, a live DNS check, or the platform's own invite email arriving at your private verification address. Shopify steps use the collaborator request code.
  • The questions. Porter, the AI setup helper on the link, answers from that step's instructions and live check results, and passes anything else to you, in one place.
  • The chasing. Reminders go out on their own, so templates 2 and 3 become the exception.

Small details that save a round trip

  • Invites expire. App Store Connect invitations expire 3 days after they're sent, though they can be resent (Apple). GoDaddy's expire if not accepted within 48 to 72 hours (GoDaddy). Ask for them on a day you can accept.
  • The right person has to send it. In App Store Connect, only the Account Holder, an Admin or an App Manager can add users. In Stripe, the Developer role can't invite anyone (Stripe), so the invite comes from the owner or an administrator.
  • Be ready to accept. GoDaddy delegates need their own GoDaddy account to accept.
  • Explain once, then link. If a client asks why you want an invite rather than their password, send them this plain guide for clients. Asking at kickoff? The kickoff email template folds this request into the first email.

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

Doing this for every client?

Get Set Keys gives each client one link that walks them through these steps and checks each one as it's done, so the request becomes one short email. Porter, the setup helper on every link, answers your client's questions straight away and passes anything it can't answer to you. Get Set Keys launches in November 2026, and you can reserve a founding place before launch.

Sources

  1. Add and edit users (App Store Connect Help)
  2. Invite a delegate to access my GoDaddy account (GoDaddy Help)
  3. Delegate access: Levels of permission (GoDaddy Help)
  4. Start a team (Stripe Documentation)
  5. User roles (Stripe Documentation)
  6. Account checklist (Stripe Documentation)

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