Jimdo Roles and Permissions

Comprehensive guide to Jimdo's user role system, access levels, and permission management for effective team collaboration.

Understanding Jimdo's Permission Model

Simplified Role System

Unlike complex CMS platforms, Jimdo uses a simplified permission model:

Two primary access levels:

1. Admin - Full control
2. Editor - Content management only

Key principles:

• Simple and easy to understand
• Plan-based limitations
• No granular permission customization
• Owner has ultimate control

Website Access Hierarchy
└── Owner (Account holder)
    ├── Admin Users (Full access)
    └── Editor Users (Content only)

Access Levels Explained

Owner

The ultimate authority:

Full control includes:

• ✓ All Admin permissions
• ✓ Billing and subscription management
• ✓ Website transfer capability
• ✓ Domain management
• ✓ Delete website
• ✓ Cancel subscription
• ✓ Export website data
• ✓ Upgrade/downgrade plan

Unique characteristics:

• Only one owner per website
• Transferable to another user
• Cannot be removed (must transfer ownership)
• Has billing responsibility
• Primary account contact

Cannot be shared: Owner credentials should never be shared.

Admin

Full website management without billing access:

Permissions:

• ✓ Edit all website content
• ✓ Modify design and layout
• ✓ Add/remove pages
• ✓ Configure website settings
• ✓ Manage SEO settings
• ✓ Add/edit blog posts
• ✓ Manage online store (if applicable)
• ✓ Configure forms and integrations
• ✓ Add/remove other users
• ✓ Change user access levels
• ✓ View analytics
• ✓ Manage domains (if delegated)
• ✗ Access billing information
• ✗ Cancel subscription
• ✗ Transfer ownership
• ✗ Delete website

Use cases:

• Website manager
• Senior developer
• Marketing director
• Agency partner
• Co-owner (without billing access)

Best for: Trusted team members who need full operational control.

Editor

Content-focused access:

Permissions:

• ✓ Edit existing page content
• ✓ Add/edit text and images
• ✓ Create/edit blog posts
• ✓ Upload images to gallery
• ✓ Manage blog comments
• ✓ Update product descriptions (basic)
• ✗ Add/remove pages
• ✗ Change website design
• ✗ Modify navigation menu
• ✗ Change website settings
• ✗ Manage SEO settings
• ✗ Add/remove users
• ✗ Configure forms
• ✗ Manage integrations
• ✗ Access analytics
• ✗ Manage domains

Use cases:

• Content writer
• Blogger
• Marketing coordinator
• Customer support (for blog/content updates)
• Freelance writer

Best for: Team members focused solely on content creation.

Jimdo Dolphin vs Jimdo Creator Permissions

Jimdo Dolphin (Modern Platform)

Access levels available:

• Owner
• Admin
• Editor

Features:

• Clear role definitions
• Easy to understand permissions
• Invitation-based access
• Real-time access changes

User interface:

Dashboard → Settings → Users & Access
- User list with roles
- Dropdown to change access level
- Clear permission descriptions

Jimdo Creator (Legacy Platform)

Access levels available:

• Owner
• Admin
• Editor (limited availability)

Features:

• Basic user management
• Less intuitive interface
• Fewer role options
• Legacy system constraints

User interface:

Admin → Settings → User Administration
- Basic user list
- Limited role information
- Email-based invitations

Recommendation: Jimdo Dolphin offers better user management capabilities.

Permission Matrix

Detailed Permission Comparison

Permission Scenarios by Use Case

Solo Business Owner

Setup:

└── Owner (You)

Recommendations:

• Keep owner credentials secure
• Enable two-factor authentication
• Regular backups
• Don't share login

Small Team (2-5 people)

Setup:

Owner (Business owner)
├── Admin (Website manager)
├── Editor (Content writer)
└── Editor (Social media manager)

Role assignments:

• Owner: Business owner (billing, final authority)
• Admin: Day-to-day manager (full operational control)
• Editors: Content team (blog, updates)

Best practices:

• One admin for business operations
• Editors for content contributors
• Regular access reviews

Marketing Agency Managing Client Site

Setup:

Owner (Client)
├── Admin (Agency lead)
├── Editor (Copywriter)
└── Editor (Designer - content updates only)

Considerations:

• Client retains ownership (billing)
• Agency has admin for development
• Content team has editor access
• Plan exit strategy (access removal)

Recommendation: Written agreement about access levels and duration.

E-commerce Store

Setup:

Owner (Store owner)
├── Admin (Store manager)
├── Admin (Inventory manager)
└── Editor (Product content writer)

Role assignments:

• Owner: Business owner (financial control)
• Admins: Operations team (orders, products, settings)
• Editor: Product descriptions only

Important: Admins can manage orders and payments.

Content-Heavy Blog/Magazine

Setup:

Owner (Publisher)
├── Admin (Editor-in-chief)
├── Editor (Writer 1)
├── Editor (Writer 2)
└── Editor (Writer 3)

Workflow:

• Editors create draft content
• Admin reviews and publishes
• Owner maintains platform

Best for: Editorial workflow with review process.

Limitations and Workarounds

No Granular Permissions

Limitation: Cannot customize specific permissions.

Example: Can't give user "edit content but not publish" or "add pages but not delete."

Workarounds:

• Use Editor role + manual review process
• Communication and trust
• Regular audits of changes
• Use external content approval tools

No Custom Roles

Limitation: Cannot create custom roles (e.g., "SEO Manager" or "Product Manager").

Workarounds:

• Choose closest role (Admin or Editor)
• Document specific responsibilities
• Training on role limitations
• Clear communication about access

Limited Audit Trail

Limitation: Basic change tracking.

Workarounds:

• Regular backups
• Screenshot important pages
• External change documentation
• Communication about updates

Plan-Based User Limits

Limitation: Number of users depends on plan:

• Start: 1 user (owner only)
• Grow: 5 users
• Business/VIP: 10 users

Workarounds:

• Remove inactive users
• Upgrade plan if needed
• Prioritize essential team members
• Share access responsibly (not recommended)

Security Best Practices

Access Level Assignment

Principle of least privilege:

• ✓ Start with Editor access
• ✓ Upgrade to Admin only if needed
• ✓ Regular access reviews
• ✗ Don't make everyone Admin

Questions to ask:

1. Does user need to change design? → Admin
2. Does user need to add/remove pages? → Admin
3. Only content updates? → Editor
4. Needs billing access? → Must be Owner

Account Security

For all access levels:

• ✓ Use strong, unique passwords
• ✓ Enable two-factor authentication (if available)
• ✓ Don't share login credentials
• ✓ Use password manager
• ✓ Log out on shared computers
• ✗ Don't use common passwords
• ✗ Don't write down passwords

For Owner specifically:

• Critical account protection
• Secondary email for recovery
• Document recovery process
• Backup authentication codes

Regular Audits

Monthly review:

• List all users with access
• Verify each user still needs access
• Confirm access levels appropriate
• Remove departing team members
• Check for suspicious activity

Quarterly deep audit:

• Review all website changes
• Update access documentation
• Test removal process
• Verify owner account security

Common Scenarios and Solutions

Scenario: Temporary Contractor Access

Need: Grant access to freelancer for 2-week project.

Solution:

1. Add as Editor (content work)
   OR
   Add as Admin (design work)

2. Set calendar reminder for removal date

3. Monitor their changes

4. Remove access when project complete

5. Export/document their work

Scenario: Designer Needs Design Access, Not Content

Need: Designer should change layout but not edit content.

Challenge: No "design-only" role in Jimdo.

Solution:

1. Grant Admin access (required for design)

2. Train on NOT editing content

3. Communication about boundaries

4. Review changes regularly

5. Consider using staging site (if available)

Scenario: Multiple Editors Need Publishing

Need: Blog writers need to publish without admin access.

Challenge: Editors can create content, but traditionally need approval.

Solution (Jimdo allows Editor publishing):

1. Grant Editor access

2. Editors can publish directly

3. Implement editorial guidelines

4. Admin reviews published content

5. Trust-based workflow

Scenario: Client Wants View-Only Access

Need: Show client progress without edit access.

Challenge: No "view-only" role in Jimdo.

Solution:

Option 1: Share preview links (no login needed)

Option 2: Schedule regular screenshots/demos

Option 3: Grant Editor access with strict instructions not to edit

Recommendation: Use preview links (safest)

Troubleshooting Permissions

User Can't Edit Content They Should Access

Possible causes:

1. User has Editor role but page is restricted
2. User viewing in preview mode, not edit mode
3. Browser cache issue
4. User logged into wrong account

Solutions:

1. Verify user role in Settings → Users & Access
2. Ensure user clicks "Edit" mode
3. Clear browser cache, log out/in
4. Check email address matches invitation

Admin Can't Access Certain Settings

Expected behavior: Admins cannot access:

• Billing information
• Subscription details
• Account deletion
• Ownership transfer

If other settings blocked:

• Log out and back in
• Check plan supports feature
• Contact Jimdo support

Editor Can See But Not Edit

Check:

1. Is user in "Edit" mode (not just viewing)?
2. Is page protected/published?
3. Is account active?
4. Did permissions recently change?

Solution: Click "Edit Website" button to enter edit mode.

Migrating Between Jimdo Platforms

Jimdo Creator to Jimdo Dolphin

User management improvements:

• Better user interface
• Clearer role definitions
• Improved invitation system
• Real-time updates

Migration considerations:

• Re-add users after migration
• Verify roles assigned correctly
• Test access levels
• Update documentation

Next Steps

• Adding and Removing Users - User management procedures
• Jimdo User Management - Overview
• Jimdo Help Center - Official documentation

Related Resources

• Jimdo User Permissions Guide
• Jimdo Plan Features
• Jimdo Security Best Practices

Quick Reference

When to Use Each Role

Use Owner for:

• Account holder with billing responsibility
• Single person with ultimate authority
• Cannot be shared

Use Admin for:

• Website managers
• Senior team members
• Full operational control needed
• Trusted partners/agencies

Use Editor for:

• Content writers
• Bloggers
• Marketing team (content only)
• Junior team members
• Temporary contributors

Permission Decision Tree

Does user need billing access?
├─ YES → Must be Owner (transfer ownership)
└─ NO → Continue...
    |
    Does user need to change design or add/remove pages?
    ├─ YES → Admin role
    └─ NO → Continue...
        |
        Only content editing?
        └─ YES → Editor role