Skip to main content
wit provides a comprehensive system for managing repository access through collaborators, teams, and role-based permissions.

Overview

The collaborator system includes:
  • Role-based access control with five permission levels
  • Team management for organizing collaborators
  • Email invitations for adding new collaborators
  • Activity logging for audit trails

Quick Start


Roles

wit uses five permission levels:

Permission Matrix


Commands

wit collaborator

List all collaborators (default command).
Output:

wit collaborator add

Invite a new collaborator.
Examples:
Output:

wit collaborator remove

Remove a collaborator from the repository.
Example:

wit collaborator update

Update a collaborator’s role.
Example:

wit collaborator show

Show details for a specific collaborator.
Output:

wit collaborator accept

Accept an invitation to join a repository.
Example:

wit collaborator revoke

Revoke a pending invitation.

wit collaborator invitations

List all pending invitations.

wit collaborator activity

View the activity log.
Output:

wit collaborator stats

Show collaborator statistics.
Output:

Teams

Teams allow you to organize collaborators and assign permissions to groups.

wit collaborator team list

List all teams.
Output:

wit collaborator team create

Create a new team.
Examples:

wit collaborator team delete

Delete a team.

wit collaborator team add-member

Add a collaborator to a team.
Example:

wit collaborator team remove-member

Remove a collaborator from a team.

Configuration

wit collaborator config

View or update collaborator settings.

Available Settings

Examples:

Email Notifications

wit can send email notifications for invitations using Resend.

Setup

  1. Get an API key from resend.com
  2. Configure wit:
Now invitations will be sent via email:

Best Practices

Principle of Least Privilege

Assign the minimum role necessary:
  • Use viewer for stakeholders who only need to see code
  • Use contributor for regular developers
  • Reserve admin and owner for project leads

Use Teams

Organize collaborators into teams:
  • Makes role changes easier (change team role, not individual roles)
  • Improves visibility into access patterns
  • Simplifies onboarding/offboarding

Review Activity Regularly

Check for:
  • Unexpected permission changes
  • Stale pending invitations
  • Inactive collaborators

Clean Up Stale Access

Periodically review and remove collaborators who no longer need access: