Connect a site
Create the custom integration in Ghost, connect the site, paste the snippet.
Create the custom integration
In Ghost Admin open Settings → Integrations and choose Add custom integration. Name it after the service so a colleague recognises it later.
Ghost shows the integration's Admin API key. Copy it; you will paste it into the connect form. Leave the Content API key alone, the service does not use it.
If you want imported bylines, or the referrers and page views in the analytics panel, also prepare the dedicated Administrator account described under bylines and copy its Staff access token from that account's own profile page in Ghost Admin.
Connect
In SponsorPass, open your workspace and choose Connect a site. The form asks for:
- Site address: the address readers use, including a subdirectory if your Ghost lives in one.
- Admin API key: the one you just copied.
- Staff access token (optional): the dedicated Administrator's, for imported bylines and for a post's referrers and page views in the analytics panel. With a shared byline the form shows no token field: paste it after connecting, under Settings → Connection (Reconnect with new credentials).
- Address on SponsorPass: a short name; your contributors' dashboard lives at
<name>.<our domain>. It cannot change later. - Bylines: one byline per contributor (imported), or one shared byline for every contribution.
The service checks the key against your site, reads the site's version, title and timezone, and registers the webhooks it listens to; each package's internal tag is created when you set the package up, or at its first draft. If the key is wrong, the site is on a plan without custom integrations, or the address is already connected, the form says exactly which.
Paste the snippet
After connecting, the site page shows a one-line <script> tag. Paste it in Ghost Admin under Settings → Code injection → Site header and save. The service checks your site once a day and the health panel shows when it saw the snippet. The snippet and theme page explains what the script does and how to place the button in a theme instead.
What the service stores
The Admin API key and the staff access token are stored encrypted with a key that lives outside the database. They are never shown again, never sent to a browser, and never written to a log. You can rotate either in Ghost at any time; the service notices the next time it talks to the site and asks you to reconnect.