This page lists the tools you’ll use day-to-day at Meridian Seven, how to access them, and key setup notes.
| Tool | Purpose | Access | Setup Notes |
|---|
| Google Workspace | Email, Calendar, Drive, Meet | @meridian7.io account | Primary identity — set up first |
| Slack | Team communication | Invitation from CTO | Join all channels relevant to your role |
| Tool | Purpose | Access | Setup Notes |
|---|
| GitHub | Source control, issues, PRs | Meridian7-io org invitation | Enable 2FA; set up SSH keys |
| Vercel | Frontend deployment | Team invitation | GitHub SSO login |
| Supabase | Database (PostgreSQL) | Org invitation | GitHub SSO login |
| Railway | Backend services | Team invitation | GitHub SSO login |
| VS Code | Code editor | Install locally | Recommended extensions in repo .vscode/ |
| Tool | Purpose | Access | Setup Notes |
|---|
| 1Password | Password management | Team invitation | Install app + CLI; see device setup |
| Doppler | Secrets management | Workplace invitation | CLI: brew install dopplerhq/cli/doppler && doppler login |
| CrowdStrike Falcon | Endpoint security (EDR) | Auto-installed by setup script | Runs silently; do not disable |
| Tool | Purpose | Access | Setup Notes |
|---|
| BetterStack | Uptime monitoring, logs, on-call | Team invitation | Check on-call schedule |
| Cloudflare | DNS, CDN, WAF | Account invitation (leadership only) | N/A for most roles |
Not everyone needs access to every tool. Your access is based on your role:
| Tool | Engineer | Operations | Finance | Leadership |
|---|
| Google Workspace | ✓ | ✓ | ✓ | ✓ |
| Slack | ✓ | ✓ | ✓ | ✓ |
| 1Password | ✓ | ✓ | ✓ | ✓ |
| GitHub | ✓ | — | — | ✓ |
| Vercel | ✓ | — | — | ✓ |
| Supabase | ✓ | — | — | ✓ |
| Railway | ✓ | — | — | ✓ |
| Doppler | ✓ | — | — | ✓ |
| BetterStack | ✓ | — | — | ✓ |
| Cloudflare | — | — | — | ✓ |
| Stripe | — | — | ✓ | ✓ |
For full role definitions and access levels, see the Access Control Policy.
Your manager initiates access provisioning via the onboarding workflow. Most systems are provisioned automatically — check your onboarding GitHub Issue for status. If you’re missing access to something, ask the CTO.
