Weebly uses a straightforward role-based permission system for site contributors. Understanding these roles ensures proper access control and team collaboration.
How Weebly Permissions Work
Role-Based Access
Weebly implements a simple hierarchy:
- Owner: Ultimate control over site and account
- Admin: Full site editing and management
- Editor: Content editing with limited settings
- Author: Blog-only contribution
Contributor → Role → Permissions → Site Access
Permission Structure
Site Access
├── Owner (one per site)
├── Admin (multiple allowed)
├── Editor (multiple allowed)
└── Author (multiple allowed, blog only)
Contributor Roles
Owner
Purpose: Complete site ownership and control
Key Capabilities:
✓ Full site editing
✓ Publish/unpublish site
✓ Manage contributors
✓ Access all settings
✓ Billing and subscriptions
✓ Domain management
✓ Transfer site ownership
✓ Delete site
✓ Export site
✓ View analytics
✓ Install/remove apps
✓ SEO settings
✓ E-commerce settings (if applicable)
Unique Permissions:
- Transfer site to another user
- Delete entire site
- Access billing information
- Change subscription plan
- Manage payment methods
- View invoices
Use Cases:
- Website owner
- Primary stakeholder
- Business owner
- Final decision maker
Limitations:
- Only one owner per site
- Cannot be removed (only transferred)
- Responsible for billing
Admin
Purpose: Full site management without billing access
Key Capabilities:
Content:
├── Edit all pages: ✓
├── Create pages: ✓
├── Delete pages: ✓
├── Publish changes: ✓
├── Edit blog: ✓
├── Manage media: ✓
└── Upload files: ✓
Design:
├── Edit theme: ✓
├── Customize design: ✓
├── Change layouts: ✓
├── Add elements: ✓
├── Modify CSS: ✓ (if available)
└── Responsive editing: ✓
Settings:
├── Site settings: ✓
├── SEO settings: ✓
├── Navigation: ✓
├── Forms: ✓
├── E-commerce: ✓ (if applicable)
├── Apps: ✓ (install/configure)
├── Contributors: ✓ (add/remove)
├── Billing: ✗
└── Site ownership: ✗
Analytics:
├── View stats: ✓
├── Traffic reports: ✓
├── E-commerce reports: ✓
└── Export data: ✓
Cannot Access:
- Billing and subscription
- Payment methods
- Invoices
- Transfer ownership
- Delete site
Use Cases:
- Site manager
- Lead developer
- Agency project manager
- Trusted team lead
Best For:
- Day-to-day site management
- Full editing without ownership
- Multi-person teams
Editor
Purpose: Content management with limited settings
Key Capabilities:
Content:
├── Edit pages: ✓
├── Create pages: ✓
├── Delete pages: ✓
├── Publish changes: ✓
├── Edit blog posts: ✓
├── Create blog posts: ✓
├── Upload images: ✓
└── Manage media library: ✓
Design:
├── Edit theme: Limited
├── Change colors: ✗
├── Change fonts: ✗
├── Add elements: ✓ (to pages)
├── Modify layouts: ✗
└── Custom CSS: ✗
Settings:
├── Site settings: ✗
├── SEO (page-level): ✓
├── Navigation: ✗
├── Contributors: ✗
├── Apps: ✗
└── E-commerce: Limited
Blog:
├── Create posts: ✓
├── Edit posts: ✓ (all posts)
├── Delete posts: ✓
├── Publish posts: ✓
├── Categories: ✓
├── Tags: ✓
└── Comments: ✓
Restrictions:
- Cannot change site-wide design
- Cannot manage contributors
- Cannot access site settings
- Cannot install apps
- Cannot view billing
Use Cases:
- Content writers
- Marketing team members
- Blog managers
- Client content updates
Best For:
- Content-focused work
- Non-technical team members
- Freelance content creators
Author
Purpose: Blog contribution only
Key Capabilities:
Blog:
├── Create draft posts: ✓
├── Edit own posts: ✓
├── Upload images to posts: ✓
├── Add tags: ✓
├── Add categories: ✓
├── Publish own posts: ✓ (or draft only, depending on settings)
├── Edit others' posts: ✗
├── Delete others' posts: ✗
└── Manage comments: ✗
Pages:
├── View: ✗
├── Edit: ✗
├── Create: ✗
└── Delete: ✗
Settings:
├── All settings: ✗
Typical Workflow:
- Author creates blog post
- Author saves as draft or publishes (based on permissions)
- If draft-only: Editor/Admin reviews and publishes
- Post appears on blog
Use Cases:
- Guest bloggers
- Contributing writers
- Content interns
- External contributors
Best For:
- Blog-only content creation
- Multiple blog contributors
- Content approval workflows
Permission Comparison Matrix
| Feature | Owner | Admin | Editor | Author |
|---|---|---|---|---|
| Edit pages | ✓ | ✓ | ✓ | ✗ |
| Create pages | ✓ | ✓ | ✓ | ✗ |
| Publish changes | ✓ | ✓ | ✓ | ✗ |
| Edit theme/design | ✓ | ✓ | Limited | ✗ |
| Change site settings | ✓ | ✓ | ✗ | ✗ |
| Manage contributors | ✓ | ✓ | ✗ | ✗ |
| Create blog posts | ✓ | ✓ | ✓ | ✓ |
| Edit all blog posts | ✓ | ✓ | ✓ | ✗ |
| Publish blog posts | ✓ | ✓ | ✓ | ✓/✗ |
| Install apps | ✓ | ✓ | ✗ | ✗ |
| SEO settings | ✓ | ✓ | Page-level | ✗ |
| View analytics | ✓ | ✓ | Limited | ✗ |
| E-commerce | ✓ | ✓ | Limited | ✗ |
| Billing access | ✓ | ✗ | ✗ | ✗ |
| Transfer site | ✓ | ✗ | ✗ | ✗ |
| Delete site | ✓ | ✗ | ✗ | ✗ |
Advanced Permission Features
Page-Level Permissions
Password-protected pages (all contributors can create):
Page Settings → Password Protection → Enable
Who can set:
- Owner: ✓
- Admin: ✓
- Editor: ✓ (on pages they create)
- Author: ✗
Use for:
- Client previews
- Members-only content
- Private pages
- WIP pages
Member Area Permissions
For membership sites:
Members Area → Permissions
Access control:
- Define member groups
- Set page access per group
- Manage member permissions
- Content restrictions
Who can configure:
- Owner: ✓
- Admin: ✓
- Editor: Limited
- Author: ✗
E-commerce Permissions
For Weebly stores:
Owner permissions:
✓ Product management
✓ Order processing
✓ Inventory
✓ Shipping settings
✓ Tax configuration
✓ Payment gateways
✓ Store settings
✓ Abandoned cart recovery
Admin permissions:
✓ Product management
✓ Order processing
✓ Inventory
✓ View reports
✓ Limited settings
✗ Payment gateways (view only)
✗ Tax settings (view only)
Editor permissions:
✓ Add products
✓ Edit products
✓ View orders
✓ Limited order processing
✗ Store settings
✗ Shipping/tax settings
Multi-Site Permissions
Account-Level Access
For users with multiple Weebly sites:
Team members (if available on plan):
- Access multiple sites
- Different roles per site
- Centralized management
Example:
Team Member: Jane Doe
├── Site A: Admin
├── Site B: Editor
├── Site C: Author
└── Site D: No access
Benefits:
- Single login
- Manage access centrally
- Consistent user across sites
Per-Site Isolation
Default behavior:
- Contributor access is per-site
- Adding to Site A doesn't grant access to Site B
- Must explicitly add to each site
Security benefit: Prevents accidental cross-site access
Special Permission Scenarios
Example 1: Agency Team Structure
Agency managing client sites:
Client Site: ABC Corp
Team:
├── Agency Owner: Owner role
│ (full control, billing access)
├── Project Manager: Admin role
│ (day-to-day management, no billing)
├── Designer: Editor role
│ (content and design, no settings)
├── Content Writer: Editor role
│ (content updates only)
└── Client Contact: Editor role
(content review and approval)
Example 2: Blog Team
Blog-focused site:
Blog Site: Tech Reviews
Team:
├── Site Owner: Owner role
│ (overall control)
├── Managing Editor: Admin role
│ (publish all content, manage blog)
├── Senior Writers: Editor role
│ (write and publish posts)
├── Junior Writers: Author role
│ (write drafts for review)
└── Guest Contributors: Author role
(occasional posts, approval required)
Example 3: E-commerce Store
Online store team:
Store: Fashion Boutique
Team:
├── Store Owner: Owner role
│ (financial access, full control)
├── Store Manager: Admin role
│ (products, orders, inventory)
├── Product Manager: Editor role
│ (product catalog only)
├── Content Manager: Editor role
│ (pages, blog, no products)
└── Social Media: Author role
(blog posts only)
Security Best Practices
Least Privilege Principle
Grant minimum required access:
Bad example:
Temporary contractor → Admin role
Reason: "Easier than figuring out exact needs"
Good example:
Temporary contractor → Editor role
Access: Specific pages only
Duration: Project timeline
Review: Before granting, after 30 days
Dangerous Permission Combinations
Be cautious with:
- Admin role: Full site control
- Owner transfer: Can't be undone easily
- App installation: Third-party code
- Custom code: Can break site
Mitigation:
- Limit Admin roles to trusted individuals
- Require approval for app installs
- Test changes on backup/staging
- Regular permission audits
Regular Audits
Monthly review:
- List all contributors
- Verify role appropriateness
- Check last access date
- Remove inactive contributors (30+ days)
- Update documentation
Audit questions:
- Does each person still need access?
- Is their role still appropriate?
- Have they accessed recently?
- Any security concerns?
Troubleshooting Permission Issues
Contributor Can't Perform Expected Action
Debug steps:
- Verify role: Check assigned role (Owner/Admin/Editor/Author)
- Check feature availability: Some features plan-dependent
- Browser/cache: Clear cache, try different browser
- Account status: Ensure invitation accepted
- Weebly status: Check if Weebly experiencing issues
Common issues:
- Wrong role assigned (Author vs Editor)
- Plan doesn't include feature
- Browser cache issues
- Invitation pending
Editor Can't Access Settings
Expected behavior: Editors can't access most settings
Solution:
- Upgrade to Admin role if needed
- Owner/Admin makes changes
- Use limited Editor features
Author Can't Publish
Expected behavior (depends on configuration):
- Some sites: Authors can publish
- Others: Authors create drafts only
Check settings:
Blog Settings → Author Permissions → Publish
Options:
- Allow authors to publish
- Require approval (draft only)
Can't See Billing
Expected behavior: Only Owner can access billing
Who needs billing access:
- Finance department: Transfer ownership temporarily
- Accountant: Provide read-only invoice access
- New owner: Transfer site ownership
No workaround: Billing = Owner only
Platform-Specific Notes
Weebly vs Weebly for Square
Differences:
Weebly (standalone):
- Traditional contributor roles
- Weebly billing
- Original permission system
Weebly for Square:
- Integrated with Square
- Square team permissions
- Combined Square + Weebly roles
- Square payment processing
Migration note: Role structure may differ
Mobile App Permissions
Weebly mobile apps:
- Same roles as web
- Mobile-specific features
- Push notifications
- Mobile editor tools
Limitations:
- Some advanced features web-only
- Admin tasks easier on desktop
- Complex design changes require web
Next Steps
- Adding & Removing Users - User management workflows
- Weebly User Management - Overview and best practices
- Weebly Help Center
Related Resources
- Weebly Help Center - Search for "contributor roles", "security", and "blog management" topics (direct topic links are no longer available)