Team Management
Collaborate with your team and share tunnel resources
Overview
NGSRV is built around teams. All resources (domains, policies, API tokens, tunnels) belong to teams, not individual users. This allows for seamless collaboration and resource sharing.
Key Concepts
- • Every user has a personal team (created automatically)
- • You can create additional teams for organizations
- • Team owners can invite members via email
- • All resources are team-scoped
- • Billing and usage are tracked per team
How Teams Work
Personal Team
When you sign up, a personal team is created automatically with your name. This team is perfect for individual projects and testing.
Organization Teams
Create additional teams for your company or organization. Invite team members and share resources like domains, security policies, and API tokens.
Team Resources
All of the following belong to teams:
- Custom Domains - All team members can use team domains
- Security Policies - Shared policies for consistent protection
- API Tokens - Team tokens for CI/CD and automation
- Tunnels - View all team tunnels in the dashboard
- Analytics - Team-wide usage and request logs
Managing Teams
Accessing Team Settings
Go to Dashboard → Teams to manage your teams.
Creating a New Team
- Click "Create Team" button
- Enter team name (e.g., "Acme Corporation")
- Click "Create"
- You're now the team owner
Inviting Team Members
- Select your team from the teams list
- Click "Invite Member"
- Enter their email address
- They'll receive an invitation email
- Once accepted, they can access all team resources
Switching Teams
Use the team selector in the dashboard header to switch between your teams. The CLI automatically uses your active team.
Team Roles
| Role | Permissions |
|---|---|
| Owner |
|
| Member |
|
Full Capture Mode
Full Capture is a paid feature that allows teams to log complete request and response bodies for debugging purposes.
⚠️ Important
- • Full Capture is a team-wide setting
- • Only available on Pro or Pay-as-you-go plans
- • Requires explicit consent from team owner
- • Logs complete request/response bodies (up to 1MB each)
- • Default: only minimal data (method, path, status, timing) is logged
Enabling Full Capture
- Upgrade to a paid plan
- Go to Teams
- Select your team
- Toggle "Enable Full Capture"
- Confirm you understand data implications
Once enabled, all new requests will have full bodies logged.
Use Cases
- Webhook Debugging - See exact payload sent by Stripe, GitHub, etc.
- API Development - Debug request/response bodies during integration
- Error Investigation - Investigate malformed requests causing errors
Common Team Workflows
Workflow 1: Shared Development Environment
- Create team for your project
- Invite all developers
- Create custom domains per developer (e.g., "alice-dev", "bob-dev")
- Create shared security policies (IP whitelist for office)
- Each dev uses their own domain with shared policies
- View all active tunnels in team dashboard
Workflow 2: Client Demo Environment
- Create custom domain "client-demo"
- Apply password authentication policy
- Share URL and credentials with client
- Monitor requests in analytics
- Revoke access by changing policy or stopping tunnel
Workflow 3: CI/CD Integration
- Create team API token
- Add token to CI secrets
- Create custom domains for preview deployments
- Apply rate limiting and WAF policies
- Tunnels created in CI are visible to all team members
- Monitor CI tunnel usage in team analytics
Best Practices
✅ Separate Personal & Work
Use your personal team for side projects, create organization teams for work.
✅ Name Domains Clearly
Use descriptive domain names: "myapp-alice", "staging-preview", "demo-client"
✅ Share Security Policies
Create team-wide policies instead of everyone making their own.
⚠️ Regular Token Rotation
Rotate team API tokens periodically, especially after team members leave.
💡 Use Full Capture Sparingly
Enable Full Capture only when debugging, disable after to save costs.