Adding users, managing their licenses and email addresses, removing them, and resolving the invitation problems that come up most.
On this page:
- Planning before you start
- Adding a user
- Invitation problems
- Licenses
- Deleting a user
- Changing an email address
- Reviewing a user’s settings
- Why users appear as contacts
Planning before you start
Before adding users and importing data, work out where your data currently lives and how your team will be structured, since both decisions affect permissions setup.
Adding a user
Administrators add users from System Settings > Users. Once a user is activated, set up their security access permissions as a separate step.
Invitation problems
If an invitation expired or never arrived, send a new one from System Settings > Users.
If a user receives no notifications, password resets, or invitations at all, the messages are most likely being blocked before delivery rather than not being sent.
Licenses
Removing a user’s license disables their access without requiring you to reassign what they were responsible for, which makes it the right tool for someone temporarily leaving rather than departing. Every user must hold a license to sign in.
Deleting a user
Administrators can delete a user outright, or delete and replace them with a new user in one step, which carries over what the departing user was responsible for.
In a plain delete, before the user is removed you are prompted to reassign the records they own or are responsible for to other active users. All standard and custom objects with records the user owns or is responsible for appear as reassignment options. No data is lost. The deleted user still stays associated with records such as completed tasks, emails, or closed projects, appears in the Deleted Users list under System Settings > User List, and shows “(Deleted)” after their name in lists, reports, dashboards, and Details and Related tabs.
If a record is not reassigned during deletion, it keeps the deleted user as its owner. Because a deleted user no longer appears in the filter-by-owner picklist, these records can be harder to locate by owner afterward. This mainly affects records with private visibility: public records remain findable by any user through their field values, and administrators can still surface private ones by building a filter that excludes all current users.
If you have a paid subscription and won’t be adding a new user to replace the deleted one, reduce the number of users on your account to lower your monthly subscription cost.
Changing an email address
Insightly uses the email address as the sign-in ID, so a change of address is a change of user ID. An administrator makes this change. The process differs by account type: for a multiple-user account the administrator uses Change User Email Address on the user’s row. An account owner’s user ID cannot be changed directly, and account ownership must be transferred to another user first. Google Workspace users sign in with their Gmail address, which Insightly cannot change, so those changes go through the Google Workspace administrator or by reassigning the license to a new user.
Reviewing a user’s settings
How you check a user’s permissions depends on whether the account uses Simple or Advanced Permissions.
Why users appear as contacts
Adding a user creates an Insightly contact for them, but system users have special contact records that behave differently from ordinary contacts.