Team Sync
Team Sync allows you to collaborate with your team by sharing collections, environments, and conduits in real-time.
What is Team Sync?
Team Sync is Nidra's collaboration feature that enables:
- Real-time synchronization of collections and requests
- Shared environments for team-wide configurations
- Collaborative conduit development
- Version history and conflict resolution
- Team member management and permissions
Getting Started
Prerequisites
- Nidra account (create if needed)
- Team workspace (create or join existing)
- Internet connection for synchronization
Enable Team Sync
- Open Nidra settings
- Go to "Team Sync" section
- Sign in with your account
- Create a new team or join existing
- Enable sync for selected collections
Creating a Team
- Click "Team Sync" in settings
- Click "Create Team"
- Enter team name
- Optionally add team description
- Click "Create"
- Invite team members
Inviting Team Members
- Go to team settings
- Click "Invite Members"
- Enter email addresses
- Select role (Admin, Editor, Viewer)
- Send invitations
Team members will receive email invitations with join links.
Sharing Collections
Share a Collection
- Right-click a collection
- Select "Share with Team"
- Choose team
- Set permissions
- Click "Share"
Permissions
- Admin: Full control, can delete
- Editor: Can modify requests and settings
- Viewer: Read-only access
Synchronization
How Sync Works
- Automatic: Changes sync in real-time
- Bidirectional: Updates flow to all team members
- Conflict resolution: Handles concurrent edits
- Version history: Track all changes
Sync Indicators
Nidra shows sync status:
- Green checkmark: Synced
- Orange clock: Syncing in progress
- Red X: Sync error (check connection)
- Blue dot: Unsynced local changes
Manual Sync
Force synchronization:
- Right-click collection
- Select "Sync Now"
Or use the sync button in the toolbar.
Working with Shared Collections
Making Changes
- Open a shared collection
- Edit requests, add new ones, etc.
- Changes sync automatically to team
- Team members see updates in real-time
Viewing Team Activity
See what your team is working on:
- Open "Team Activity" panel
- View recent changes
- See who made what changes
- Filter by team member or date
Preventing Conflicts
Best practices:
- Communicate: Let team know what you're working on
- Work on different areas: Divide collections by feature
- Use branches (if supported): Isolate experimental work
- Sync often: Pull latest changes before making edits
Environment Sharing
Shared Environments
Share environments with the team:
- Right-click environment
- Select "Share with Team"
- Choose team
- Set read-only or editable
- Share
Best Practices
- Share base configurations: Common variables all need
- Keep secrets local: Don't share API keys/passwords
- Use parent environments: Share parent, customize child locally
Secret Variables
For sensitive data:
- Mark variables as "Secret" in shared environments
- Team members set their own values locally
- Values don't sync (only variable names)
Conflict Resolution
When Conflicts Occur
Conflicts happen when:
- Two people edit the same request simultaneously
- You edit while offline, others edit online
- Multiple people modify collection structure
Resolving Conflicts
Nidra presents conflict resolution UI:
- View your changes
- View other person's changes
- Choose:
- Keep yours: Discard remote changes
- Keep theirs: Accept remote changes
- Merge: Combine both (when possible)
- Confirm resolution
Avoiding Conflicts
- Sync frequently
- Communicate with team
- Work on different parts of collections
- Use locking (if supported)
Version History
Viewing History
See all changes to a collection:
- Right-click collection
- Select "Version History"
- Browse timeline of changes
- See who made each change
Restoring Previous Versions
Undo mistakes:
- Open version history
- Find the version to restore
- Click "Restore"
- Confirm
All team members will receive the restored version.
Offline Mode
Working Offline
You can work without internet:
- Make changes to synced collections
- Changes are queued locally
- When online, changes sync automatically
Sync on Reconnect
When internet returns:
- Nidra detects connection
- Pushes local changes
- Pulls remote changes
- Resolves conflicts if needed
Team Management
Roles and Permissions
Team Owner:
- Full control over team
- Manage members
- Delete team
Admin:
- Invite/remove members
- Manage shared collections
- Change permissions
Editor:
- Edit shared collections
- Create new requests
- Cannot manage team
Viewer:
- View shared collections
- Cannot edit
- Can duplicate to personal collections
Changing Roles
- Go to team settings
- Find team member
- Click role dropdown
- Select new role
- Save
Removing Members
- Go to team settings
- Find member to remove
- Click "Remove"
- Confirm
They lose access immediately.
Best Practices
Organization
- Create teams by project: Don't mix unrelated work
- Use clear naming: Help team find collections easily
- Document collections: Add descriptions for context
- Regular cleanup: Archive old collections
Security
- Don't share secrets: Keep credentials local
- Use viewer role: For people who only need to see
- Review permissions: Regularly audit who has access
- Remove former members: Promptly when they leave
Collaboration
- Communicate: Use team chat or comments
- Establish conventions: Agree on naming, structure
- Review changes: Check team activity regularly
- Merge carefully: Resolve conflicts thoughtfully
Performance
- Limit sync scope: Don't sync everything
- Prune history: Archive old versions
- Monitor storage: Keep team usage reasonable
Troubleshooting
Sync Not Working
Check:
- Internet connection
- Login status (signed in?)
- Team permissions (do you have access?)
- Nidra version (update if needed)
Changes Not Appearing
- Force manual sync
- Check conflict resolution queue
- Verify you're looking at shared collection
- Restart Nidra
Can't Share Collection
- Verify team membership
- Check collection ownership
- Ensure no naming conflicts
- Review team storage limits
Advanced Features
Collection Links
Share view-only links to anyone:
- Right-click collection
- Select "Get Public Link"
- Share URL with stakeholders
- They can view without account
API Documentation
Generate public API docs from collections:
- Mark collection as documentation
- Add descriptions and examples
- Publish as public docs
- Share URL with external developers
Webhooks
Get notified of team changes:
- Team settings → Webhooks
- Add webhook URL
- Select events (collection changed, etc.)
- Your system receives notifications
Migration
From Solo to Team
Convert personal collections to team:
- Create team
- Share personal collections with team
- Invite team members
- Transfer ownership if needed
Between Teams
Move collections:
- Export from current team
- Import to new team
- Update environment references
- Share with new team members
Next Steps
- Set up authentication → for team APIs
- Build conduits → collaboratively
- Explore multi-version management → with your team