Pomio CRM is a multi-tenant customer relationship management product for teams that share pipeline and score, with roles, MFA, and audit inside each tenant.
Permission type vs scope
A permission type says what action is allowed (for example view or edit). Scope says how far that action reaches: only your records, your team’s, or everything in the tenant.
Own scope
Own means the user works on records assigned to them. It reduces noise and limits accidental edits on other people’s pipeline items.
Team scope
Team extends visibility and action to the user’s team. Useful when a location or squad shares leads and opportunities.
Tenant scope
Tenant scope covers the full tenant. Administrators and broad roles use this when they must see or manage the whole organisation space.
Why scope matters in CRM
CRM data is shared work. Without scope, “edit leads” can mean the entire company. With own/team/tenant, the same role language stays clear as the team grows.
Go deeper
Is RBAC only roles like admin and user?
Roles are the package of permissions. In Pomio CRM, each permission also carries a scope (own, team, or tenant), so two people with “edit” can still see different record sets.
How does this relate to audit?
Actions remain attributable: who did what, when. Passwords and MFA secrets are not stored in the audit trail.
Does MFA replace RBAC?
No. MFA verifies the person signing in. RBAC decides what that person may do after sign-in, within their tenant.