Collaborate on security by inviting team members to your CodeThreat organization.
Invite Team Members
Navigate to Team Settings
Go to Organization Settings → Members
Click Invite Member
Click Invite Member button
Enter Email Addresses
Add one or more email addresses (one per line or comma-separated)
Assign Role
Select role for invited members:
- ADMIN: Full administrative access
- USER: Standard member access (view-only for most features)
- Custom roles: If your organization has created custom roles
Set Repository Access (Optional)
Choose repository access:
- All repositories: Access to all current and future repos
- Selected repositories: Choose specific repos
Send Invitations
Click Send InvitationsEmail invitations are sent immediately
Invitation Process
What Invited Users Receive
Email invitation with:
- Organization name
- Role assigned
- Invitation link (valid for 7 days)
- Instructions to accept
Accepting Invitations
User Clicks Link
Invited user clicks invitation link in email
Sign Up or Sign In
If existing user: Sign in
If new user: Create account
Accept Invitation
Review organization details and click Accept
Access Granted
User is added to organization with assigned role
Managing Pending Invitations
View Pending Invitations
Organization Settings → Members → Pending Invitations tab
Shows:
- Invited email
- Role
- Sent date
- Expiration date
Resend Invitation
If user didn’t receive invitation:
- Find pending invitation
- Click Resend
- New invitation email sent
Cancel Invitation
To revoke an invitation:
- Find pending invitation
- Click Cancel
- Invitation link becomes invalid
Invitations expire after 7 days. Expired invitations must be resent.
Bulk Invitations
Invite multiple team members at once:
# Enter multiple emails:
alice@company.com
bob@company.com
charlie@company.com
alice@company.com, bob@company.com, charlie@company.com
Best Practices
Assign appropriate roles: Use principle of least privilege
Set repository access: Limit access to relevant repositories
Use USER role for stakeholders: Non-technical stakeholders typically need read-only access
Invite via work emails: Use company email addresses, not personal
Review pending invitations: Cancel expired or incorrect invitations
Welcome new members: Brief them on security practices and tools
What’s Next?
