SITE123 is a hosted website builder with a simplified, account-centric access model. Unlike enterprise CMSes with granular permission systems, SITE123 operates primarily as a single-owner platform. The account holder has full control, and collaboration features are limited compared to platforms like WordPress or Shopware. Multi-user management is available on paid plans but with a constrained role system.
Permission model
SITE123's access model is straightforward:
- Account Owner -- the primary account holder with full control over all sites, billing, domain settings, and content. There is exactly one owner per account.
- Collaborators (paid plans) -- invited users who can edit site content. Collaborators are invited per site and can modify pages, images, and text but cannot change account-level settings like billing, domain, or plan.
- No granular permissions -- there is no per-page, per-section, or per-feature permission system. A collaborator either has edit access to the entire site or no access at all.
- No API access model -- SITE123 does not expose a public API, so there are no API keys, tokens, or programmatic access controls.
The model is designed for small businesses and personal sites where one person (or a small team) manages the website without needing complex role hierarchies.
Available roles
| Role | Access | Limitations |
|---|---|---|
| Account Owner | Full control: billing, domains, site content, design, settings, user management | One per account, cannot be transferred without support |
| Collaborator | Edit site content: pages, text, images, forms | No billing access, no domain management, no design/template changes, no analytics settings |
| Store Manager (e-commerce plans) | Manage orders, products, and inventory | Limited to e-commerce sections, no site design or account settings |
There is no Administrator role between Owner and Collaborator. The Owner must handle all configuration, theme, and integration tasks personally.
Admin UI paths
| Task | Location |
|---|---|
| Manage collaborators | Dashboard > Settings > Manage Collaborators |
| Invite a collaborator | Settings > Manage Collaborators > Add Collaborator (email invite) |
| Remove a collaborator | Settings > Manage Collaborators > [User] > Remove |
| Account settings | Dashboard > Account Settings |
| Billing management | Dashboard > My Sites > Upgrade/Manage Plan |
| Domain settings | Dashboard > Settings > Domains |
| E-commerce user management | Dashboard > Store > Staff (if applicable) |
API access management
SITE123 does not provide a public API. Integration options are limited to:
- Embed codes -- Owner can add custom HTML/JavaScript via the "Custom Code" feature in site settings. This is the primary method for adding analytics scripts, chat widgets, and third-party integrations.
- Built-in integrations -- SITE123 offers pre-built integrations (Google Analytics, Facebook Pixel, Google Tag Manager) configured through the dashboard. These are Owner-only settings.
- Webhooks -- not available. Form submissions can be routed to email but not to custom endpoints.
- Export -- site content cannot be exported via API. Manual backup is limited to what the dashboard provides.
Since there is no API, there are no API keys to manage, rotate, or revoke.
Analytics-specific permissions
SITE123's analytics capabilities are Owner-only:
- Google Analytics integration -- configured at Dashboard > Settings > Integrations > Google Analytics. Enter the Measurement ID (G-XXXXXXX). Only the Account Owner can configure this. Collaborators cannot see or modify analytics settings.
- Google Tag Manager -- add the GTM container ID at Dashboard > Settings > Integrations > Google Tag Manager. Owner-only configuration.
- Facebook Pixel -- configured at Dashboard > Settings > Integrations > Facebook Pixel. Owner-only.
- Built-in statistics -- SITE123 shows basic visitor counts and page views in the dashboard. Available to the Account Owner only. Collaborators do not see these statistics.
- Custom Code for tracking -- the Owner can inject custom tracking scripts via Settings > Custom Code > Head/Body injection. This is the fallback for any analytics tool not supported by built-in integrations:
<!-- SITE123: Settings > Custom Code > Head injection -->
<!-- Example: GA4 + GTM dual deployment -->
<script async src="https://www.googletagmanager.com/gtag/js?id=G-XXXXXXXX"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'G-XXXXXXXX');
</script>
- E-commerce analytics -- order and revenue reports are available in the Store section on e-commerce plans. Access follows the Store Manager role if assigned.
For teams that need analytics access without full site editing capability, the workaround is to:
- Share read-only access to the external analytics platform (e.g., add team members as Viewers in Google Analytics)
- Keep the SITE123 account credentials with the Owner only
- Use GA/GTM's own user management for analytics collaboration rather than trying to manage it through SITE123
Sub-pages
- Roles and Permissions -- detailed collaborator capabilities, e-commerce role access, and Owner vs. Collaborator feature matrix
- Adding and Removing Users -- inviting collaborators, managing access, and transferring site ownership