Team Collaboration¶

Share tunnel configurations with your team and collaborate effectively.

Sharing Tunnels with Colleagues¶

Share your tunnel setup so colleagues can connect to the same servers.

Export Your Tunnels¶

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

What Gets Shared¶

Your colleague will need to configure their own SSH key or AWS profile after importing.

Import Shared Tunnels¶

When you receive a tunnel file:

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¶

Get new colleagues set up quickly with your team's tunnel configurations.

Quick Onboarding Steps¶

For the person sharing:

1. Export the tunnels they'll need
2. Send the export file
3. Share the server access requirements (which SSH key, AWS profile, etc.)

For the new team member:

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

Verification Checklist¶

After importing, verify each tunnel works:

• SSH tunnels: Correct SSH key selected
• AWS tunnels: AWS profile configured in Settings
• All tunnels: Can connect successfully

Keeping Tunnels in Sync¶

When tunnel configurations change, keep your team updated.

Manual Sync (Simple)¶

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

Using a Shared Location¶

Store tunnel exports in a shared location for easy updates:

• Shared drive (Google Drive, Dropbox, OneDrive)
• Team wiki or documentation site
• Private Git repository

Team members can grab the latest configuration anytime.

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

Best Practices for Teams¶

Naming Conventions¶

Agree on a naming pattern so everyone can find tunnels easily:

[environment]-[service]

Examples:
dev-postgres
staging-api
prod-redis

Separate Keys per Person¶

For better security and audit trails:

• Each team member uses their own SSH key
• Keys should be added to servers by your admin
• If someone leaves, only their key needs to be revoked

Document Your Tunnels¶

Keep a simple list of your team's tunnels:

Managing Access¶

Who Should Have Access¶

Consider creating different tunnel sets for different roles:

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 Team Issues¶

Colleague Can't Connect After Import¶

Check these things:

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

Different Results for Same Tunnel¶

If the same tunnel works for some but not others:

• SSH keys differ: Each person needs their key authorized on the server
• AWS profiles differ: Check IAM permissions match
• Network access differs: Some may need VPN

Keeping Everyone Updated¶

When tunnel settings change:

1. Export the updated configuration
2. Notify the team (with what changed)
3. Team members re-import

Next Steps¶

• Common Workflows - Daily tunnel usage
• Import & Export - Detailed export options
• Key Management - Managing SSH keys
• AWS Settings - AWS profile configuration