Tilda Roles and Permissions

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

Understanding Tilda's Permission Model

Role-Based Access System

Tilda uses a well-defined role-based permission model:

Two primary user types:

1. Owner - Full control and billing access
2. Collaborators - Four role types with varying permissions

Characteristics:

• Clear role definitions
• Flexible permission assignments
• Plan-based availability
• Granular access control

Access Hierarchy
└── Owner (Primary account)
    └── Collaborators
        ├── Administrator (full editing)
        ├── Editor (content editing)
        ├── Designer (design focus)
        └── Viewer (read-only)

User Types

Owner

Primary account holder with complete authority:

Full permissions:

• ✓ Edit all project pages
• ✓ Create/delete pages
• ✓ Design and layout control
• ✓ Settings and integrations
• ✓ SEO and analytics setup
• ✓ Domain management
• ✓ Billing and subscription
• ✓ Add/remove collaborators
• ✓ Assign collaborator roles
• ✓ Transfer project ownership
• ✓ Delete project
• ✓ Export project data
• ✓ Full analytics access

Unique characteristics:

• One owner per project
• Billing responsibility
• Cannot be removed (must transfer)
• Ultimate authority

Best practices:

• Keep credentials secure
• Use strong password
• Enable 2FA
• Don't share owner login

Collaborator Roles

Four distinct collaborative roles:

Collaborator Role Descriptions

Administrator

Full editing access without billing control:

Permissions:

• ✓ Edit all pages
• ✓ Create new pages
• ✓ Delete pages
• ✓ Publish/unpublish pages
• ✓ Clone pages
• ✓ Change page settings
• ✓ Edit navigation
• ✓ Upload images and files
• ✓ Access all blocks and elements
• ✓ Edit SEO settings
• ✓ Configure integrations
• ✓ Export pages
• ✓ View analytics (if granted)
• ✓ Manage project settings (limited)
• ✗ Access billing
• ✗ Add/remove collaborators
• ✗ Change subscription
• ✗ Transfer project
• ✗ Delete project

Use cases:

• Website manager
• Technical lead
• Senior designer
• Project manager
• Agency partner

Best for: Trusted team members who need comprehensive site management without financial access.

Security note: Can make significant changes; grant carefully.

Editor

Content editing focus:

Permissions:

• ✓ Edit existing pages
• ✓ Create new pages
• ✓ Edit text and content blocks
• ✓ Upload images (content-related)
• ✓ Change text styles
• ✓ Edit basic page settings
• ✓ Publish/unpublish pages (if granted)
• ✗ Delete pages (unless granted)
• ✗ Change page structure significantly
• ✗ Edit global styles
• ✗ Modify navigation menu
• ✗ Configure integrations
• ✗ Access advanced settings
• ✗ Export pages

Use cases:

• Content managers
• Marketing team
• Copywriters
• Blog editors
• Product managers

Best for: Team members who manage content without needing design or technical capabilities.

Typical workflow: Create and edit content, submit for review/publish (depending on settings).

Designer

Design and layout focus:

Permissions:

• ✓ Edit page layouts
• ✓ Modify design elements
• ✓ Change blocks and sections
• ✓ Edit visual styles
• ✓ Upload design assets
• ✓ Configure animations
• ✓ Edit typography
• ✓ Manage color schemes
• ✓ Work with custom CSS (if available)
• ✓ Clone and duplicate pages
• ✗ Delete pages (unless granted)
• ✗ Publish pages (unless granted)
• ✗ Edit significant content
• ✗ Configure integrations
• ✗ Access project settings

Use cases:

• Web designers
• UX/UI specialists
• Brand designers
• Frontend developers
• Creative team

Best for: Design professionals who need layout and visual control without content management responsibility.

Note: Can make significant visual changes; ensure alignment with brand guidelines.

Viewer

Read-only access:

Permissions:

• ✓ View all pages
• ✓ Browse project structure
• ✓ See page layouts and content
• ✓ Access preview mode
• ✓ View page settings (read-only)
• ✗ Edit any content
• ✗ Create pages
• ✗ Delete pages
• ✗ Publish pages
• ✗ Upload files
• ✗ Change settings
• ✗ Export pages

Use cases:

• Clients (review access)
• Stakeholders
• Reviewers
• Approval managers
• External consultants

Best for: Stakeholders who need to review progress without editing capability.

Workflow: Review and provide feedback through comments or external channels.

Permission Matrix

Detailed Permission Comparison

Note: "Optional" means owner can enable/disable per collaborator. "Limited" means restricted subset of permissions.

Advanced Permission Configuration

Page-Specific Access

Control which pages collaborators can access:

Configure:

Project Settings → Team → Edit Collaborator → Page Access

Options:

• All pages: Access entire project
• Specific pages: Select individual pages
• Folder/section: Access pages in specific folder

Example:

Collaborator: Marketing Editor
Role: Editor
Page Access:
☑ Blog folder (all posts)
☑ Marketing landing pages
☐ Home page (restricted)
☐ Product pages (restricted)

Use cases:

• Department-specific access
• Client access to their sections only
• Agency access to development pages
• Contractor access to assigned work

Custom Permission Sets

Advanced plans allow custom configurations:

Per collaborator, configure:

• ☑ Can publish pages
• ☑ Can delete pages
• ☑ Can export pages
• ☑ Can edit SEO
• ☑ Can configure forms
• ☑ Can access analytics
• ☐ Can edit navigation (restricted)

Example: Content Publisher Role:

Base role: Editor
Custom permissions:
☑ Can publish (enable)
☑ Can edit SEO (enable)
☐ Can delete pages (disable)
☐ Can export (disable)

Result: Can create, edit, and publish content with SEO, but cannot delete or export.

Permission Scenarios

Small Marketing Team

Setup:

Owner: Marketing director
├── Administrator: Web manager
├── Editor: Content writer 1
├── Editor: Content writer 2
└── Designer: Graphic designer

Workflow:

• Owner oversees project
• Administrator manages site structure
• Editors create content
• Designer handles visuals

Agency Managing Client Project

Setup:

Owner: Client
├── Administrator: Agency lead
├── Designer: Agency designer
├── Editor: Agency copywriter
└── Viewer: Client stakeholder

Rationale:

• Client retains ownership
• Agency has working access
• Client stakeholder can review
• Clear responsibility boundaries

Large Content Organization

Setup:

Owner: Publisher
├── Administrator: Technical manager
├── Editor (Blog): Blog editor (blog pages only)
├── Editor (News): News editor (news pages only)
├── Editor (Marketing): Marketing editor (landing pages)
├── Designer: Brand designer
└── Viewer: Compliance reviewer

Page-specific access:

• Blog editor: Blog folder only
• News editor: News folder only
• Marketing editor: Landing pages only
• Designer: All pages
• Reviewer: All pages (read-only)

E-commerce Project

Setup:

Owner: Store owner
├── Administrator: Store manager
├── Editor: Product manager (product pages)
├── Designer: Brand designer
└── Viewer: Inventory team (review product listings)

Plan-Based Limitations

Free Plan

Collaborator access:

• ✗ No team collaboration
• Owner only

Personal Plan

Collaborator limits:

• ✓ Up to 1 collaborator
• ✓ Basic roles
• Limited custom permissions

Business Plan

Collaborator capabilities:

• ✓ Up to 5 collaborators
• ✓ All role types
• ✓ Page-specific access
• ✓ Custom permissions

Business PRO

Enhanced features:

• ✓ Up to 10 collaborators
• ✓ Full permission control
• ✓ Advanced access settings
• ✓ Detailed activity tracking

Enterprise

Maximum capabilities:

• ✓ Custom team size
• ✓ Advanced role customization
• ✓ API access for user management
• ✓ Priority support

Best Practices

Assigning Roles

Principle of least privilege:

• ✓ Start with minimum necessary role
• ✓ Viewer before Editor
• ✓ Editor before Administrator
• ✓ Page-specific access when possible
• ✗ Don't default to Administrator

Decision guide:

1. Need to edit content? → Editor
2. Need to change design? → Designer
3. Need full project access? → Administrator
4. Only need to review? → Viewer
5. Need billing access? → Must be Owner

Security Practices

Account security:

• ✓ Strong passwords
• ✓ Individual accounts (no sharing)
• ✓ Regular access reviews
• ✓ Remove inactive collaborators
• ✓ Document access purpose
• ✗ Don't share owner credentials

Permission management:

• Review quarterly
• Adjust based on actual needs
• Remove when role changes
• Document permission decisions

Communication

When assigning roles:

• Explain role permissions
• Set clear expectations
• Provide training
• Document responsibilities
• Share guidelines

Limitations and Workarounds

No Approval Workflow

Limitation: No built-in content approval process.

Workarounds:

• Disable publishing for Editors
• Owner/Admin publishes after review
• Use comments for feedback
• External approval tools
• Team protocols

No Field-Level Permissions

Limitation: Cannot restrict specific fields or blocks.

Workarounds:

• Page-level access control
• Clear guidelines
• Regular audits
• Training

Troubleshooting

Collaborator Cannot Edit Page

Check:

1. Role allows editing
2. Page included in their access
3. Page not locked
4. Logged in correctly
5. Browser cache cleared

Collaborator Has Wrong Permissions

Fix:

1. Project Settings → Team
2. Edit collaborator
3. Change role or custom permissions
4. Save

Need More Granular Control

Options:

1. Upgrade plan
2. Use page-specific access
3. Custom permission configuration
4. Clear guidelines and training

Next Steps

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

Related Resources

• Tilda Plans & Features
• Team Collaboration Guide
• Tilda Security

Quick Reference

Role Selection Guide

Permission Decision Tree

What does user need?

Review only?
├─ YES → Viewer
└─ NO → Continue

Design/layout changes?
├─ YES → Designer
└─ NO → Continue

Content editing?
├─ YES → Editor
└─ NO → Continue

Full project access?
├─ YES → Administrator
└─ NO → Re-evaluate

Billing and team management?
└─ YES → Must be Owner (transfer if needed)