Work together without everyone being allowed everything
Adding your colleagues costs nothing extra, so you don't have to choose who gets in. What someone may do, you set with their role.
One login the whole team shares
In a lot of small companies a CRM charges per user. The result is predictable: one account gets made, and it gets shared. That throws away the one thing a shared system is for, because you can no longer see who did what, and nobody feels responsible for a deal.
The other way round is just as awkward. Give everyone full access and the intern updating the list can delete an entire company file as well. Not out of malice, but because delete sits next to save.
Four roles, and the line is drawn in the database
Every colleague gets their own login and one role in the organisation. That role decides what they can do: everything, nearly everything, the day-to-day work, or watch only.
What matters more than the roles is where they are enforced. Not by hiding a button, but in the database: if a read-only account asks for a change, the database refuses the row, including when the request comes from outside the screens. A check somebody forgot to write in the code cannot get round that line.
On top of that, everything anyone changes is recorded: who, what, when, and the attempts that were refused as well. That is not keeping an eye on your staff but the answer to “who changed this”, the question you ask at the moment it suits you least.
Your membership of an organisation also doesn't hang off your login but sits separately from it. So you can belong to more than one organisation with the same account, and the data of those organisations never meets.
What you actually set
Invite by email address
You invite someone at their address, with the role in the invitation. They first see which organisation is inviting them and in what role, and accept after that. A button that joins you to an unknown organisation without explaining is not an invitation.
Owner and manager
May do everything in the CRM, including deleting data for good. Managing the team is the owner's: whoever can change roles can make themselves owner and shut everyone else out. Deleting asks for confirmation with the name in the question first, so it is never a misclick.
User
The day-to-day work: creating and updating companies, contacts, deals, tasks and notes. Not managing the team, not deleting for good.
Read-only
Watch and change nothing. For a bookkeeper, an adviser, or someone who has just started, and the database simply won't let them write.
Read on
Security
Where your data sits, who can reach it, and how we enforce that line.
Read moreImport and export
Your data stays yours, including when you leave again.
Read morePricing
One price for your whole company, not per user. That's why nobody has to see what's going on through a shared account.
Read more
Invite one colleague
Put a company in, give your colleague the role that suits them, and see whether you can both find each other's work.