Knowledge base
Create a Netlify personal access token and connect it, so you can publish static sites to your own Netlify account from your dashboard.
Connecting your own Netlify account lets you publish a static site to your Netlify account from your Zinn® dashboard. You own the project and the bill; we handle the deploy, the custom domain and the DNS records.
A Netlify account. Netlify's free plan can be used; its limits are Netlify's, and on a busy account the one you meet first is usually the number of deploys — Netlify allows a few per minute and about a hundred a day.
In Netlify, open Applications → Personal access tokens and choose New access token. Name it, choose an Expiration, and press Generate token. If your team signs in with SAML single sign-on, tick Allow access to my SAML-based Netlify team and be signed in through it. Copy the token — Netlify shows it once. No scopes need choosing.
Open Integrations in your dashboard and choose Connect an account. Pick Static hosting (Netlify, Vercel) as the group and Netlify as the account, fill in API token, and press Connect account.
We test what you paste before anything is saved. A key that does not work is never stored, and the answer says what was wrong with it. A key that works is kept encrypted in our secrets vault — never in our database — and is never shown again, not even to you.
target. Choose it and we publish the site's build to a project on your account.
needs so the domain resolves to the new host.
your own vendor dashboard.
It worked and then stopped. Resetting your Netlify password invalidates every personal access token made before the reset, and tokens also expire on the date you chose. Generate a new token and connect it.
A deploy is refused as rate-limited. Netlify limits how often an account may deploy. Wait a few minutes; a site that was not deployed is left exactly as it was.
It says the key was rejected. Almost always one of three things: a space or a line break copied with it, a key that has expired, or a key that was revoked or regenerated after you copied it. Create a fresh one and paste it again.
It connects, but something later fails. The key authenticates but lacks a permission the action needs. Create a new key with the permissions listed above, then disconnect the old connection and connect the new key.
Open Integrations, find the account and press Disconnect. That deletes the stored key at once. Anything that was using it stops at its next action, and the screens that depended on it say so rather than failing quietly.
Disconnecting does not undo what was already done — records, deployments or settings we changed on your account stay as they are. If you think the key itself may have leaked, also revoke it at the vendor; disconnecting removes our copy, not theirs.
What we have been writing about hosting, SEO and running sites at scale.
How hosting shapes indexing and link equity in 2026: keeping pages indexed, vetting aged domains before you build on them, link building without a footprint, and an honest line on what infrastructure can and cannot do for SEO.
Read the post →A practical checklist for fast, secure WordPress: server-level caching, a per-site object cache, the handful of plugins worth running, keeping the stack current, and the WooCommerce pages you must never cache.
Read the post →What actually separates good managed hosting from a cheap box with a control panel — migrations, backups, isolation, real caching and honest scaling — and how to judge it before you commit.
Read the post →Support is included on every plan, the desk is open 24 hours a day, and you can write to us in any of our 58 languages — we answer you in yours.
Contact support → All articles →