Skip to main content

​
What Reach Provides

Credential Sets

  • Dev and prod credential sets
  • Partner hash and JWT secret
  • Partner API Key
  • Additional environments upon request

Communication & Access

  • Shared Slack channel for technical questions
  • Access to Partner Dashboard
  • Optional Reach Developer MCP Beta access for organization administrators
  • Direct line to product and engineering team

​
Optional: Connect the Reach Developer MCP (Beta)

The Developer MCP uses browser-based WorkOS authentication, not the API keys or JWT secrets listed above. An administrator authorizes one WorkOS organization, which scopes the connection to the corresponding Reach partner and its tenants. See Reach Developer MCP (Beta) for client setup and current capabilities.

​
Your Responsibilities

​
1. Store Credentials Securely

Best Practices:
  • Use environment variables or secrets management (AWS Secrets Manager, HashiCorp Vault, etc.)
  • Never commit credentials to version control
  • Rotate credentials if compromised
  • Restrict access to credentials to only necessary team members

​
2. Request Additional Environments

If you need staging, demo, or other environments beyond dev/prod:
  1. Contact Reach team via your shared Slack channel
  2. Specify what environment you need and its purpose
  3. Receive additional credential sets
  4. Configure your application to use appropriate credentials per environment

​
3. Join Communication Channels

Shared Slack Channel Usage:
  • Technical questions during implementation
  • Schema definition assistance
  • Verifying tracking implementation
  • Requesting additional credentials
  • Troubleshooting customer setup issues
The Reach team monitors your shared Slack channel during business hours. For urgent production issues, include “@channel” in your message.

​
Next Steps

Once your credentials are set up and secured, you’re ready to begin frontend integration.

Phase 2: Frontend Integration

Create JWT authentication endpoint and embed the Reach UI