Settings

Shop

Connections

Storage

Settings -> Storage keeps your uploads (images, book files, course and workshop resources, collection files, videos, logos, bank transfer receipts, licence release zips) in your own storage account instead of on this site. Every plan can use it.

1. Pick a provider and enter its keys. The "How to set up" note under each one walks you through it.
   • S3-compatible: Amazon S3, Cloudflare R2, DigitalOcean Spaces, Wasabi, Backblaze B2, MinIO and others. Choosing your service fills in hints for the endpoint and region. Give a Public URL only if the bucket serves files publicly (or has a domain or CDN in front of it): your images then load straight from it. Without one, files reach your visitors through your site.
   • Google Drive, OneDrive, Dropbox: enter the client ID and secret of your own app, Save, then click Connect and sign in. Files go in a folder named after your site.
2. Switch it on and Save. We first write, read back and delete a small test file; storage is switched on only if that works. Test connection runs the same check at any time.
3. From then on, every new upload goes to your storage. Files you uploaded before stay where they are and keep working. Move my files copies them over (each file is checked after copying and only then removed here); it runs in the background and the page shows how far it got. Bring my files back does the reverse.
4. Switching off sends new uploads back to this site; files already in your storage keep working as long as it stays connected. Disconnect removes your keys from this site, and is only possible once every file has been brought back.

Keys you save are never shown again (only their last characters). If your storage refuses an upload, the form says so: the file is never quietly kept here instead. Paid files (book downloads, resources, collection files) are never public: buyers get them through their download links as before. Customer profile pictures go to your storage only when it has a Public URL. System health shows whether your storage is connected and when it was last tested. Not available on the public demo sites.

AI

Settings -> AI connects your own Claude, ChatGPT or Gemini account, so you can get AI help on your site (Blog -> Posts -> Write with AI, Appearance -> Theme -> Bring your theme). Every plan can use it. You bring your own API key, so your AI provider bills you directly for what you use; a blog post usually costs a few cents.

1. Pick a provider and follow its steps to get an API key: the Claude Console for Claude, the OpenAI platform for ChatGPT, Google AI Studio for Gemini. An API key is not the same as a chat subscription such as ChatGPT Plus or Claude Pro, which other apps cannot use.
2. Paste the key, keep or change the model, and click Save and test. We send one tiny request to check that the key and model work, and show the answer.
3. The AI buttons appear once a key is saved. Remove key hides them again.

Your key is never shown again (only its last characters). AI runs only when you click a button, and what it writes fills your form (or, for a theme, a draft) for you to check: nothing is published on its own. For Write with AI we send your brief, what you are writing, your name, profession and About text, and for a post the titles and descriptions of your last three published posts; for Bring your theme, your images (scaled down, without file names or camera data), your note and the list of themes, fonts and layouts. Nothing about your customers or sales is ever sent. If your provider refuses (wrong key, no credit, an unknown model), the page tells you why. Not available on the public demo sites.

System

• System health: see Site health.
• Backups: one .zip of your whole site (see below).

Backups

Settings -> Backups makes a backup of everything that makes your site: pages, posts, products, sales, customers, memberships, settings, your team's accounts and roles, and every uploaded file (images in all their sizes, book files, course resources, receipts, licence releases). Visitor statistics and the activity log are not included. Your external storage connection is not included either: it stays as it is.

• Create backup makes one now. The newest 5 are kept; download the ones you want to keep for longer.
• Download saves the .zip to your computer. It holds your team's password hashes and your encrypted keys, so keep it somewhere safe.
• Restore (site owner only) replaces everything on your site with the backup. Type your site's name to confirm. A backup of the site as it is right now is made first, automatically, so a restore can be undone by restoring that one. After a restore, you and your team sign in with the accounts and passwords in the backup.
• Restore from a file (site owner only) does the same with a .zip you downloaded earlier. Only a backup of this site, made here and not changed since, is accepted. Files up to 2 GB can be uploaded: large ones are sent in pieces, so keep the page open while it uploads. The restore then runs on the server; the page shows that it is working and the result when it is done, and you can leave and come back. One restore or import runs at a time.
• Moving to Self-hosted: upload the same .zip in the Self-hosted installer ("Restore from a backup") and your site moves over with its accounts. Payment gateway keys and email passwords may need to be entered again there.
• Import from a self-hosted site (site owner only): the other way round. Make a backup on your Self-hosted site (its Settings -> Backups), then upload that .zip here. Its pages, posts, products, sales, customers, settings and files replace what is on this site; your own account and team stay as they are, and the other site's accounts are not carried over (what they wrote becomes yours). Enter your payment gateway keys, email password and other secrets again afterwards. A backup of this site is made first, so the import can be undone.