---

name: framer-security-basics description: 'Apply Framer security best practices for secrets and access control.

Use when securing API keys, implementing least privilege access,

or auditing Framer security configuration.

Trigger with phrases like "framer security", "framer secrets",

"secure framer", "framer API key security".

' allowed-tools: Read, Write, Grep version: 1.5.0 license: MIT author: Jeremy Longshore jeremy@intentsolutions.io tags:

• saas
• framer compatibility: Designed for Claude Code

---

Framer Security Basics

Prerequisites

A security owner, least-privilege access policy, secret-manager references, domain/DNS ownership, and synthetic test project.

Output

Maintain a security receipt with identity scope, control result, access-review date, owner, and redacted incident state. Do not include keys, form submissions, or private content.

Error Handling

Deny unexpected permissions or publishing destinations, revoke access on suspected exposure, and route incidents through the designated owner.

Examples

Use a staging site to verify a temporary collaborator cannot publish to production, remove access, and record only the control outcome and opaque project reference.

Overview

Security best practices for Framer API keys, plugin development, and Server API access.

Instructions

Step 1: Credential Management

Credential	Scope	Where to Store
Server API Key (framer_sk_*)	Per-site	Secrets vault
Site ID	Per-site	Can be in config
Plugin auth tokens	Per-user session	Never persist

# .env (never commit)
FRAMER_API_KEY=framer_sk_abc123...
FRAMER_SITE_ID=abc123

# .gitignore
.env
.env.local

Step 2: Plugin Security

// Plugins run in Framer's iframe sandbox — limited browser APIs
// Never store secrets in plugin code (it's client-side)

// Fetch external data through your own API proxy
const data = await fetch('https://your-api.com/framer-data', {
  headers: { 'Authorization': `Bearer ${sessionToken}` },
});

Step 3: Server API Key Rotation

# 1. Generate new key in Framer site settings
# 2. Update in secrets vault
# 3. Test connection
node -e "
  const { framer } = require('framer-api');
  framer.connect({ apiKey: process.env.FRAMER_API_KEY, siteId: process.env.FRAMER_SITE_ID })
    .then(() => console.log('OK'))
    .catch(e => console.error('FAIL', e.message));
"
# 4. Revoke old key in site settings

Step 4: Security Checklist

• API keys in environment variables, never in code
• .env in .gitignore
• Plugin never stores or exposes API keys
• Server API accessed only from backend, never client
• Pre-commit hook scans for framer_sk_* leaks
• HTTPS-only for all API communication

Resources

• Framer Server API
• Plugin Security

Next Steps

For production deployment, see framer-prod-checklist.