Skip to content

Team Sharing

Share tunnel configurations with your team using export and import.

Sharing Tunnels

Export

  1. Go to File > Export
  2. Select the tunnels to share
  3. Save the .json file
  4. Send it to your colleague

What Gets Shared

Included Not Included
Tunnel names and settings Passwords
Host addresses and ports Private SSH keys
Connection type (SSH/AWS) AWS credentials

Recipients configure their own credentials after importing.

Import

  1. Go to File > Import
  2. Select the .json file
  3. Review the tunnels
  4. Click Import
  5. Configure your credentials for each tunnel

Onboarding New Team Members

Person sharing:

  1. Export the tunnels the new member needs
  2. Send the export file
  3. Share server access requirements (which SSH key, AWS profile, etc.)

New team member:

  1. Import the tunnel file
  2. Set up SSH keys (ask your admin if needed)
  3. Configure AWS profile in Settings > AWS (if using AWS tunnels)
  4. Test each tunnel by connecting

Keeping Tunnels in Sync

When configurations change:

  1. Export the updated tunnels
  2. Share with the team (email, Slack, shared drive)
  3. Team members import the new configuration

For ongoing sync, store exports in a shared location -- a shared drive, team wiki, or private Git repository -- so members can grab the latest version anytime.

Name exports with dates (tunnels-2025-12-21.json) so everyone knows which version they have.

Best Practices

Naming Conventions

Agree on a naming pattern so tunnels are easy to find:

[environment]-[service]

Examples:
dev-postgres
staging-api
prod-redis

Separate Keys per Person

Each team member should use their own SSH key. Keys are added to servers by your admin. If someone leaves, only their key needs revoking.

Document Your Tunnels

Keep a list of your team's tunnels and who has access:

Tunnel Purpose Access
dev-postgres Development database All developers
staging-api Staging API server QA + Developers
prod-postgres Production database Leads only

Managing Access

Consider creating different export sets for different roles:

Role Tunnels
Developers Development + Staging
QA Team Staging only
Team Leads All environments
On-call Production + Monitoring

When Someone Leaves

  1. Remove their SSH key from servers (ask your admin)
  2. Rotate any shared credentials they had access to
  3. Update team documentation

Troubleshooting

Colleague Can't Connect After Import

  1. Do they have the correct SSH key?
  2. Is their public key on the server?
  3. For AWS tunnels: is the AWS profile configured in Settings?
  4. Can they connect to the server outside of StormTunnel?

Same Tunnel Works for Some but Not Others

  • SSH keys differ -- each person needs their key authorized on the server
  • AWS profiles differ -- check that IAM permissions match
  • Network access differs -- some may need VPN