Team Collaboration: Working Together

Managing user feedback is rarely a solo endeavor. Whether you’re a startup with a small team or an enterprise with dedicated support staff, Qaid’s team collaboration features help you work together efficiently. In this guide, we’ll explore how to invite team members, understand role permissions, assign feedback, and configure notifications.

Inviting Team Members

Growing your team starts with invitations. From your project settings, you can invite colleagues by email to join your project.

How to Send an Invitation

1. Navigate to your project’s Settings page
2. Scroll to the Team Members section
3. Enter your colleague’s email address
4. Select their role (Owner or Member)
5. Click Send Invitation

The invited person will receive an email with a unique invitation link. They have 7 days to accept before the invitation expires. If they don’t have a Qaid account yet, they’ll be prompted to create one when they click the link.

Managing Pending Invitations

You can view all pending invitations in the Team Members section. From here, you can:

• Resend an invitation if the original email was lost
• Revoke an invitation if you’ve changed your mind
• See when each invitation expires

Once accepted, team members appear in the active members list where you can manage their roles or remove them from the project.

Understanding Roles: Owner vs Member

Qaid uses a simple two-role system designed to balance collaboration with security.

Owner Role

Owners have full administrative control over the project. This includes:

• All member permissions (everything listed below)
• Invite and remove team members
• Change member roles (promote members to owners or demote owners to members)
• Delete the project entirely
• Manage API keys (create, revoke, rename)
• Configure project settings (domain restrictions, notification settings)
• Access billing (for the account owner)

The user who creates a project automatically becomes its first owner. Projects can have multiple owners, which is useful for redundancy if team members leave.

Member Role

Members can work with feedback but cannot make administrative changes:

• View all feedback in the project
• Archive and unarchive feedback items
• Add admin notes to feedback
• Assign feedback to themselves or other team members
• Mark feedback as read
• Create GitHub issues from feedback (if GitHub integration is enabled)

Members cannot invite new team members, modify API keys, or delete the project. This makes the member role ideal for support staff, contractors, or anyone who needs to work with feedback without administrative access.

Choosing the Right Role

Consider these guidelines when assigning roles:

Scenario	Recommended Role
Co-founders or team leads	Owner
Full-time developers	Owner or Member
Support staff	Member
External contractors	Member
QA team members	Member

When in doubt, start with the Member role. You can always promote someone to Owner later, but it’s harder to explain why you’re demoting them.

Assigning Feedback

One of the most powerful collaboration features is the ability to assign feedback items to specific team members. This creates accountability and helps distribute the workload.

How Assignment Works

1. Open any feedback item from your inbox
2. Click the Assign button (or the current assignee to change it)
3. Select a team member from the dropdown
4. The feedback is now assigned

When you assign feedback:

• The assignee receives a notification (if they’ve enabled them)
• The feedback item shows the assignee’s name and avatar
• You can filter the inbox to show only feedback assigned to specific people
• The assignment history is tracked, including who assigned it and when

Assignment Best Practices

Assign based on expertise. If feedback relates to the checkout flow, assign it to whoever owns that feature. This ensures the right person sees relevant feedback first.

Use assignments for follow-ups. When feedback requires investigation, assign it to yourself or a teammate as a reminder. The assignment acts like a lightweight task.

Don’t over-assign. Not every piece of feedback needs an assignee. Quick “thumbs up” responses might not require action. Reserve assignments for feedback that needs attention.

Clear assignments when done. After addressing feedback, either archive it or clear the assignment. This keeps the inbox clean and helps identify genuinely unassigned items.

Filtering by Assignee

The inbox supports powerful filtering to help you focus:

• Assigned to me - See only feedback you’re responsible for
• Assigned to [teammate] - See a specific person’s queue
• Unassigned - Find feedback that needs someone to own it
• All feedback - See everything regardless of assignment

Combine assignee filters with other criteria like feedback type (positive/negative), date range, or archived status for precise views of your feedback queue.

Notification Preferences

Staying informed without being overwhelmed is a balancing act. Qaid offers granular notification controls at both the user and project level.

User Notification Settings

Each team member controls their own notification preferences from their account settings:

Email Notifications

• Enable or disable email notifications entirely
• Choose between immediate notifications or daily digest
• Select which events trigger notifications:
  • New feedback received
  • Feedback assigned to you
  • Escalated feedback

Project Notification Settings

Project owners can configure project-wide notification settings:

Email Recipients

• Add email addresses that receive all project notifications
• Useful for shared inboxes or mailing lists
• Independent of individual team member preferences

Trigger Configuration

• Choose which feedback types trigger notifications:
  • Positive feedback
  • Negative feedback
  • Escalated feedback (matches escalation rules)

Escalation Rules (Pro Plan)

For high-priority feedback, escalation rules let you define conditions that trigger immediate notifications:

• Keyword matching - Alert when feedback contains specific words like “broken,” “urgent,” or “security”
• Feedback type - Escalate all negative feedback
• Console errors - Escalate feedback that captured JavaScript errors

When feedback matches an escalation rule, it’s flagged as escalated and triggers immediate notifications.

Notification Best Practices

Start minimal, then expand. Begin with only critical notifications enabled. Add more as you understand your team’s feedback volume.

Use digests for high-volume projects. If you receive dozens of feedback items daily, the daily digest email prevents inbox overload while keeping you informed.

Create a shared inbox. Add a team mailing list to project notifications so someone always sees incoming feedback, even when individuals are on vacation.

Collaboration Workflow Example

Here’s how a typical team might collaborate on feedback:

1. Feedback arrives - A user submits negative feedback about a confusing settings page
2. Notification sent - The project notification emails your team’s shared inbox
3. Triage - A team member reviews the inbox and assigns it to the designer who owns settings
4. Investigation - The designer adds admin notes documenting the issue and potential solutions
5. Resolution - After shipping a fix, the designer archives the feedback with a final note

This workflow ensures nothing falls through the cracks while distributing work across the team based on expertise.

What’s Next?

With your team set up and notifications configured, you’re ready to tackle feedback at scale. Consider exploring:

• GitHub Integration - Automatically create issues from feedback
• Custom notification templates - Brand your notification emails
• Escalation rules - Ensure critical feedback gets immediate attention

Team collaboration transforms feedback from a chore into a streamlined workflow. When everyone knows their role and stays informed, user insights actually reach the people who can act on them.