Manage users
Overview
You must create a user for each person using your Cin7 Omni account.
For example, if you run a store with three salespeople, you’ll need four users—one for yourself and one for each employee.
Create as many users as you need up to your plan's user limit. Edit users as their responsibilities change, and delete them when they leave. Each user has private credentials so only they can log in.
To manage users, you must be an administrator.
Create a user
Before creating a new user, ensure you’ve created a role to assign to the user, or be prepared to create a custom role.
To create a new user:
From the user menu in the navigation, open Users.
Click Create User. The User Details page will open.
Fill in the user’s settings on the User Particulars, General Permissions, and (if available) Module Permissions tabs. Find more about user settings below.
Click Save.
The person you created this user for will receive an email with a link. They must click that link to create a password. Once they’ve created a password, they can log in to Cin7 Omni for the first time. They’ll be prompted to set up two-factor authentication (2FA) during their first login.
I didn’t receive my new user setup email
If you’re a new user but haven’t received your setup email, submit a ticket with Cin7 Omni Support and ask for it to be resent.
Edit a user
You can edit users to assign them a new role or update their details:
From the user menu in the navigation, open Users.
Select the user to edit.
Edit their user settings. Find more about user settings below.
Click Save.
Remove a user
Removing users permanently stops them from logging in to your Cin7 Omni account. Their data is saved for reporting and auditing purposes.
To remove a user:
From the user menu in the navigation, open Users.
Select the user to remove.
On the User Particulars tab, set Status to Disabled.
Click Save.
User settings
User Particulars
Enter the user’s First Name and Last Name.
Enter the user’s Email Address. They’ll use this to finish creating their user and to log in to Cin7 Omni.
Enter the user’s Job Title.
Enter the user’s Phone and Mobile.
Enter any Notes about the user.
For License Type, select Standard to give the user access to the Omni backend. Else, to give the user access to the POS only, select POS .
For Allowed IP Addresses, add the IP addresses (separated by commas) from which the user can access Omni. Else, to allow the user to access Omni from any IP address, leave this blank.
For Staff POS Access Number, enter a unique number the user can use to access the POS. Else, if this is left blank, they must use their email address.
For Role, select the user’s role. Else, select Custom and define custom permissions for the user on the Module Permissions tab.
General Permissions
For Default Branch, select the branch where this user works. The transactions they create will be assigned to this branch by default. Else, if left blank, the user’s default branch will be the last branch they assigned a transaction to.
For Branch Access, select Full Access to give the user permission to view stock and edit transactions for all branches. Else, select Limited Access and then choose the branches where they can view stock and edit transactions.
For Price Tiers, select Full Access to give the user permission to use all price tiers. Else, select Limited Access and then choose the price tiers they can use.
Module Permissions
If you’ve set the user’s Role to Custom, the Module Permissions tab will be shown. Here you define the user’s custom role.
You’ll see a list of each area of Cin7 Omni. For each area, define the user’s permissions:
No Access: The user can’t view or edit in this area.
Standard: The user can view and edit in this area, except they can’t view cost of goods sold (COGS) or edit locked transactions.
Manager:The user can view and edit in this area, except they can’t edit locked transactions.
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB