Users
Users are the individual people who can log in to your Commerce Kitty account. Each teammate, contractor, and virtual assistant who needs access should have their own user record.
How users work
Every login is tied to one user. Commerce Kitty does not support shared logins, and you should not hand out the same credentials to multiple people. Giving each person their own user gives you an audit trail and lets you revoke access for one person without disrupting the rest of the team.
The first user on an account is the account owner. The account owner always has full permissions and cannot be locked out. Every additional user is a regular user whose permissions are controlled by the user group they belong to.
The account owner bypasses user group permission checks entirely. Everyone else is subject to whatever their group allows.
Inviting a user
Go to Configuration, then Users, and click add. Fill in the email address and name, pick a user group, and save. Commerce Kitty sends an invite email with a link to set a password.
Disabling a user
When someone leaves the team, disable their user instead of deleting it. Disabled users cannot log in but their historical actions remain in your audit log. You can re-enable them later if they come back.
User fields
The login identifier and where invite and password reset emails are sent. Must be unique across your account.
First Name
The user's given name. Shown in the admin UI next to actions that person has taken.
Last Name
The user's family name.
User Group
The group this user belongs to. The group's permissions determine what the user can see and do. See User Groups for details on how permissions are assigned.
Roles
Additional role flags layered on top of the user group. Most installs can leave these alone and rely on groups for all permission control. Use roles for special cases like a read-only auditor who needs to bypass a specific group rule.
Enabled
Whether the user can log in. Turn this off to suspend access immediately.
Users can also generate API keys. Those keys inherit the user's permissions. Disabling a user also disables their API keys.