What Scratch edits in Memberstack
- Member custom fields (text and rich text)
- Member metadata (free-form JSON)
- Login redirect URLs
- Member email addresses
How it works
Scratch pulls your Memberstack member list into local files. Your AI rewrites custom fields, metadata, and login redirects across the list. Member plan connections, subscription status, and system fields stay read-only. You review every change in Scratch and approve the ones that look right. Scratch pushes the edits back through the Memberstack API.
Good for normalizing custom fields after a signup-form change, standardizing metadata across imports, or fixing login-redirect drift between member tiers.