Account Security Features
Cin7 Core offers several features to maintain and enhance the security of your account.
Periodic password change
Users in your organisation can be forced to change their passwords at regular intervals. Set the password change frequency in General Settings → Security. Password change frequency can be set to Never (default), every month, every 3 months, every 6 months, every year.
The date of the next password change is calculated from when the password was first set, not from when the password change frequency feature was activated.
Note: Passwords in Cin7 Core must follow these rules to be valid:
Use 8 or more characters
Must include upper and lower case characters (e.g. Aa)
Must include a number (1234)
Must include a symbol ($%&?)
Must not be the same as the last 10 previous passwords.
User Profile page
The User Profile page allows you to manage your account settings – set up a personal name for the Cin7 Core account, set up 2-step authentication and view recent login attempts. It can be accessed from your Account menu.
The User Login History grid shows the 10 most recent login actions; this should be regularly checked for any unusual logins or suspicious account activity.
Account locks for multiple incorrect login attempts
Cin7 Core locks out user accounts after five (5) failed incorrect password attempts. If you forget your password, click the Forgot your password link on the Cin7 Core Login page to get a new one. If you still fail to log on to Cin7 Core after changing your password, contact the Cin7 Support Team.
Two-factor authentication
Two-factor authentication (2FA) adds an extra layer of security to your user account or to an organisation account, in case your password is stolen. Cin7 Core makes 2FA mandatory on all accounts. If you have not yet enabled two-factor authentication for your account, you will be prompted to do so when you log in. See our two-factor authentication article for more information.
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB