When to use:

  • Backup before major configuration changes
  • Transfer settings to a new workspace
  • Share configuration with team members
  • Restore after accidental changes

Access: Settings → Data & Export → Export/Import Settings section

Export Settings

Quick Export

  1. Go to Settings → Data & Export
  2. Scroll to Export Settings
  3. Choose export type:
  • Without API keys (default) - Safe for sharing
  • With API keys - Full backup including credentials
  1. Choose format:
  • JSON (recommended) - Preserves all structure
  • CSV - Spreadsheet-compatible view
  1. Click Export Settings

File downloads as: illixis_settings_YYYYMMDD_HHMM.json

What's Included

Settings exported:

  • Brand voice and tone
  • Content strategy preferences
  • Title formats and writing style
  • Target audience definition
  • Brand keywords and competitors
  • Color scheme and styling
  • Email templates and signatures
  • Video script templates
  • Image generation preferences
  • Offer display settings
  • Banner ad defaults
  • GSC intelligence thresholds
  • Brainstorming themes
  • AI visibility tracking preferences

NOT included:

  • Third-party connections (GSC, GA4, email platforms)
  • Content, briefs, or generated articles
  • Analytics data
  • User accounts or permissions

Export Options

Without API keys (recommended for sharing):

  • Excludes sensitive credentials
  • Safe to share with team members
  • Safe to store in version control
  • Can be imported without overriding existing API keys

With API keys (full backup):

  • Includes all API credentials
  • Required for complete restore
  • Store securely (treat like passwords)
  • Useful for migrating workspaces

Import Settings

Quick Import

  1. Go to Settings → Data & Export
  2. Scroll to Import Settings
  3. Click Choose File and select your .json or .csv file
  4. Choose API key handling:
  • ☐ Override existing API keys (unchecked = keep your current keys)
  1. Click Import Settings

Your settings are applied immediately.

Import Behavior

Default (unchecked "Override API keys"):

  • Imports all non-sensitive settings
  • KEEPS your current API keys (doesn't overwrite)
  • Safe for importing shared configurations

With "Override API keys" checked:

  • Imports EVERYTHING including credentials
  • REPLACES your current API keys
  • Only use when restoring a full backup

Import Safety

Before importing, the system:

  • Creates automatic backup of current settings
  • Validates the import file format
  • Checks for missing or invalid fields
  • Skips unrecognized settings (for forward compatibility)

If import fails, your original settings remain unchanged.

Automatic Backups

How It Works

ILLIXIS automatically backs up your settings whenever you save changes:

  • Triggered on every settings save
  • Tracks which section changed
  • Records who made the change
  • Deduplicates identical backups (saves space)
  • Keeps last 30 backups per workspace

View Backup History

  1. Go to Settings → Data & Export
  2. Scroll to Settings History
  3. View table of recent backups:
  • Date and time
  • Section changed (Brand Voice, Content Strategy, etc.)
  • Changed by (user name)
  • Actions (Download, Restore)

Restore from Backup

  1. Find the backup you want to restore
  2. Click Restore for that backup
  3. Confirm restoration

Safety: Before restoring, the system creates a new backup of your current settings. You can undo the restore by restoring the "pre_restore_backup" entry.

Download a Backup

Click Download next to any backup to save it as JSON file.

Useful for:

  • Offsite backup storage
  • Comparing changes over time
  • Sharing configuration snapshots

Cross-Tenant Migration

Scenario: Copy Settings to New Workspace

From original workspace:

  1. Export settings with API keys (if you want to copy credentials)
  2. Save the JSON file

In new workspace:

  1. Import the saved JSON file
  2. Check Override API keys if you want to copy credentials
  3. Import

Result: New workspace has identical configuration to original.

Scenario: Share Configuration with Team

As configuration owner:

  1. Export settings without API keys
  2. Share the JSON file via email, Slack, etc.

As recipient:

  1. Import the shared JSON file
  2. Leave Override API keys unchecked
  3. Add your own API credentials in Settings

Result: Team member has your content strategy, voice, and preferences, but uses their own API keys.

Format Details

JSON Format (Recommended)

```json
{
"metadata": {
"exported_at": "2026-02-05T10:30:00",
"tenant_name": "Your Workspace",
"tenant_slug": "your-workspace",
"version": "1.0",
"includes_api_keys": false
},
"settings": {
"business_brand_name": "Your Brand",
"brand_tone": "professional, friendly, helpful",
"default_target_word_count": 1500,
...
}
}
```

Advantages:

  • Preserves data types (numbers, booleans, arrays)
  • Includes metadata for tracking
  • Easy to validate
  • Git-friendly (can diff changes)

CSV Format

```csv

ILLIXIS Settings Export

Tenant: Your Workspace

Exported: 2026-02-05T10:30:00

Includes API Keys: False

Setting,Value
business_brand_name,Your Brand
brand_tone,"professional, friendly, helpful"
default_target_word_count,1500
```

Advantages:

  • View in Excel or Google Sheets
  • Easy to review in table format
  • Can edit with text editor

Limitations:

  • No type preservation (everything becomes string)
  • No metadata section
  • Harder to validate

Troubleshooting

Import Failed: "Invalid JSON format"

Cause: File is corrupted or not valid JSON

Fix:

  1. Open file in text editor
  2. Validate JSON at jsonlint.com
  3. Check for missing commas, brackets, quotes
  4. Re-export from original source

Import Succeeded but Settings Look Wrong

Cause: File from different ILLIXIS version or modified manually

Fix:

  1. Go to Settings History
  2. Restore the automatic "pre_import_backup" entry
  3. Try exporting from original workspace again

API Keys Not Working After Import

Cause 1: Imported file didn't include API keys (export was "without API keys")

Fix: Add your API keys manually in Settings → Brand & Voice

Cause 2: Imported API keys belong to different account

Fix: Replace with your own API keys in Settings

Backup History Empty

Cause: Backups are only created when you save settings changes

No action needed: Make a settings change and save. Backup will appear.

Restore Creates Duplicate Backup

This is normal: System creates safety backup before every restore. It's intentional.

To clean up: Just ignore old backups. System auto-prunes after 30 backups.

Best Practices

Regular Backups

Manual export recommended:

  • Weekly during active development
  • Before major configuration changes
  • After perfecting your brand voice settings
  • When testing new strategies

Store exports:

  • Cloud storage (Dropbox, Google Drive)
  • Password manager (if includes API keys)
  • Version control (if no API keys)

Configuration Versioning

Use descriptive export filenames:
```
illixis_settings_before_rebrand_20260205.json
illixis_settings_summer_tone_20260620.json
illixis_settings_final_20260901.json
```

Team Collaboration

Share template configurations:

  1. Create "master" workspace with ideal settings
  2. Export without API keys
  3. Share with team via shared folder
  4. Team imports to their workspaces

Result: Consistent brand voice across team without sharing credentials.

Migration Checklist

When migrating to new workspace:

  1. ✅ Export settings with API keys
  2. ✅ Test API keys work in new workspace
  3. ✅ Verify brand voice matches original
  4. ✅ Check content generation produces expected results
  5. ✅ Reconnect integrations (GSC, GA4, email platforms)
  6. ✅ Test brief creation and content generation

Related Features

  • Export All Data (same page) - Complete GDPR export including content, briefs, videos, emails
  • Settings History (same page) - View and restore automatic backups
  • Account Switcher - Manage multiple workspaces
  • Audit Logs - Track who changed what settings and when

Need help? Contact support or check Settings → Help & Support

More in Account & Settings

User Roles & Permissions

Control what each team member can access and modify. ILLIXIS uses role-based access control RBAC to ensure team members have appropriate permissions for their responsibilities.

→
Approval Workflows

Control who reviews and approves content before it goes live. ILLIXIS approval workflows let you build multi-stage review chains with role-based approvers, deadlines, and automatic escalation.

→
Audit Logs

ILLIXIS automatically records every significant action in the platform with an immutable audit trail. Track who did what, when, and from where - critical for compliance SOC 2, GDPR, security investigations, and accountability.

→
White-Label Branding

Replace ILLIXIS branding with your own across the entire platform. Perfect for agencies delivering client work or businesses wanting a fully branded experience.

→
Two-Factor Authentication (2FA) Setup

Two-factor authentication 2FA adds an extra layer of security to your ILLIXIS account. When enabled, you'll need both your password and a verification code from your phone to sign in.

→
← Back to Help Center

Ready to lose the stack?

One platform. You approve. ILLIXIS executes. Marketing that just happens.

Join the waitlist•No spam, ever•Unsubscribe anytime
★First 20 founding members: 50% off any plan for your first year.

Marketing, Unstacked.