Technical Access Request
Document ID: WBL-OB-TAR-[ID]-v1.0
Project: [PROJECT NAME]
Client: [CLIENT NAME]
Project Lead: [PM NAME] — [PM EMAIL]
Date Issued: [DATE]
Access Required By: [DATE]
Security Notice: Never send passwords, API keys, or sensitive credentials by email, Slack, or any unencrypted channel.
How to share credentials with Webility:
- Preferred method: [1Password Share link / LastPass Share / Bitwarden Send] — your project lead will send you a secure link
- Alternative: Our secure credential form at [URL]
- Never: Email, WhatsApp, Google Doc, or any public/shared document
If you have a corporate password manager or secrets vault, ask your project lead about direct vault-to-vault transfer.
Webility stores all received credentials in our encrypted secrets manager, with access restricted to personnel assigned to your project. Credentials are revoked from our systems at project handover and replaced with Client-owned accounts.
Section 1 — Domain & DNS
| Item | Details | Access Method |
|---|
| Domain registrar name | (e.g., GoDaddy, Namecheap, Cloudflare, Google Domains) | |
| Domain registrar login URL | | |
| Registrar account username / email | | Via secure link |
| Registrar account password | | Via secure link |
| Two-factor authentication (2FA) | ☐ Yes ☐ No | If yes: can you generate a recovery code or temporary access code? |
| DNS managed separately? | ☐ Yes — by: ___________ ☐ No | |
| DNS management platform (if separate from registrar) | | |
| Primary domain(s) | | |
| Additional domains / subdomains relevant to project | | |
DNS change authorization: Who must approve DNS changes?
Are there any DNS TTL or change-freeze restrictions? (e.g., corporate IT policy requires 48-hour notice for DNS changes)
Section 2 — Hosting & Server Access
2.1 Current Hosting Provider
| Item | Details |
|---|
| Hosting provider name | |
| Hosting plan type | ☐ Shared ☐ VPS ☐ Dedicated ☐ Cloud (provider: ___) ☐ Platform-managed (Shopify, Vercel, etc.) |
| Control panel type | ☐ cPanel ☐ Plesk ☐ DirectAdmin ☐ Custom dashboard ☐ None |
| Control panel URL | |
| Control panel username | Via secure link |
| Control panel password | Via secure link |
| Server IP address | |
| Server location / region | |
| PHP version | |
| Server OS | (e.g., Ubuntu 22.04, CentOS) |
2.2 SSH / SFTP Access
| Item | Details |
|---|
| SSH / SFTP hostname | |
| Port | (default: 22) |
| Username | Via secure link |
| Authentication method | ☐ Password ☐ SSH key pair |
| Password (if password auth) | Via secure link |
| SSH private key (if key auth) | Via secure link |
| Root access available? | ☐ Yes ☐ No — sudo only ☐ No access |
Note: Plain FTP (unencrypted) should not be used. If only FTP is available, please flag this to your project lead so we can discuss secure alternatives.
(Complete if hosted on Vercel, Netlify, AWS, GCP, DigitalOcean, Azure, etc.)
| Item | Details |
|---|
| Platform name | |
| Account email | Via secure link |
| Account password | Via secure link |
| Preferred method | ☐ Share account credentials ☐ Invite launchko@[...] as team member |
| Team/Organization name on platform | |
| Project / app name on platform | |
| Region / datacenter location | |
| Any environment variables (production) | Via secure link — provide a list of key names and values |
Section 3 — CMS & Website Admin
3.1 CMS Login
| Item | Details |
|---|
| CMS platform | ☐ WordPress ☐ Shopify ☐ Webflow ☐ Sanity ☐ Contentful ☐ Squarespace ☐ Wix ☐ Other: ___ |
| CMS admin URL | |
| Admin username / email | Via secure link |
| Admin password | Via secure link |
| 2FA enabled? | ☐ Yes ☐ No |
| If 2FA: recovery option available for Agency? | |
3.2 Database Access (if applicable)
| Item | Details |
|---|
| Database type | ☐ MySQL ☐ PostgreSQL ☐ MariaDB ☐ MongoDB ☐ Other: ___ |
| Database host | |
| Database name | |
| Database username | Via secure link |
| Database password | Via secure link |
| phpMyAdmin URL (if available) | |
| Any tables that must NOT be touched | |
3.3 Staging / Development Environment
| Item | Details |
|---|
| Staging site URL | |
| Staging admin credentials | Via secure link |
| Staging server access | Via secure link |
| Is staging auto-synced from production? | ☐ Yes ☐ No |
| Any restrictions on staging environment? | |
| Tool | Account Owner | Access Method | Login / Property ID |
|---|
| Google Analytics 4 | | ☐ Add launchko@gmail.com as Editor ☐ Share credentials | GA4 Property ID: |
| Google Search Console | | ☐ Add launchko@gmail.com as Owner ☐ Share credentials | |
| Google Tag Manager | | ☐ Add as Editor ☐ Share credentials | Container ID: |
| Google Ads | | ☐ Add as linked account ☐ Share credentials | |
| SEMrush / Ahrefs / Moz | | ☐ Add as team member ☐ Not required | |
| Hotjar / Microsoft Clarity | | ☐ Add as team member ☐ Not required | Site ID: |
| Other analytics tool | | | |
Preferred method for Google tools: Add the Agency's Google account ([Webility LLC GOOGLE ACCOUNT]) as an admin/editor on each property. Do not share your Google account password.
Section 5 — Third-Party Integrations & APIs
For each third-party service integrated with or required for the project, provide credentials or API access:
5.1 CRM
| Item | Details |
|---|
| CRM platform | (e.g., HubSpot, Salesforce, Pipedrive) |
| Access method | ☐ Admin invite ☐ API key ☐ OAuth |
| API key or access token | Via secure link |
| Relevant portal / account ID | |
| Pipelines / stages we should know about | |
| Any data we should not modify | |
5.2 Email Marketing
| Item | Details |
|---|
| Platform | (e.g., Mailchimp, Klaviyo, Brevo, ActiveCampaign) |
| Access method | ☐ Team invite ☐ API key |
| API key | Via secure link |
| Account ID / username | |
| Lists / audiences we'll be working with | |
| Transactional email provider (if separate) | |
5.3 Payment Gateway
| Item | Details |
|---|
| Payment provider | (e.g., Stripe, PayPal, Square) |
| Access method | ☐ Team invite ☐ API keys (test + live) |
| Test API key (publishable) | Via secure link |
| Test API key (secret) | Via secure link |
| Live API key (publishable) | Via secure link — only when ready for production |
| Live API key (secret) | Via secure link — only when ready for production |
| Webhook endpoint requirements | |
| Any existing subscriptions / recurring billing we must not disrupt | |
5.4 Booking / Scheduling
| Tool | Access Method | Credentials |
|---|
| (e.g., Calendly, Acuity, Mindbody) | ☐ API ☐ Embed code only ☐ Admin invite | Via secure link |
| Platform | Access Method | Credentials / API Keys |
|---|
| n8n / Make / Zapier | ☐ Team invite ☐ New instance | Via secure link |
| Anthropic / OpenAI / Google AI | ☐ API key ☐ New account for project | Via secure link |
| Database (Supabase / Airtable / etc.) | ☐ Team invite ☐ API key | Via secure link |
| Vector database (Pinecone / Weaviate / etc.) | ☐ API key | Via secure link |
5.6 Other Integrations
| Tool / Service | Purpose | Access Method | Credentials |
|---|
| | | |
| | | |
| | | |
Section 6 — SSL & Security
| Item | Details |
|---|
| SSL certificate provider | (e.g., Let's Encrypt, Comodo, DigiCert) |
| SSL expiry date | |
| SSL managed by | ☐ Hosting provider (auto-renew) ☐ Manual renewal ☐ Agency (if on Webility hosting) |
| Web Application Firewall (WAF) | ☐ Yes — provider: ___________ ☐ No |
| Cloudflare enabled? | ☐ Yes ☐ No |
| Cloudflare account access | Via secure link (if changes are required) |
| Security plugin (WordPress) | (e.g., Wordfence, Sucuri) |
| Tool | Purpose for Project | Access |
|---|
| Slack workspace | ☐ Client to invite Agency ☐ Agency to create shared channel | Workspace URL: |
| Microsoft Teams | ☐ Client to invite Agency ☐ Not used | |
| Google Workspace / Drive | ☐ Client to share folder ☐ Agency to create folder | |
| Figma organization | ☐ Client to invite as editor ☐ Agency account used | |
| GitHub / GitLab organization | ☐ Client to invite ☐ Agency org used | Repository URL: |
| Notion workspace | ☐ Client to invite ☐ Agency workspace used | |
| Role | Name | Email | Phone | Availability |
|---|
| Client Primary Technical Contact | | | | |
| Client IT / System Administrator | | | | |
| Hosting Provider Support (if external IT manages hosting) | | | | |
| Domain Registrar Account Holder | | | | |
| Emergency Decision-Maker (if primary contact unavailable) | | | | |
IT / security policy notes (e.g., all server changes require change management ticket; IP whitelist required for server access):
Section 9 — Access Security Checklist (Agency Internal)
To be completed by Webility Project Lead upon receiving access.
Access Log
Maintained by Agency. Records all credentials received and their status.
| System | Access Level | Date Received | Received From | Transferred at Handover | Date Transferred |
|---|
| | | | ☐ Yes ☐ N/A | |
| | | | ☐ Yes ☐ N/A | |
| | | | ☐ Yes ☐ N/A | |
| | | | ☐ Yes ☐ N/A | |
Webility — WBL-OB-TAR-[ID]-v1.0 | CONFIDENTIAL — contains security-sensitive information.
Distribute only to authorized personnel. Do not print unless necessary. Do not store in shared drives.