CredVault
Dashboard

Coder Team Collaboration

Collaborate with teammates in shared workspaces. Code together, review changes, and pair program effectively.

Sharing Workspaces

Invite to Your Workspace

  1. Click workspace
  2. Click Share
  3. Select team member(s)
  4. Choose permission level
  5. Click Send Invite

Teammate gets notification and can join immediately.

Permission Levels

View

  • Read files
  • See terminal output
  • Can't modify code
  • Perfect for code reviews
  • Perfect for demos

Edit

  • Read and modify files
  • Run terminal commands
  • Create new files
  • Delete files
  • Perfect for pair programming
  • Perfect for code reviews with changes

Admin

  • Full control
  • Stop/delete workspace
  • Change settings
  • Manage team access
  • Only give to trusted teammates

Real-time Collaboration

Simultaneous Editing

Multiple people editing same file:

alice.js:                          bob.js:
function greet() {      ←→        function calculate() {
  return "hello";                    return x + y;
}                                  }

Both see each other's changes in real-time!

Cursor Position

See where teammates are:

  • Alice's cursor: Red dot in line 5
  • Bob's cursor: Blue dot in line 8
  • Can see who typed what

Terminal Sharing

Shared terminal means:

  • Both see same output
  • Either can type commands
  • Useful for debugging
  • Or run tests together

Pair Programming

Session Setup

  1. Developer A creates workspace
  2. Shares with Developer B (Edit permission)
  3. Both click to open
  4. Same environment, same files

Best Practices

Setup

  • Use clear naming: "pair-session-feature-x"
  • Chat while working together
  • Designate driver and navigator
  • Swap roles every 15-30 minutes

Driver (actively coding)

  • Types the code
  • Navigates files
  • Runs tests
  • Navigator watches and suggests

Navigator (guiding)

  • Suggests approach
  • Catches errors
  • Checks for edge cases
  • Reviews code in real-time

Communication

Use chat while pairing:

Alice: "Let me extract this to a function"
Bob: "Good idea, name it calculateTotal?"
Alice: "Perfect"
[Alice types function]
Bob: "Add JSDoc?"
Alice: "Done"

Code Review

Share for Review

  1. Create workspace
  2. Share with reviewer (View permission)
  3. Reviewer can:
    • Read your code
    • Open terminal to test
    • See git history
    • Leave comments

Two Approaches

Live Review

  • Developer and reviewer both in workspace
  • Reviewer sees code being fixed
  • Immediate feedback
  • Fast iteration

Asynchronous Review

  • Developer shares workspace
  • Reviewer looks when ready
  • Can test running code
  • Leave comments for fixes

Inviting Team Members

Bulk Invite

Invite multiple people:

  1. Click Share
  2. Type names/emails
  3. Add multiple people
  4. Set same permission for all
  5. Click Send

Invite Workflow

Workspace: "Team Project"
Shared with:
- alice@team.com (Edit) ✓
- bob@team.com (Edit) ✓
- carol@team.com (View) ✓
- david@team.com (pending)

Click names to change permissions anytime.

Removing Access

Revoke Access

  1. Click workspace
  2. Click Share
  3. Find person
  4. Click Remove
  5. They lose access immediately

Leave Workspace

Person can leave:

  1. Click workspace
  2. Click Leave
  3. Unshared from workspace
  4. Owner still has access

Usage Scenarios

Onboarding New Developer

  1. Create full workspace
  2. Share with Edit access
  3. New developer starts with environment already set up
  4. Existing developer pairs with them (driver/navigator)
  5. New developer gets productive in hours vs days

Bug Investigation

  1. Developer reports bug to you
  2. They share workspace
  3. You join with View access
  4. Reproduce bug together
  5. Discuss fix
  6. Fix code with Edit permission
  7. Test together

Feature Development

  1. Create workspace for feature
  2. Share with feature team (3 people)
  3. All have Edit access
  4. Work on different files simultaneously
  5. Git keeps changes coordinated
  6. Review before merging

Architecture Review

  1. Create workspace with architecture
  2. Share with all senior engineers
  3. Use View permission
  4. Team examines code
  5. Discuss improvements
  6. Junior updates code with feedback

Workspace Activities

See Who's Here

Workspace shows active users:

Workspace: backend-api
Online right now:
- alice (2 hours) - In file: api.js
- bob (30 minutes) - In terminal
- carol (10 minutes) - In database.js

Activity Feed

See what teammates did:

14:30 - alice: Created file models/User.ts
14:32 - bob: Modified file routes/api.js
14:34 - alice: Committed "Add user model"
14:36 - carol: Started terminal "npm test"

Notifications

Notifications You Get

Your team did something:
- alice shared workspace "backend-api" with you (Edit)
- bob is now in workspace "frontend-app"
- carol added you to workspace "data-pipeline"

Manage Notifications

Choose what to be notified about:

  1. Click Settings
  2. Click Notifications
  3. Toggle what you want to know:
    • Shared workspaces
    • Team member actions
    • Workspace errors

Best Practices

Security

  • Only share with people who need access
  • Use View permission for sensitive code
  • Remove access when leaving project
  • Audit who has access to workspaces

Communication

  • Use chat while collaborating
  • Be explicit about who's driving
  • Ask before making big changes
  • Explain your approach

Workflow

  • Name workspaces clearly
  • Keep shared workspaces focused
  • Clean up after pair sessions
  • Use git to track changes

Troubleshooting

Person can't see my workspace

  • Check if they're invited (they should get notification)
  • Check permission level (View vs Edit)
  • Have them refresh page
  • Check if workspace is running

Changes not syncing

  • Refresh page
  • Check internet connection
  • Check if you're still in workspace
  • Check for notification of disconnect

Too many people causing lag

  • Consider separate workspaces
  • Person not actively using can Leave
  • Use git for better coordination
  • Chat instead of all in same file