ScrymeDeveloper Docs
Security Best Practices

Protect tenant data and operational integrity

Scryme’s strongest security posture comes from strict tenant isolation, least-privilege credentials, and explicit verification before every state-changing action.

Recommended controls

  • •Use tenant-scoped credentials and never reuse a staff token across multiple organizations.
  • •Validate webhook signatures before updating downstream state or triggering workflows.
  • •Scope operations by organization and verify the target entity belongs to the active tenant before mutation.
  • •Keep secrets in environment variables or a hardened secret manager and rotate them on a defined schedule.
  • •Prefer least-privilege server-side permissions for admin, inventory, and payment workflows.