Teams are currently available for select organizations. If you don’t see Teams, contact support.

​
What are Teams?

Teams let you scope Decipher to the areas of your product that each group owns. A team is defined by:
  • URL patterns: pages or paths the team is responsible for (e.g. /checkout, /admin, settings, or billing).
  • Members: org users who belong to the team for quick switching and visibility.
When a team is selected, Decipher filters what you see to that team’s surface area:
  • All Issues: shows only issue collections whose affected page matches the team’s URL patterns. You’ll see badges like “Trending Issues (last 24 hours) for your team” and an info tooltip listing the team’s URLs.
  • Home: trending issues and summaries reflect the selected team.
When no team is selected (All Teams), you see org‑wide results.

​
How to create a team

  1. Go to Settings → Team Management.
  2. Click Create Team.
  3. Enter a Team Name.
  4. Add Page URLs the team owns. Use simple contains matches; for example:
    • /setup matches /home/setup/1
    • billing matches /org/billing/plan Tip: keep patterns short and specific to the area the team owns.
  5. (Optional) Select Members from your org to add to the team.
  6. Save Team.
Behind the scenes, Decipher uses these URL patterns to filter collections on the All Issues page and the dashboard when that team is active.

​
Adding members to a team

Members are used for convenience and visibility—they do not change filtering rules. Anyone in the org can switch to a team view, but adding members:
  • Makes the team easy to find in the selector for those users.
  • Helps communicate ownership in settings.
To add or modify members:
  1. In Settings → Team Management, open an existing team.
  2. Use the Members picker to add or remove users.
  3. Save.

​
Switching between team views

Use the team selector at the top of All Issues and the Home dashboard.
  • All Teams: clears the team filter and shows org‑wide data.
  • Specific Team: filters views to that team’s URL patterns. You’ll see a small info icon next to section headers that shows which URLs are applied.
Notes:
  • Switching teams updates lists immediately (e.g., Most Recent, Trending Issues) to reflect the selected team.
  • Sorting and filters you apply (like issue type, user, account) work on top of the team filter.
  • If you don’t see the team selector, your org may not have Teams enabled yet.

​
Tips for effective teams

  • Keep URL patterns short and stable (e.g., /checkout instead of full URLs).
  • Align each team’s patterns with clear ownership boundaries.
  • Start with one or two patterns, then refine as needed.