Less Annoying CRM User Management Guide

• Model type: role-based
• Description: Two-level model: Admin or Regular User. Admins have full account control; regular users have full CRM data access but no account-administration rights. No custom roles, no field-level permissions, no record-ownership restrictions.
• Custom roles: No
• Custom roles plan: Not documented
• Granularity: Coarse – binary Admin/User toggle only. No object-level, field-level, or pipeline-level permission controls.

1. Log in as an Admin.
2. Navigate to Settings → Users.
3. Click 'Add a new user'.
4. Enter the new user's name and email address.
5. Optionally toggle Admin status on or off.
6. Click 'Send invitation'.
7. The invited user receives an email and must click the link to set a password and activate their account.

Required fields: First name, Last name, Email address

Watch out for:

• Each added user immediately increases the monthly bill by $15; billing is prorated for mid-cycle additions.
• The invitation email can land in spam; users should be advised to check junk folders.
• There is no domain-based auto-provisioning; every user must be manually invited.
• No SSO or SCIM provisioning is available, so user creation cannot be automated via an identity provider.

• Can delete users: No
• Delete/deactivate behavior: Less Annoying CRM does not permanently delete user accounts. Admins can remove a user from the account, which revokes login access and stops billing for that seat. The removed user's data (contacts, notes, tasks) remains in the account and is reassigned or retained under the account's shared database.

1. Log in as an Admin.
2. Navigate to Settings → Users.
3. Locate the user to be removed.
4. Click 'Remove user' next to their name.
5. Confirm the removal in the dialog prompt.

Watch out for:

• Removing a user does not reassign their tasks or events to another user automatically; admins should manually reassign before removal.
• If the removed user was the sole Admin, another user must be promoted to Admin first.
• There is no 'deactivate' or 'suspend' state; removal is the only way to revoke access, and it is immediate.

• Where to check usage: Settings → Users (shows list of all active users and their last login date)
• How to identify unused seats: Admins can review the last login date displayed next to each user in Settings → Users to identify inactive accounts. No automated idle-user reporting is available.
• Billing notes: Billing is per active user per month. No annual commitment required. No free viewer or read-only seats. Adding a user mid-cycle is prorated; removing a user mid-cycle credit handling should be confirmed directly with Less Annoying CRM support, as the public docs do not specify proration on removal.

Every user added mid-cycle increases the monthly bill immediately at $15/user/month, prorated for the remainder of the cycle. There is no read-only or guest seat tier - every person who needs any access costs a full seat.

Removing a user is the only way to revoke access; there is no suspend or deactivate state. Admins should manually reassign open tasks and events before removal, since the platform does not do this automatically. Proration behavior on mid-cycle removals is not documented publicly and should be confirmed with support.

Reviewers consistently flag the absence of granular permissions as a real-world limitation. Teams that need to restrict which contacts or pipelines a user can see have no native path to do so - every app user sees the full shared contact database.

The lack of SSO and SCIM is a recurring friction point for growing teams, as every hire and departure requires manual admin action. The absence of a temporary suspend state is also noted: removal is all-or-nothing and immediate.

Common complaints:

• Users report that the lack of granular permissions (e.g., no way to restrict which contacts or pipelines a user can see) is a significant limitation for teams that need data segregation.
• No SSO or SCIM support means user provisioning and deprovisioning must be done entirely by hand, which is cited as a friction point for growing teams.
• Some reviewers note there is no read-only or free guest seat option, so every person who needs any access costs a full $15/month.
• The absence of a 'deactivate' state (only full removal) means there is no way to temporarily suspend a user without losing their seat assignment.
• Admins cannot restrict regular users from viewing all contacts in the shared database, which is a concern for accounts with sensitive segmented data.

Less Annoying CRM is a strong fit for small teams that want a simple, low-cost CRM with no tier complexity and no contracts. The flat $15/user/month rate covers every feature for every seat.

Teams that need data segregation, role granularity, or IdP-driven provisioning will hit hard limits quickly. If your IT or HR workflow depends on automated onboarding and offboarding, the fully manual user lifecycle will create ongoing overhead at scale.

Bottom line

Less Annoying CRM delivers on its name for small teams with straightforward needs: one price, one seat type, and a simple two-role model that covers every app in the account under a shared contact database.

The tradeoff is a fully manual user lifecycle - no SSO, no SCIM, no granular permissions, and no way to temporarily suspend a user.

Teams that can absorb that overhead will find it a capable, low-friction CRM; teams with compliance requirements, sensitive data segmentation needs, or automated provisioning workflows will outgrow its access model before they outgrow its features.