Skip to main content

Team and Member Management

![Figure Needed] Team management interface showing member list, invitations, and permission controls

Manage team members and control resource access through VNETWORK's centralized permission system.

Topics

Permission Model

VNETWORK uses Role-Based Access Control (RBAC) with three permission layers:

  1. Service-based: Access rights to specific VNETWORK services
  2. Action-based: Operations allowed (list, view, create, edit, delete)
  3. Resource-based: Access to specific resources within services

Key Benefits

  • Centralized Control: Manage multiple users through unified group structure
  • Granular Permissions: Detailed control over service and resource access
  • Activity Monitoring: Track member actions within the organization
  • Secure Collaboration: Multiple users working on shared projects safely
Security Best Practices
  • Apply "least privilege" principle - grant only necessary permissions
  • Use Exclude options for sensitive resource protection
  • Review member permissions regularly
  • Remove inactive accounts promptly