#Users
The table lists each user's name, email, Role, Status (Invite pending, Active, Inactive) and the dates invited and joined.
Invite user: First name *, Last name *, Email *, Role *. Because inviting someone grants access to your books, LedgersLab asks you to confirm with a 6-digit code sent to your own email before the invite goes out. The invitee receives a branded email; the link is valid for 24 hours (Chapter 1, section 1.4). From a row's ⋯ menu: Resend invite, Deactivate / Activate, and delete. You cannot deactivate or delete your own account, nor the company's owner. Deactivating or deleting someone removes their access to this company only — if their sign-in also belongs to other companies, they keep those. Seats are limited by your plan.
If the email you invite already has a LedgersLab sign-in (they use it for another company), the invitation adds this company to that sign-in; they accept it while signed in and keep their own password (Chapter 1, section 1.4). Their email can then only be changed by them, not from this page, because it is their sign-in for the other companies too.
#Roles
Roles decide what a user can see and do. The table shows Name, Description, Slug and Permissions (granted / total); built-in roles are tagged Predefined — their name and description are locked but their permissions can still be changed.
New role: Role name, Description, then Permissions grouped by Module and subject (Customers, Invoices, Bills, Bank accounts, Employees…) with abilities (View, Create, Edit, Delete, Post, Approve…). All on a subject grants or revokes everything in it; at least one permission is required. Custom roles need the Advanced plan; every plan has the predefined roles.
#Security
Two-factor authentication for your own account (Chapter 1, section 1.5).