TBA Foundation · Lesson 2 of 9 · about 1 hour
After this lesson you can #
- Sign in with your company code, user name and password.
- Set up and use two-factor verification, and know what “trust this device” does.
- Choose a strong password and keep your login to yourself.
- Explain what the license agreement is and who signs it.
Why it matters #
A company’s books are only as safe as its sign-ins. TBA asks for a second factor, ties every action to one named user, and records who agreed to what. Good habits here protect you and your company.
Read #
- Logging In and Two-Factor Authentication
- Users and Permissions (the parts on passwords and MFA)
- The License Agreement
The big picture #
You enter your company code, then your user name and password. Two-factor sign-in then asks for a one-time code from an authenticator app or from an email. Ticking Trust this device for 30 days skips the code on that browser, but never the password. A strong password has at least 10 characters with upper and lower case, a number and a special character. Never share a login: ask an administrator to create a user for the person, with only the permissions they need, so the audit log and your company’s license stay accurate.
A company administrator signs the license agreement for the company. They type their full name and position and confirm they can bind the company, and TBA keeps a permanent record of who signed, when and from where.
Try it #
- Sign in to a demo company and find where your two-factor method is set.
- Create a password that meets the rules and say aloud why each rule is there.
- Find the audit event log and look at your own sign-in.
Check yourself #
Explain to a colleague what “trust this device” does and does not skip. A practice quiz and certification exams are planned for a later release.
