An account user is someone you add to help run your Kajabi account, such as a team member, a contractor, or a virtual assistant. Custom permissions let you give that person access to exactly the areas they need, instead of settling for whichever built-in role comes closest.

You start from a role, then switch individual permissions on or off for that one person. The change applies only to them, so customizing one Assistant does not affect any other Assistant on your account.

This page covers who can customize permissions, how customizing affects your plan's extra users, what each permission group controls, and how to put someone back on their role's defaults.

To change another account user's permissions, you must be the Account Owner or a Co-owner. Administrators can open a user's profile and see the permission groups, but the checkboxes are read-only for them.

Two limits always apply:

Every account user has a role. The role you pick sets their starting permissions:

Pick a role and its default permissions are checked automatically, and you can still adjust any box individually. The moment you change one permission, the Role dropdown switches to Custom, and the user's row on the Users list reads Custom (Administrator), naming whichever role their permissions started from.

The underlying role does not change. Custom is a label describing that this person's access has been adjusted, not a sixth role you can assign directly.

Customizing someone's permissions can change how they count toward your plan's user limit. If your plan limits extra users, Co-owner, Administrator, and any customized user each count as one.

What this means in practice:

When a limit applies, the Role & Permissions section shows how many extra users you have used, along with Buy an extra user and Upgrade plan links when your plan supports them.

Permissions are organized into seven groups that follow the Kajabi navigation, so the question to ask is where in Kajabi someone does the work, not which team owns it. Each permission has a short description under it explaining what it covers.

Manage comments and Product announcements sit underneath Courses, but they are set independently. Turning off Courses does not turn them off.

Single use coupon codes sits underneath Offers & coupons. Turning off Offers & coupons turns it off, too.

Two states stop a permission from being edited, and they read differently:

A permission left in the can't be changed yet state appears neither on nor off, because no decision has been recorded for it. It does not mean access has been denied.

Community access is handled separately from the permission groups, in the Community access section of the user's profile. Select a community to give the user access to it, then choose what they can do inside it:

Set these per community, so someone can moderate one community without touching another.

If you want to undo your changes and put someone back on the standard permissions for their role, use the reset link rather than unticking boxes by hand:

Their Role dropdown stops showing Custom, and the extra user their customization was using is released.

Each account user's profile has two tabs: Settings, where you set their role and permissions, and Activity.

The Activity tab shows a feed of what has happened to that user's account: when they were created, role changes, permission changes, site access changes, suspensions and unsuspensions, and password resets. Permission entries expand with View permissions to show what was Granted and what was Removed.

The Details card on the same tab shows Total sign ins, Last signed in, and whether MFA enabled is set to Yes or No. The Site Access card lists the sites the user can reach.

Every custom permission set starts from a role, which serves as the baseline being adjusted. This table shows what each role can reach before any changes are made. It is the same reference published in Account users.

No. Their role stays whatever was selected, and it continues to set the starting point for that person's permissions. The Role dropdown displays Custom to tell you their access has been adjusted, and the Users list shows the role the customization was built from, such as Custom (Administrator).

It depends on their role. If your plan limits extra users, customizing an Assistant, Support Specialist, or Payments Assistant uses one, because those roles do not normally use one. Customizing a Co-owner or Administrator does not, since they already use one. Resetting the user to their role defaults gives it back.

Either Kajabi has not finished adding it, in which case the row reads This permission can't be changed yet, or the feature is not part of your plan, in which case it reads Not included in your plan. Administrators also see every permission as read-only, because only the Account Owner and Co-owners can change them.

Yes. Saving signs the user out of Kajabi. Their new access applies the next time they sign in.

No. Permissions are set per person, so you customize each account user individually.

No. Deleting an account user is not available. You can suspend a user to remove their access instead. For the steps, see Account users.