Carrd User Management: Roles and Permissions | OpsBlu Docs

Carrd User Management: Roles and Permissions

Understand Carrd's single-owner account model, site sharing limitations, and how to manage analytics access on Carrd sites.

Carrd is a single-page website builder designed for simplicity. Unlike most platforms, Carrd has no multi-user or team collaboration features. Each Carrd account is owned by one person, and there is no way to invite collaborators, assign roles, or share admin access to individual sites.

Permission model overview

Carrd uses a single-owner model with no role-based access control. One email address owns the account, and that account controls all sites within it. There are no team workspaces, shared projects, or permission levels.

This means user management on Carrd is fundamentally about account-level credential management rather than role assignment.

Account types and capabilities

Carrd has two account tiers, but neither supports multiple users:

  • Free -- Up to 3 sites, limited features. Single owner. No custom domains, no custom code injection.
  • Pro ($19/year for Pro Standard, higher tiers for Plus and Max) -- Custom domains, forms, widgets, and custom code injection. Still single owner. Pro tiers differ in the number of sites allowed (10, 25, or 100).

There is no "team" or "agency" plan. If multiple people need to manage Carrd sites, each person must have their own Carrd account.

Workarounds for team access

Since Carrd has no native multi-user support, teams typically handle shared access through:

  • Shared credentials -- Multiple people log in with the same email/password. This is the only way to share full site editing access. Use a password manager with shared vaults to manage this securely.
  • Site transfers -- Carrd allows transferring a site to a different Carrd account. Go to the site's settings and use the transfer option. This moves ownership entirely rather than sharing it.
  • Export/import -- Pro users can export site data and import it into another account, though this creates a copy rather than maintaining a shared source of truth.

For agencies managing client sites, the typical pattern is to build the site under the agency's Pro account and transfer it to the client's account upon delivery.

Managing the account

Account settings are accessed by clicking the profile icon in the top-right of the Carrd dashboard:

  • Email and password -- Updated under account settings. Changing the email requires verification.
  • Connected accounts -- Carrd supports Google and Twitter/X login. These are linked under account settings.
  • Subscription management -- Pro plan billing is managed under the account settings page.
  • Delete account -- Permanently removes the account and all sites. There is no undo.

Analytics and tracking on Carrd

Carrd's approach to analytics is limited by its simplicity:

  • Built-in analytics -- Carrd does not provide any built-in traffic or analytics dashboard
  • Google Analytics -- Pro users can add a GA tracking ID under each site's settings (Site Settings > Meta Tags > Google Analytics ID). This only accepts a measurement ID (G-XXXXXXXX format).
  • Custom tracking scripts -- Pro users can inject custom HTML/CSS/JS via the site editor. Add an "Embed" element, select "Head" or "Footer" placement, and paste your tracking code:
<!-- Example: GTM container added via Carrd Embed element (Head placement) -->
<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>
  • Form tracking -- Carrd Pro forms can submit to external services (Mailchimp, Google Sheets, custom webhooks). Configure under the form element's settings.

Since there is only one user per account, there is no distinction between who can view analytics and who can install tracking. The account owner has full control over everything.

Security considerations

  • Carrd does not support two-factor authentication -- strong, unique passwords are essential
  • There is no session management or device visibility feature
  • No API is available -- all management is through the web UI only
  • No audit log or activity history exists
  • If sharing credentials, ensure the password is changed when a team member's access should be revoked

When Carrd is not enough

If your project requires multi-user editing, role-based permissions, or team collaboration, Carrd is not the right platform. Consider alternatives that support team features natively, such as Webflow (team workspaces), WordPress (roles and capabilities), or a headless CMS like Contentful (organization-level RBAC).

Sub-pages in this section

Nach oben