Skip to main content

Inviting Your Team

Learn how to add team members to your Distil workspace and manage permissions.

Team Member Roles​

Distil has two roles:

Admin​

Full access to everything:

  • Review and accept cards
  • Push to integrations (Jira, Linear)
  • Manage workspace settings
  • Invite and remove team members
  • Configure integrations
  • View diagnostics and analytics

Member​

Standard product team access:

  • Review and accept cards
  • Push to integrations (if configured)
  • Add signal notes and tags
  • View the roadmap

Cannot:

  • Change workspace settings
  • Add/remove team members
  • Configure integrations
  • View admin diagnostics

How to Invite Team Members​

  1. Go to Settings → Team
  2. Click "Invite Team Member"
  3. Enter their email address
  4. Select their role (Admin or Member)
  5. Click "Send Invite"

They'll receive an email with an invitation link. The link expires in 7 days.

Best Practices​

Start Small​

Invite 1-2 people initially to establish your workflow. Add more as processes solidify.

Most People Should Be Members​

Only give admin access to people who truly need to configure integrations or manage billing.

Designate a Feedback Owner​

Pick one person (usually a PM) to be the primary "curator" of feedback. Others can contribute, but having one owner prevents confusion.

Team Workflows​

Solo PM + Engineering Lead​

  • PM reviews and accepts cards
  • Engineering lead weighs in on technical feasibility
  • PM pushes accepted work to Jira when ready

Multiple PMs​

  • Divide by product area or customer segment
  • Use tags to track ownership (e.g., "mobile-team," "enterprise")
  • Weekly sync to review accepted items together

PM + Customer Success​

  • CS adds raw feedback from customer calls
  • PM reviews and evaluates signal
  • PM shares roadmap with CS for customer communication

Collaboration Features​

Comments on Cards​

Team members can discuss feedback directly on cards. Use this for:

  • Debating whether to accept
  • Sharing additional context
  • Coordinating on push timing

Signal Notes (Shared)​

Signal notes are visible to everyone. Use them to document patterns:

  • "Requested by 5 enterprise customers"
  • "Blocks 3 other features on roadmap"
  • "Mentioned in 2 sales calls this week"

Acceptance Rationale (Important)​

When accepting a card, document why. Your team should understand the decision:

  • "Top requested feature in Q1 feedback"
  • "Prerequisite for launching European region"
  • "Reduces support load by an estimated 20%"

Team Member Limits by Plan​

Your plan determines how many team members you can invite:

  • Free: 1 member (you)
  • Starter: Up to 3 members
  • Growth: Up to 10 members
  • Enterprise: Unlimited members

Learn more about plans

Removing Team Members​

To remove someone from your workspace:

  1. Go to Settings → Team
  2. Find the team member
  3. Click "Remove"
  4. Confirm removal

They'll immediately lose access to the workspace. Cards they created or accepted remain in the system.

Managing Offboarding​

When team members leave:

Reassign their work: Review cards they were tracking and assign new owners if needed.

Preserve context: Signal notes and acceptance rationale remain, so you don't lose institutional knowledge.

Update integrations: If they had personal API keys connected, regenerate those connections.

Security and Access​

Data Access​

All team members can see all feedback in the workspace. If you need to restrict access to certain feedback, consider using separate workspaces.

Integration Credentials​

Only admins can configure integrations (Jira, Linear). This prevents accidental disconnections.

Audit Trail (Governance Pack)​

If you have the Governance Pack, you get full audit trails showing:

  • Who accepted each card
  • When decisions were made
  • Who pushed items to integrations

Learn about Governance Pack

Next Steps​