Yes. Once a quarter, check who has a login, which role and scope each person has, who is an administrator and whether multi-factor authentication is on. It takes half an hour and catches access that nobody meant to keep. Pomio CRM enforces roles and scope on the server and logs important actions.
Yes. Keep one short, agreed list of labels, each with a one-line meaning, and let only an administrator add new ones. Do not use labels for things that already have a field, such as stage, owner or source. Pomio CRM has filterable labels next to teams, locations and live search.
Two, and rarely more than three. A small business CRM needs a named main administrator and one backup, both with multi-factor authentication. Everyone else works with a sales role and a narrow scope. Pomio CRM separates the organisation admin role from sales roles and logs important actions.
Yes — suspend a leaving colleague’s CRM account at the end of their last working day, after their open deals, tasks and contacts have been handed over. Suspending instead of deleting keeps history, ownership trails and the audit log intact. Pomio CRM lets admins activate and suspend users and records important actions.
Usually yes — archive deals, companies and contacts you no longer work with instead of deleting them, so history, reports and relationships stay intact and a mistake can be undone. Permanent deletion is the exception, for cases such as a privacy erasure request. Pomio CRM uses soft archive with restore and keeps relationships.
Yes — every person who works in the CRM should have their own named login; shared accounts break ownership, the audit trail, permissions and offboarding. Pomio CRM invites each user by email, gives each person their own role permissions and records actions per user in the audit log.
RBAC in a CRM combines a permission (what you may do) with a scope: own records, team records, or the whole tenant. How Pomio CRM applies own/team/tenant scopes.