Overview
SeggWat’s team management features allow you to collaborate with your colleagues on feedback collection and analysis. This guide walks you through inviting team members, managing roles, and organizing your team effectively.Setting Up Your Team
Step 1: Navigate to Access Control
1
Open Settings
From your dashboard, click Settings in the sidebar.
2
Go to Access Control
Click the Access Control tab to view your current team members.
Step 2: Invite Team Members
1
Click Invite Member
Click the Invite Member button at the top of the Access Control page.
2
Enter Email and Role
- Email: Enter the email address of the person you want to invite
- Role: Select either Member or Admin (Owners can only be promoted later)
3
Send Invitation
Click Send Invitation. The invitee will receive:
- An email with an invitation link
- An in-app notification (if they already have an account)
4
Track Invitation Status
The invitation will appear in your team list with a “Pending” status until accepted.
Invitations expire after 7 days. You can resend expired invitations from the Access Control page.
Understanding Roles
Before inviting team members, understand which role fits their responsibilities:Member
Best for:
- Support agents
- Contractors
- Part-time helpers
- View feedback
- Create feedback manually
Admin
Best for:
- Team leads
- Product managers
- Engineers
- Manage projects
- Invite members
- Create API keys
Owner
Best for:
- Founders
- CTOs
- Finance team
- Manage billing
- Delete organization
- Everything Admins can do
Managing Invitations
Viewing Pending Invitations
Your Access Control page shows all team members and pending invitations with their status:| Status | Icon | Meaning |
|---|---|---|
| Active | ✅ | Member has joined and is active |
| Pending | ⏳ | Invitation sent, awaiting acceptance |
| Expired | ❌ | Invitation expired after 7 days |
Resending Invitations
If someone didn’t receive or missed the invitation email:- Find the invitation in the Access Control page (it will show “Pending” or “Expired”)
- Click the Resend button next to their email
- A new invitation email will be sent with a fresh 7-day expiration
Deleting Invitations
To cancel a pending invitation:- Find the invitation in the Access Control page
- Click the Delete button (trash icon)
- Confirm the deletion
Changing Member Roles
When to Change Roles
Common scenarios:- Promotion: Member becomes team lead → promote to Admin
- Temporary elevation: Need someone to help with API integration → temporarily promote to Admin
- Demotion: Admin role no longer needed → demote to Member
- Ownership transfer: Founder leaving → promote another member to Owner first
How to Change Roles
1
Locate the Member
Go to Settings → Access Control and find the member in the list.
2
Click Role Dropdown
Click the role dropdown next to their name (shows current role).
3
Select New Role
Choose the new role from the dropdown:
- Member
- Admin
- Owner (only visible if you’re an Owner)
4
Confirm Change
The role change takes effect immediately. The member will see their new permissions the next time they refresh.
Removing Team Members
When to Remove Members
- Employee/contractor has left the company
- External partner’s project is complete
- Account security (e.g., suspicious activity)
- Regular access audit cleanup
How to Remove Members
1
Navigate to Access Control
Go to Settings → Access Control.
2
Find the Member
Locate the member you want to remove in the team list.
3
Click Remove
Click the Remove button (trash icon) next to their name.
4
Confirm Removal
Confirm the removal in the dialog. This action cannot be undone (but you can re-invite them).
| Your Role | Can Remove |
|---|---|
| Owner | Everyone (except yourself if last Owner) |
| Admin | Members only |
| Member | Nobody |
What Happens After Removal
- Member immediately loses access to the organization
- They can no longer view projects or feedback
- Their previous contributions remain (feedback, comments, etc.)
- You can re-invite them later if needed
Team Organization Best Practices
Start Small, Scale Up
1
Begin with Owners
Start with 2-3 Owners (founders, key stakeholders).
2
Add Admins
Promote team leads and product managers to Admin as needed.
3
Invite Members
Add support staff, contractors, and viewers as Members.
4
Review Quarterly
Every 3 months, audit your team and remove inactive members.
Role Assignment Guidelines
- Startup (< 10 people)
- Growing Team (10-50 people)
- Enterprise (50+ people)
Recommended structure:
- 2 Owners (co-founders)
- 1-2 Admins (lead developer, product manager)
- Rest as Members
Security Best Practices
Use work email addresses
Use work email addresses
Always invite team members using their work email addresses, not personal emails. This makes it easier to track who has access and revoke it when they leave the company.
Regular access reviews
Regular access reviews
Set a recurring calendar reminder (quarterly) to review team members:
- Remove departed employees
- Demote members who no longer need elevated access
- Check for unused invitations
Principle of least privilege
Principle of least privilege
Give people the minimum role needed for their job:
- Default to Member unless they need to manage projects
- Use Admin for project/team management only
- Reserve Owner for billing and critical operations
Document role assignments
Document role assignments
Keep a spreadsheet or doc tracking:
- Who has which role and why
- When roles were granted
- Review dates for temporary elevated access
Offboarding checklist
Offboarding checklist
When someone leaves:
- Remove them from the organization
- Revoke any API keys they created
- Update project ownership if needed
- Document the removal date
Common Team Workflows
Onboarding a New Team Member
1
Prepare Access
- Determine their role (usually start with Member)
- List projects they need access to
2
Send Invitation
- Go to Settings → Access Control
- Click Invite Member
- Enter their work email and select role
3
Share Documentation
Send them:
- Link to Quickstart Guide
- Link to your organization’s feedback guidelines
- Any project-specific context
4
Follow Up
- Ensure they accepted the invitation within 7 days
- Check if they need elevated access after a trial period
Managing Contractors
Short-term contractors (< 1 month)
Short-term contractors (< 1 month)
Approach: Invite as Member with clear end date
Long-term contractors (> 3 months)
Long-term contractors (> 3 months)
Approach: Treat as regular team members
External partner companies
External partner companies
Approach: Use API keys instead of user accountsWhy: API keys are easier to revoke and don’t give partner access to your dashboard UI.
Handling Team Growth
As your team grows, here’s how to maintain organization:| Team Size | Action |
|---|---|
| 5 → 10 members | Create clear role documentation. Promote first Admin. |
| 10 → 25 members | Implement quarterly access reviews. Document role change process. |
| 25 → 50 members | Add multiple Admins. Consider API keys for systems instead of user accounts. |
| 50+ members | Establish formal onboarding/offboarding process. Audit access monthly. |
Troubleshooting
Member Didn’t Receive Invitation Email
- Check spam folder - Ask them to check spam/junk
- Verify email address - Confirm you entered it correctly
- Resend invitation - Click Resend in Access Control
- Check email deliverability - If multiple people aren’t receiving emails, contact support
Cannot Remove Last Owner
Problem: You’re trying to remove or demote the last Owner. Solution:- First promote another trusted member to Owner
- Then remove or demote the original Owner
- SeggWat requires at least one Owner for organization continuity
Invitation Shows as Expired
Problem: Invitation expired after 7 days. Solution:- Click Resend next to the expired invitation
- This creates a new invitation with a fresh 7-day expiration
- Ask the invitee to accept it promptly
Member Has Wrong Role
Problem: Someone was invited with the wrong role. Solution:- Wait for them to accept the invitation (can’t change pending role)
- Once accepted, change their role via the dropdown
- Or delete the pending invitation and send a new one with correct role
Advanced: API Key Team Management
For programmatic access, use API keys instead of user accounts:When to Use API Keys vs User Accounts
| Use Case | Recommendation |
|---|---|
| Human team member | ✅ User account (Member/Admin/Owner) |
| Automated service | ✅ API key |
| CI/CD pipeline | ✅ API key |
| External partner view-only | ✅ API key |
| External partner needs dashboard | ❌ User account (Member) |
Managing API Keys for Teams
1
Create Labeled Keys
Always add a descriptive label:
- ✅ “Production API Server - John’s Project”
- ✅ “GitHub Actions CI/CD”
- ❌ “Key 1”
2
Track Ownership
Document who created each key in your team wiki or project docs.
3
Regular Rotation
Rotate keys every 90 days for production environments:
- Create new key with updated label “(Rotated 2025-01-15)”
- Update application with new key
- Revoke old key after confirming new one works
4
Monitor Usage
Check “Last Used” timestamp monthly. Revoke keys unused for 30+ days.