Book a demo

Security architecture

Designed for regulated, data-sensitive operations.

Separate trust boundaries, server-side authorization, approval workflows, and auditable state changes, built for IT and security evaluators who need substance, not badge collecting.

Contact security team Security documentation

Security pillars

Trust boundaries

Distinct security perimeters for each access surface.

Staff application, Customer Portal, external API clients, inbound webhooks, background workers, and administrative settings each receive explicit authentication and authorization rules, no shared assumptions across boundaries.

Read in documentation →

Role-based access control

Permissions plus record scopes on every action.

Authorization combines granular permissions with record scopes (OWN, TEAM, DEPARTMENT, ALL) and business rules. A user may hold a permission yet still be blocked when a record state or scope prohibits the action.

Read in documentation →

Approval workflows

Maker/checker patterns for high-risk operations.

Payment verification, compliance onboarding decisions, research publication, payroll approval and lock, and expense approvals follow controlled workflows. High-risk changes can require separation between the actor and the approver.

Read in documentation →

Operational history

Traceable state changes across the lifecycle.

Lead assignment and duplicate merge, payment verification and refund, customer and onboarding case decisions, research publication and revision, and integration settings changes are logged to authenticated users for review and audit.

Read in documentation →

Architecture

Explicit trust boundaries

Each access surface receives its own authentication and authorization rules. Assumptions do not carry across boundaries.

  • Staff application Operational users with RBAC and record scopes
  • Customer Portal End-customer self-service with strict self-scope
  • External APIs Scoped credentials per client or integration
  • Inbound webhooks Provider signature or shared-secret verification
  • Administrative settings Configuration changes with audit trail
Trust boundary diagram for staff, portal, API, and administrative access

Operational history

Audited state changes

High-impact lifecycle events are traceable to authenticated users, supporting compliance review, fraud detection, and operational accountability.

Login & security events Authentication activity and permission changes
Lead ownership reassignment Assignment history preserved for coaching and audit
Payment verification & refund Financial state changes with actor attribution
Compliance & onboarding decision KYC and risk assessment outcomes before activation
Research publication & revision Immutable published revisions with approval trail
Payroll approval & lock Controlled compensation and period finalization
Audit trail showing authenticated user attribution on state changes

Authentication

  • Session-based staff login with login throttling and account protection.
  • Two-factor authentication can be enforced by installation policy when your organization requires it.
  • Separate Customer Portal identity namespace, portal users access only their own records.
  • Scoped API credentials with revocation and rotation for external integrations.

Sensitive data handling

  • Least-privilege access through RBAC for KYC identity data, payment information, employee records, and compliance evidence.
  • Private documents stored outside public web directories; downloads require permission checks.
  • Masked display where full values are unnecessary for the task at hand.
  • Integration credentials encrypted at rest; secrets never stored in application source or documentation.

Application engineering controls

  • CSRF protection on browser actions; request validation on all form submissions.
  • Parameterized database operations; framework output escaping.
  • Rate limiting on sensitive endpoints; secure cookie settings and security headers.
  • File uploads restricted by type and size; permission-protected download endpoints.

Deployment and infrastructure

TradePacer CRM runs as a dedicated installation per client. Hosting environment, network access policies, backup strategy, and disaster recovery are defined during deployment planning with your team, we do not publish generic uptime or certification claims on this page.

If your evaluation requires a security questionnaire, data processing review, or architecture walkthrough, contact us with your requirements and we will respond with accurate, deployment-specific information.

Contact us about security Users & roles documentation

Evaluate security with your team

Request a security and deployment discussion tailored to your installation requirements.

Contact security team Book a demo