Member Management

Organization members are the people who have access to an org. The org member list controls who can see the org dashboard, browse sites, and be invited to specific sites. It's separate from site membership — joining an org doesn't automatically grant access to every site inside it.

This page covers org-level roles, the invite flow, how org and site membership interact, and how to remove or disable members.


Org-Level Roles

There are three roles at the org level:

Owner — Full control over the org, including billing. Every org has exactly one owner (the person who created it) by default, though ownership can be transferred. The owner is the only role that can manage the subscription, change the org's plan, and add/remove sites that exceed the plan limit.

Admin — Can invite and manage members, manage sites, and access every site in the org. Cannot modify billing or transfer ownership. Most teams operate with one or two admins handling day-to-day org management.

Member — Can see the org dashboard and access sites they've been explicitly granted access to. Cannot invite other members, manage sites, or see billing. This is the default role for new invites.

The three roles map cleanly to "billing", "ops", and "user" — a small team typically has one owner, one or two admins, and everyone else as members.


The Invite Flow

To add someone to the org:

  1. From the Members screen, click Invite Member.
  2. Enter their email and pick an org-level role (member, admin, owner).
  3. Optionally, immediately grant them access to specific sites with site-level roles.
  4. Send the invite.

The invitee receives an email with a link to accept. Until they accept, the invite shows up as Invited in the members list. After accepting, they appear as Active.

You can invite people who already have a SleekCMS account (they accept the invite when signed in) or new users (they create an account when accepting). Either path lands them in the org with the role you assigned.


How Org and Site Membership Interact

Membership is two-layered. An org member becomes a site member when they're explicitly added to a site:

  • Org members without site membership see the org dashboard but cannot enter any site's content or builder.
  • Org members with site membership see the sites they've been granted access to. The site-level role (admin or editor) determines what they can do within that site.

Org admins automatically have access to every site in the org with admin-level permissions. They don't need to be individually added to each site.

Org owners have the same site access as org admins, plus billing access.

The split is intentional — it lets you have org members who don't have access to any site yet (useful for staged onboarding, contractors waiting on a specific project, billing-only owners) and lets agencies grant clients access to a single site without exposing the rest of the org.

Site MembersSites


Changing a Member's Role

From the Members screen, the action menu next to each member offers role changes:

  • Promote to admin / demote to member — Adjust org-level role.
  • Transfer ownership — Owner-only action that moves the owner role to another member. The previous owner becomes an admin. Useful when the original creator leaves the team.

Changing the role takes effect immediately. The member sees the updated permissions on their next page load.


Removing Members

To remove someone from the org:

  1. Find them in the Members list.
  2. Click the action menu and choose Remove.
  3. Confirm.

Removal:

  • Revokes their access to the org and every site within it.
  • Cancels any pending invites for that user in this org.
  • Leaves their account intact (they can still log in to SleekCMS, just not to this org).

If you'd rather temporarily disable rather than permanently remove (e.g., a contractor between engagements), set their role to a no-access state or simply remove them; you can re-invite later with the same email.


Pending and Disabled States

Members appear in one of three states:

State Meaning
Active Accepted the invite, has access
Invited Sent an invite, hasn't accepted yet
Disabled Membership exists but is suspended — no access

Invited members keep their pending state until they accept the email link. If they don't accept within a reasonable time, you can resend or revoke the invite.

Disabled members are a soft pause — useful for offboarding flows where you want to keep the membership record but block access. Re-enabling restores their previous permissions.


Audit and Activity

The Members screen shows when each member was added and their current state. For deeper audit needs (who did what, when), use the activity log inside each site's settings — org-level activity history is more limited.


What's Next