Workspace basics
Choose a recognizable name for your workspace. Teams running multiple products often mirror the product name here.
Upload a square logo or mark. Scout applies it to shared reports and notification emails.
Decide which environment (production, staging, preview) Scout selects when teammates launch a new exploration.
Roles and access
Invite collaborators with their work email. Each invitation includes links to recent runs so new teammates can understand how Scout explores your product.
Notifications
Receive a daily or weekly summary of new findings and resolved issues.
Select where immediate alerts go—email, Slack, Teams, or webhooks. Each channel can be filtered by severity so only critical findings interrupt your flow.
Billing and usage
1
Pick a plan
Choose month-to-month for prototypes or annual for production teams. Plans include a baseline number of exploration hours.
2
Track consumption
The usage dashboard highlights how many hours each environment consumed. Schedule insights help prevent surprise overages.
3
Manage add-ons
Purchase extra exploration hours or reserved automation runs as your coverage expands.
Best practices
- Keep a single workspace per product so histories stay focused.
- Use descriptive environment names (“Production – US” instead of just “Prod”).
- Review access quarterly to ensure only active collaborators can launch explorations.