Strikingly Roles and Permissions | OpsBlu Docs

Strikingly Roles and Permissions

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

Guide to Strikingly's team member permission system, access levels, and collaboration features for effective website management.

Understanding Strikingly's Permission Model

Simplified Access System

Strikingly uses a straightforward permission model designed for ease of use:

Two primary user types:

  1. Owner - Full control and billing access
  2. Team Members - Various levels of editing access

Characteristics:

  • Simple and intuitive
  • Plan-based availability
  • Easy to understand
  • Limited but effective customization
Access Hierarchy
└── Owner (Primary account)
    └── Team Members
        ├── Full Access
        ├── Limited Access (sections)
        ├── Blog Editor
        └── Store Manager (e-commerce)

User Types

Owner

Primary account holder with complete control:

Full permissions:

  • ✓ Edit all site sections
  • ✓ Add/remove pages
  • ✓ Design and layout control
  • ✓ Settings and SEO
  • ✓ Domain management
  • ✓ Billing and subscription
  • ✓ Add/remove team members
  • ✓ Set team member permissions
  • ✓ Transfer site ownership
  • ✓ Delete website
  • ✓ Export website data
  • ✓ Analytics access

Unique characteristics:

  • Only one owner per site
  • Billing responsibility
  • Cannot be removed (must transfer)
  • Ultimate authority

Best practices:

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

Team Members

Invited collaborators with editing access:

Available roles (all plans, including Free — up to 10 teammates per site):

  • Administrator — Full access except cannot delete site or manage teammates
  • Editor — Can edit all content but cannot access analytics, settings, form responses, or Simple Store
  • Store Manager — Can edit only Simple Store items
  • Blogger — Can write blog posts but cannot publish them

Access controlled by:

  • Role assigned by site owner
  • Only the site owner can add or remove collaborators
  • Specific permissions granted

Team Member Access Levels

Full Access

Comprehensive editing capability:

Permissions:

  • ✓ Edit all website sections
  • ✓ Add new pages
  • ✓ Remove pages
  • ✓ Modify navigation menu
  • ✓ Upload images to any section
  • ✓ Edit blog posts
  • ✓ Manage store products (if e-commerce)
  • ✓ Update SEO settings (basic)
  • ✓ Change design elements
  • ✓ Publish changes immediately
  • ✗ Access billing
  • ✗ Manage domain
  • ✗ Add/remove team members
  • ✗ Change subscription
  • ✗ Transfer site

Use cases:

  • Website manager
  • Marketing director
  • Content manager
  • Agency partner
  • Co-administrator

Best for: Trusted team members needing comprehensive site management.

Security note: Can make significant changes; grant carefully.

Limited Access (Section-Specific)

Restricted to specific pages/sections:

Permissions:

  • ✓ Edit assigned sections only
  • ✓ Update content on permitted pages
  • ✓ Upload images for their sections
  • ✓ Change text and media
  • ✗ Add/remove pages
  • ✗ Edit navigation
  • ✗ Access other sections
  • ✗ Modify site design
  • ✗ Access settings

Configuration example:

Team Member: John Doe
Allowed sections:
☑ About Us page
☑ Services page
☑ Team page
☐ Home page (restricted)
☐ Contact page (restricted)
☐ Blog (restricted)

Use cases:

  • Department content managers
  • Regional managers
  • Specialized editors
  • Limited-scope contractors

Best for: Team members responsible for specific content areas.

Availability: Higher-tier plans (Pro, VIP, Enterprise)

Blog Editor

Blog-focused access:

Permissions:

  • ✓ Create blog posts
  • ✓ Edit blog posts
  • ✓ Delete blog posts
  • ✓ Manage blog categories/tags
  • ✓ Upload blog images
  • ✓ Publish/unpublish posts
  • ✓ Schedule posts (if available)
  • ✗ Edit website pages
  • ✗ Change blog design/layout
  • ✗ Access site settings

Use cases:

  • Content writers
  • Bloggers
  • Marketing team (content)
  • Guest contributors

Best for: Content creators focused on blog management.

Workflow: Create and publish directly or submit for review (owner can set).

Store Manager (E-commerce)

E-commerce store management:

Permissions:

  • ✓ Add/edit products
  • ✓ Manage product categories
  • ✓ Update pricing and inventory
  • ✓ Upload product images
  • ✓ Manage product descriptions
  • ✓ View orders
  • ✓ Process orders and shipments
  • ✗ Change payment settings
  • ✗ Modify shipping settings
  • ✗ Access payout information
  • ✗ Edit non-store pages

Use cases:

  • Store manager
  • Inventory coordinator
  • Product manager
  • Customer service

Best for: E-commerce operations without full site access.

Availability: Sites with Strikingly store enabled.

Permission Matrix

Detailed Permission Comparison

Feature/Action Owner Full Access Limited Access Blog Editor Store Manager
Content
Edit all pages ✓ ✓ Assigned only ✗ ✗
Add/remove pages ✓ ✓ ✗ ✗ ✗
Edit navigation ✓ ✓ ✗ ✗ ✗
Upload images ✓ ✓ Limited Blog only Products only
Blog
Create posts ✓ ✓ ✗ ✓ ✗
Edit posts ✓ ✓ ✗ ✓ ✗
Delete posts ✓ ✓ ✗ ✓ ✗
Blog settings ✓ Limited ✗ ✗ ✗
E-commerce
Add products ✓ ✓ ✗ ✗ ✓
Manage orders ✓ ✓ ✗ ✗ ✓
Payment settings ✓ ✗ ✗ ✗ ✗
Shipping settings ✓ ✗ ✗ ✗ ✗
Design & Settings
Change design ✓ ✓ ✗ ✗ ✗
SEO settings ✓ Basic ✗ ✗ ✗
Site settings ✓ ✗ ✗ ✗ ✗
Domain settings ✓ ✗ ✗ ✗ ✗
Administration
Add team members ✓ ✗ ✗ ✗ ✗
Billing access ✓ ✗ ✗ ✗ ✗
Transfer site ✓ ✗ ✗ ✗ ✗
Analytics ✓ Limited ✗ ✗ Limited

Note: All four roles (Administrator, Editor, Store Manager, Blogger) are available on all Strikingly plans including Free. Each site supports up to 10 team members.

Permission Scenarios

Small Business (2-3 people)

Setup:

Owner: Business owner
├── Full Access: Marketing manager
└── Blog Editor: Content writer

Rationale:

  • Owner maintains control
  • Marketing manager handles site updates
  • Writer focuses on blog content

Marketing Agency

Setup:

Owner: Client
├── Full Access: Agency lead
├── Limited Access: Copywriter (Services + About pages)
└── Blog Editor: Content team

Rationale:

  • Client retains ownership
  • Agency manages site development
  • Limited access for specific tasks
  • Clear responsibility boundaries

E-commerce Store

Setup:

Owner: Store owner
├── Full Access: Store manager
├── Store Manager: Inventory coordinator
└── Store Manager: Customer service

Rationale:

  • Owner oversees business
  • Manager handles site operations
  • Inventory team manages products
  • Support processes orders

Content Team (Blog/Magazine)

Setup:

Owner: Publisher/Editor-in-chief
├── Full Access: Managing editor
├── Blog Editor: Writer 1
├── Blog Editor: Writer 2
└── Blog Editor: Writer 3

Rationale:

  • Publisher controls platform
  • Managing editor oversees site
  • Writers create content
  • Editorial workflow maintained

Plan-Based Limitations

Free Plan

Team member access:

  • ✗ No team member support
  • Owner only
  • No collaboration

Upgrade to: Pro or higher

Limited Plan

Team member access:

  • ✗ No team collaboration
  • Owner only

Upgrade to: Pro plan minimum

Pro Plan

Team member capabilities:

  • ✓ Up to 2 team members
  • ✓ Basic permission types
  • ✓ Invitation system
  • Limited section control

VIP Plan

Enhanced capabilities:

  • ✓ Up to 10 team members
  • ✓ Advanced permissions
  • ✓ Section-specific access
  • ✓ Better collaboration tools
  • ✓ Activity tracking

Enterprise Plan

Maximum capabilities:

  • ✓ Custom team size
  • ✓ Advanced permission control
  • ✓ Priority support
  • ✓ Custom workflows

Best Practices

Assigning Access Levels

Principle of least privilege:

  • ✓ Start with minimum access
  • ✓ Grant only what's needed
  • ✓ Blog editor before full access
  • ✓ Section-specific before full site
  • ✗ Don't default to full access

Decision guide:

  1. What does user need to edit? → Specific sections or all?
  2. Need to add pages? → Full access
  3. Only blog? → Blog editor
  4. Only products? → Store manager
  5. Temporary? → Set review date

Security Practices

Account security:

  • ✓ Strong passwords
  • ✓ Don't share owner credentials
  • ✓ Individual team member accounts
  • ✓ Regular access reviews
  • ✓ Remove inactive users
  • ✗ Don't share logins
  • ✗ Don't use generic accounts

Access management:

  • Document who has access
  • Quarterly access reviews
  • Remove departing members immediately
  • Monitor activity
  • Set expiration dates for temporary access

Communication

When adding members:

  • Explain access level
  • Set clear expectations
  • Provide training
  • Document responsibilities
  • Share content guidelines

When removing:

  • Inform in advance (if appropriate)
  • Thank for contributions
  • Explain timeline
  • Answer questions

Limitations and Workarounds

No Granular Field Permissions

Limitation: Cannot set permissions per field or content type.

Example: Can't grant "edit text but not images" or "view but not publish."

Workarounds:

  • Use section-based access control
  • Editorial guidelines
  • Regular content reviews
  • Trust-based collaboration

No Approval Workflow

Limitation: No built-in content approval process.

Workarounds:

  • Manual review process
  • Communication before publishing
  • Regular content audits
  • External approval tools
  • Team protocols

No Custom Roles

Limitation: Cannot create custom permission sets beyond defaults.

Workarounds:

  • Choose closest role
  • Document responsibilities
  • Training on limitations
  • Clear communication

Troubleshooting

Team Member Cannot Edit Assigned Page

Check:

  1. Invitation accepted
  2. Correct access level
  3. Page included in their sections
  4. Logged in correctly
  5. Browser cache cleared

Solutions:

  • Verify section assignment
  • Log out and back in
  • Clear browser cache
  • Check access level

Team Member Has Too Much Access

Fix:

  1. Settings → Team
  2. Edit member
  3. Change to more restrictive level
  4. Save

Immediate effect: Next login

Need More Control Than Provided

Options:

  1. Upgrade plan for advanced features
  2. Use section access for page-level control
  3. Communication and training
  4. Regular reviews

Comparing to Other Platforms

Translating Roles

From WordPress:

  • Administrator → Owner
  • Editor → Full Access
  • Author → Blog Editor
  • Contributor → Blog Editor (limited)

From Shopify:

  • Owner → Owner
  • Staff (full) → Full Access
  • Staff (orders) → Store Manager
  • Staff (blog) → Blog Editor

Next Steps

Quick Reference

Permission Decision Tree

What does user need?

Blog only?
├─ YES → Blog Editor
└─ NO → Continue

Specific pages only?
├─ YES → Limited Access
└─ NO → Continue

Products/orders only?
├─ YES → Store Manager
└─ NO → Continue

Full site editing?
├─ YES → Full Access
└─ NO → Re-evaluate

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

Access Level Quick Guide

Need Recommended Role
Billing access Owner only
Full site editing Full Access
Specific pages Limited Access
Blog management Blog Editor
Product management Store Manager
View only Not supported*

*For view-only, share preview link instead.

Back to top