Strikingly is a hosted website builder designed for single-page websites and simple multi-page sites. Its user management model is account-owner-centric with limited collaboration features. The platform prioritizes simplicity over granular access control -- there are no role hierarchies, no ACLs, and no per-section permissions. For teams, Strikingly offers basic collaborator invitations on paid plans, but the permission model remains binary: full edit access or no access.
Permission model
Strikingly's access control is minimal:
- Account Owner -- the account creator with full control over all sites, billing, domains, integrations, and settings. One owner per account.
- Collaborators (Pro plans and above) -- invited users who can edit site content and design. Collaborators work within the same editor as the owner with nearly identical editing capabilities, but cannot manage billing, domains, or account settings.
- Team Sites (Strikingly for Teams) -- enterprise offering with a team dashboard. Team admins can manage multiple sites and assign editors, but the permission model remains simple: team admin or site editor.
- No per-page permissions -- all collaborators can edit all pages and sections on a site. There is no way to restrict a collaborator to specific pages or content blocks.
Available roles
| Role | Access scope | Restrictions |
|---|---|---|
| Account Owner | Full control over all sites and account | None -- unrestricted |
| Collaborator | Edit site content, design, pages, blog posts | No billing, no domain management, no account settings, no analytics configuration |
| Team Admin (Teams plan) | Manage team sites, assign editors, view team dashboard | Billing may still be owner-only depending on plan |
| Team Editor (Teams plan) | Edit assigned sites within the team | No team management, no account settings |
Admin UI paths
| Task | Location |
|---|---|
| Manage collaborators | Site Editor > Settings > Manage Collaborators |
| Invite a collaborator | Settings > Manage Collaborators > Add (email invite) |
| Remove a collaborator | Settings > Manage Collaborators > [User] > Remove |
| Account settings | Dashboard > Account (top-right menu) |
| Billing management | Dashboard > Account > Plan & Billing |
| Domain settings | Site Editor > Settings > Domains |
| Team management (Teams) | Team Dashboard > Members |
API access management
Strikingly does not provide a public API for site management. Integration options:
- App Store integrations -- Strikingly's App Store offers pre-built integrations (Google Analytics, Facebook Pixel, Mailchimp, etc.) configured through the editor. These are toggle-based and managed by the Owner.
- Custom code injection -- paid plans allow custom HTML/CSS/JavaScript in the site header and footer via Settings > Custom Code. Only the Owner and Collaborators can access this.
- E-commerce API -- Strikingly's Simple Store has limited integration capabilities. Order data can be exported but there is no REST API for programmatic access.
- No webhooks -- there is no webhook system for real-time event notifications.
- No OAuth/SSO -- authentication is Strikingly account credentials only (email + password or social login).
Analytics-specific permissions
Strikingly's built-in analytics and integration management:
- Built-in Analytics -- Strikingly shows basic visitor statistics (page views, unique visitors, traffic sources) in the site dashboard. This is visible to the Account Owner. Collaborators can also view the analytics dashboard in the editor.
- Google Analytics -- configured at Site Editor > Settings > Services > Google Analytics. Enter the Measurement ID. Only the Account Owner can enable and configure this integration. Collaborators may not see the Services settings panel.
- Facebook Pixel -- configured at Settings > Services > Facebook. Owner-only configuration.
- Google Tag Manager -- can be added via custom header code injection (Settings > Custom Code > Header Code). Requires the Owner or a Collaborator with custom code access:
<!-- Add to Strikingly: Settings > Custom Code > Header Code -->
<!-- Google Tag Manager -->
<script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);
})(window,document,'script','dataLayer','GTM-XXXXXXX');</script>
- Conversion tracking -- e-commerce conversion tracking for Simple Store is configured in the Analytics or Services settings. Owner-only.
- Blog analytics -- blog post view counts are shown in the blog management section. Accessible to anyone with editor access.
For analytics teams that need data access without site editing rights:
- Grant access through the external analytics platform (e.g., add as Google Analytics viewers)
- Share Strikingly's built-in analytics screenshots or exports manually
- Do not share Strikingly account credentials -- there is no read-only role
The primary limitation is that Strikingly's built-in analytics cannot be shared without granting edit access. Use the external analytics platform's own user management for collaborative analytics workflows.
Sub-pages
- Roles and Permissions -- collaborator capabilities, team plan roles, and owner vs. collaborator feature comparison
- Adding and Removing Users -- inviting collaborators, managing team members, and revoking access