Invite a Team Member
How to add another person to your Commerce Kitty account, give them the right level of access, and remove them later if you need to.
Before you start
Decide what the new user should be able to do. The two common patterns are:
- Operations user: can view and edit products, orders, and customers but cannot change billing or invite other users
- Administrator: can do everything except change ownership of the account
Both are configured through user groups, which bundle a set of permissions together. If a suitable group does not exist yet, create one first.
Step 1. Create a user group (optional)
Skip this step if you already have a user group with the right permissions, or if you are inviting an administrator.
Open Configuration → User Groups and click New User Group. Give it a clear name like "Operations" or "Read Only", then select the permissions you want this group to have. Save the group.
For the full list of permissions and how groups work, see User Groups.
Step 2. Add the user
Open Configuration → Users and click New User. Fill in:
- Email: the address they will use to log in
- First Name and Last Name: for activity logs and dropdowns
- User Group: the group you created in Step 1, or an existing one
- Enabled: on, so they can log in
Save the user. Commerce Kitty creates the account.
The new user will need to set their own password using the password reset flow on the login page. Send them the login URL and tell them to click "Forgot password" with their email.
Step 3. Verify their access
Ask the new user to log in and confirm they can see the things they should and cannot see the things they should not. If something looks wrong, edit their user group to adjust permissions and have them log out and back in.
Removing a user
To remove someone, open Configuration → Users, find their record, and either:
- Disable them by toggling Enabled off. They cannot log in but their record stays in place along with any historical activity.
- Delete them entirely. Use this when someone leaves and you have no reason to keep the record.
Disabling is the safer option for most departures. It preserves audit trails and lets you re-enable access later without recreating the user.