Access control
Territorial boundaries you can trust.
A user cannot reach data outside their authority, even with a direct API call. UI filters narrow scope further; they never widen it.
Defense in depth
Multiple layers. One trusted boundary.
The platform enforces access at the layer that actually matters: where the data lives. Other layers exist for performance and UX; they are not security boundaries on their own.
- Identity
- Bring your identity provider. Multi-factor required for everyone, step-up required for destructive actions.
- Authorization
- Every request is checked against a central policy. Deny is the default.
- Data scope
- Every query is automatically scoped to the user's market and team. Out-of-scope rows are simply not returned.
- Operational
- Database accounts are least-privileged. Even if application code were bypassed, the underlying infrastructure resists damage.
Markets
A controlled vocabulary you own.
Markets are the most security-sensitive attribute in the platform. Every lead has one. Every query scopes by it. Every change is audited.
- Vocabulary
- Global. India, the United States, the United Kingdom, Germany, France, Italy, Spain, the Netherlands, Singapore, Australia, the UAE, Saudi Arabia, Brazil, Japan, and every country in between. Admin-editable per organization.
- Custom segments
- Continents (Europe, Africa, APAC), trade blocs (EU, GCC, ASEAN), or arbitrary business segments. Not restricted to countries.
- Tagging
- Each lead is tagged with its market deterministically at ingestion. The rule is set per connector.
- Quarantine
- Records that cannot be confidently tagged stay in a quarantine queue until an administrator assigns one. Nothing is silently defaulted.
- Reassignment
- Changing a lead's market is a deliberate administrative action and is itself audited.
Roles
Composable scopes. Bounded administration.
A user has a base role, one or more market scopes, and an optional team scope. A regional administrator can manage users within their market, never globally.
- Sales representative
- Works leads assigned to them, plus unassigned in their market when configured. Writes their own leads.
- Team lead
- Works the team within their market. Writes the team's leads.
- Regional manager
- Works their assigned market. Writes leads and assignments in market.
- Regional administrator
- Plus: configures workflows; manages users and roles within their market.
- Global head
- Reads all markets. No write.
- Super administrator
- All markets, all operations. Required for cross-market changes.
- Auditor
- Defined scope, read-only.
- Service account
- Programmatic identity for integrations, scoped to specific operations and markets.
Built for organizations that run sales across markets.
Talk to us about your deployment, your access model, your sources. We will follow up within one business day.