GitScrum / Docs
Todas as Boas Práticas

Convidar Membros da Equipe para Projeto GitScrum | Guia

Convide membros com permissões baseadas em papéis. Adicione desenvolvedores, gerentes e clientes com níveis de acesso apropriados para colaboração.

3 min de leitura

How to invite team members to a GitScrum project?

Invite team members by navigating to project settings, clicking "Team" or "Members," and adding their email addresses. Assign roles (Admin, Member, Viewer) to control permissions. GitScrum sends email invitations automatically. Team members can join immediately after accepting, with access to the board, tasks, and documentation based on their assigned role.

Step-by-step team member invitation:

  • Open your project - Navigate to the project board
  • Go to Settings - Click gear icon or Settings menu
  • Select "Team" or "Members" - Team management section
  • Click "Invite Member" - Opens invitation form
  • Enter email address - Team member's email
  • Select role - Admin, Member, or Viewer
  • Click "Send Invitation" - Email sent automatically
  • Member accepts - Clicks link in email to join
  • Team member roles and permissions

    PermissionAdminMemberViewer
    View board and tasks
    Create tasks
    Edit tasks
    Move tasks
    Delete tasks
    Manage columns
    Project settings
    Invite members
    Remove members

    Role recommendations by team position

    PositionRecommended RoleReason
    Project ManagerAdminFull control needed
    Tech LeadAdminManage board structure
    DeveloperMemberTask management
    QA EngineerMemberTesting tasks
    DesignerMemberDesign tasks
    ClientViewerProgress visibility
    StakeholderViewerRead-only access

    Invitation management

    • Pending invitations - See who hasn't accepted yet
    • Resend invitation - Send reminder email
    • Cancel invitation - Revoke before accepted
    • Change role - Modify after joining
    • Remove member - Revoke access entirely

    Best practices for team access

  • Start with minimum access - Elevate as needed
  • Use Viewer for clients - Prevent accidental changes
  • Limit Admins - 1-2 per project typically
  • Review periodically - Remove inactive members
  • Document access policy - In NoteVault
  • Related articles