Skip to main content
All CollectionsAccount ManagementSecurity
Best Practices: Account Security
Best Practices: Account Security

How to keep your account private and secure.

Ann Tindog avatar
Written by Ann Tindog
Updated over a week ago

Implementing strong security practices can safeguard your account from unauthorized access and potential breaches.

Creating a strong password

A strong password is your first line of defense against unauthorized access. Here’s how to create one:

  • Length and complexity: Use at least 12 characters, including a mix of uppercase and lowercase letters, numbers, and special characters.

  • Avoid common phrases: Avoid using easily guessable information like "password123," "qwerty," or your name and birthdate.

  • Use a passphrase: Consider using a passphrase, a series of random words that are easy for you to remember but hard for others to guess. For example, "RedPine#Coffee!Boat."

  • Unique passwords: Use a different password for each of your accounts to prevent a breach in one account from compromising others.

Enabling two-factor authentication (2FA)

Two-factor authentication adds an extra layer of security to your account, and is recommended by Casefleet as a best practice. 2FA requires both your password and a second form of verification to access your account.

Click here for instructions on enabling 2FA for your user profile.

Saving backup codes

When you set up 2FA, most services provide backup codes. It is highly recommended to save a copy of these codes, in the event you lose access to your primary 2FA method.

To save a copy, go to User Profile > Two Factor Authentication > Regenerate Backup Codes.

Adding a phone backup

A phone backup can be crucial if your primary 2FA device is lost or unavailable, and will allow you to log in using a one-time passcode sent via SMS:

Keeping login credentials private

Sharing login credentials can pose a significant security risk and limits your ability to leverage Casefleet's collaboration tools, such as

  1. The ability for both people to work within the program simultaneously, without interrupting each other's workflows.

  2. The ability to better manage user privileges, such as restricting administrative access.

  3. The ability to assign and track tasks on the same case for different team members.

Ensure each user has their own login credentials. This practice helps maintain security and accountability. A shared login poses a significant security risk to your account and does not let you use two-factor authentication, which is strongly advised as a best practice.

Did this answer your question?