Zyro Roles and Permissions | OpsBlu Docs

Zyro Roles and Permissions

How to manage user roles, permissions, and team access controls in Zyro. Covers available role types, permission boundaries, and access management best.

Understanding user roles and permissions in Zyro helps you manage team access effectively and securely.

Overview

Zyro manages user access through roles with predefined permission sets. The available roles and features depend on your Zyro plan.

Available Roles

Owner

Access Level: Full control

Permissions:

  • ✓ Full website editing access
  • ✓ Create and delete websites
  • ✓ Publish changes
  • ✓ Manage domain settings
  • ✓ Access billing and subscriptions
  • ✓ Manage team members
  • ✓ Account settings
  • ✓ Delete account

Limitations:

  • Only one owner per account
  • Ownership transfer requires contacting Zyro support — there is no self-service option
  • Account tied to owner's email

Best for:

  • Business owner
  • Primary account holder
  • Final decision maker

Admin (If Available)

Access Level: High control

Permissions:

  • ✓ Full website editing access
  • ✓ Create websites
  • ✓ Publish changes
  • ✓ Manage domain settings
  • ✓ Invite/remove team members (may be limited)
  • ✓ Access most settings

Limitations:

  • ✗ Cannot access billing
  • ✗ Cannot delete account
  • ✗ Cannot remove owner
  • Some features like custom code injection require a paid plan

Best for:

  • Project managers
  • Lead developers
  • Trusted team members
  • Agency employees

Editor (If Available)

Access Level: Content management

Permissions:

  • ✓ Edit website content
  • ✓ Use website editor
  • ✓ Upload images and files
  • ✓ Modify text and layouts
  • Publish changes (depends on settings)

Limitations:

  • ✗ Cannot manage team
  • ✗ Cannot access billing
  • ✗ Cannot delete websites
  • ✗ Cannot manage domains
  • ✗ Limited settings access

Best for:

  • Content creators
  • Designers
  • Copywriters
  • Client collaborators

Permission Matrix

Action Owner Admin Editor
Edit website content
Publish changes Limited
Create websites
Delete websites Limited
Manage domains
Access billing
Manage users Limited
Account settings Limited
Custom code Limited

Note: Zyro (now Hostinger Website Builder) permissions follow the roles outlined above. Premium features like custom code and e-commerce require a paid plan.

Plan-Specific Features

Free Plan

User Management:

  • Owner only
  • No collaborators
  • No team features

Workaround: Must upgrade to add team members.

Unleash Plan

User Management:

  • Owner access
  • Limited collaboration features (check current plan)
  • Basic team features are available on premium plans only

Best for: Solo entrepreneurs, small projects

eCommerce Plan

User Management:

  • Owner access
  • Team collaboration available
  • Multiple user support
  • Basic role management

Best for: Growing businesses, small teams

eCommerce Plus Plan

User Management:

  • Owner access
  • Full team management
  • Advanced role controls
  • Multiple team members

Best for: Larger teams, agencies, enterprises

What Each Role Can Access

Website Editor Access

All Roles (Owner, Admin, Editor):

  • Zyro website editor
  • Add/edit/delete pages
  • Modify layouts and sections
  • Upload images
  • Edit text content
  • Use AI tools
  • Preview changes

Differences:

  • Editor may need approval to publish
  • Admin and Owner can publish immediately
  • Owner has ultimate control

Website Settings

Owner:

  • All website settings
  • Domain management
  • SSL certificates
  • Custom code injection
  • SEO settings
  • Analytics integrations

Admin:

  • Most website settings
  • Domain management (usually)
  • Custom code (usually)
  • SEO settings

Editor:

  • Limited settings access
  • May access SEO basics
  • Limited to content-related settings

Account Settings

Owner:

  • Email and password
  • Billing information
  • Subscription management
  • Team management
  • Account deletion
  • Data export

Admin:

  • May access team settings
  • Limited billing view
  • Cannot delete account

Editor:

  • Profile settings only
  • Cannot access account settings

Managing Permissions

Assigning Roles

When inviting a team member:

  1. Choose appropriate role for their responsibilities
  2. Consider least-privilege principle
  3. Grant minimum necessary access
  4. Review and adjust as needed

Changing Roles

To change a user's role:

  1. Go to Account SettingsTeam
  2. Find the user
  3. Click Edit or Change Role
  4. Select new role
  5. Save changes

Effect: Changes apply immediately

Custom Permissions

Availability: Depends on plan

If available:

  • Customize role permissions
  • Create specific access levels
  • Restrict certain features
  • Fine-tune control

Check: Your plan documentation for custom permission options

Access Control Best Practices

Principle of Least Privilege

Rule: Grant minimum access needed

Examples:

  • Content writer → Editor role
  • Project lead → Admin role
  • Business owner → Owner role

Avoid: Giving everyone admin/owner access

Regular Access Review

Schedule: Review quarterly

Checklist:

  • List all users
  • Verify roles are still appropriate
  • Remove inactive users
  • Check for unnecessary permissions
  • Update as needed

Separation of Duties

Best Practice: Divide responsibilities

Examples:

  • Content team → Editor access
  • Dev team → Admin access
  • Finance → Owner access to billing

Benefit: Reduces risk, improves security

Common Scenarios

Hiring a Designer

Role: Editor Permissions: Edit content, upload images Restrictions: Cannot publish without approval

Setup:

  1. Invite with Editor role
  2. Grant access to specific websites (if possible)
  3. Communicate guidelines
  4. Review their work before publishing

Working with Agency

Role: Admin (for project manager) Permissions: Full editing, publish access Restrictions: No billing access

Setup:

  1. Invite agency PM with Admin role
  2. Agency can invite their team
  3. Set project timeline
  4. Remove access when project complete

Adding Business Partner

Consideration: Do they need billing access?

Options:

  • Needs billing: May need to add as co-owner (contact support)
  • No billing: Admin role sufficient

Setup:

  1. Determine appropriate role
  2. Invite to team
  3. Document access granted
  4. Review access regularly

Temporary Contractor

Role: Editor Duration: Limited

Setup:

  1. Invite with Editor role
  2. Set calendar reminder to remove access
  3. Monitor their changes
  4. Remove access when work complete
  5. Document access period

Security Considerations

Protecting Your Account

Owner Responsibilities:

  • Secure password
  • Enable 2FA (if available)
  • Monitor team access
  • Review activity logs
  • Respond to suspicious activity

Audit Trail

If available:

  • Review who made changes
  • Track publishing history
  • Monitor login activity
  • Check team modifications

Use for:

  • Security monitoring
  • Quality control
  • Accountability

Password Management

For all users:

  • ✓ Use unique, strong passwords
  • ✓ Enable 2FA if available
  • ✓ Never share passwords
  • ✓ Use password manager

For shared access (not recommended):

  • Change password after project
  • Limit duration of access
  • Monitor activity closely

Troubleshooting Permissions

User Can't Access Feature

Check:

  1. What is their role?
  2. What feature are they trying to access?
  3. Is it available on your plan?
  4. Are they logged in correctly?

Fix:

  • Upgrade their role if appropriate
  • Confirm plan includes feature
  • Verify account credentials
  • Contact Zyro support

Permission Denied Errors

Causes:

  • Insufficient role permissions
  • Plan limitations
  • Account issue

Fix:

  • Review user's role
  • Check plan features
  • Verify account status
  • Contact support if needed

Can't Remove User

Causes:

  • Owner cannot be removed
  • Don't have permission to remove users
  • Technical issue

Fix:

  • Only owner/admin can remove users
  • Contact owner if you're not
  • Try different browser
  • Contact Zyro support

Zyro-Specific Notes

Account-Level Access

Important: Zyro manages users at account level

Implications:

  • Users may see all websites on account
  • Cannot easily restrict per-website access
  • May need separate accounts for different clients

Workaround: Use separate Zyro accounts for different clients/projects

AI Tools Access

All editing roles can:

  • Use AI website builder
  • Generate content with AI
  • Regenerate designs

Consideration: Train team on AI tool usage

Custom Code Permissions

Varies by role:

  • Owner: Full access
  • Admin: Usually full access
  • Editor: May be restricted

For tracking implementation:

  • Owner or Admin role needed
  • Ensures proper code injection
  • Maintains tracking integrity

Next Steps

Additional Resources