Assign technical ownership
Owners, Admins, and Developers can manage technical setup while Billing and Viewer roles remain bounded.
CRM integration operations
Keep shared CRM integrations inside one reviewed workspace boundary
ThrottleProxy can centralize caller keys, exact destination rules, traffic protection, member permissions, and safe operational evidence for a reviewed CRM integration. Provider credential storage and automatic data synchronization are not connected.
Workspace scopedRole governedProvider neutral
Practical boundaries
Make integration ownership and traffic policy visible
Approve the provider host
Use the smallest exact public hostname or explicit one-level wildcard required by the integration.
Protect shared capacity
Apply rate, queue, concurrency, size, and timeout boundaries before high-volume synchronization work.
Keep credentials separate
ThrottleProxy authentication is never the upstream CRM credential and is removed before forwarding.
Audit workspace actions
Use tenant-scoped audit events for supported key, destination, member, invite, and configuration actions.
Escalate with safe context
Support cases should include bounded status and timing evidence, never contacts, access tokens, or raw bodies.
Good fit
- Workspace-owned integrations with a known CRM API destination.
- Teams that need role clarity around keys, destinations, and support.
- Synchronization traffic that benefits from bounded shared resources.
Not a replacement for
- A turnkey CRM connector or field-mapping product.
- Storing OAuth refresh tokens or injecting provider credentials.
- Unbounded background synchronization without application-level reconciliation.
Common questions
Does ThrottleProxy provide CRM OAuth storage?
No. Upstream credential storage is not connected and must be designed as a separate reviewed capability.
Can a wildcard approve every CRM domain?
No. Plain entries match exact hosts, and explicit wildcards match exactly one subdomain level after broad and public-suffix patterns are rejected.
Does it replace synchronization state?
No. The application remains responsible for cursors, records, reconciliation, and provider-specific lifecycle behavior.
Start with one narrow integration
Use one workspace key, one exact public host, and non-sensitive test traffic.