This is the section to send to whoever’s setting up Deductive for your team. It’s a one-time, sequential walkthrough. Sign in, connect every relevant tool at once, install Slack, and confirm the workspace is ready. Once you’re done, point your team at Use Deductive → Welcome and you’re out of the loop. If you’re a regular user who landed here by accident, jump to Use Deductive → Welcome.Documentation Index
Fetch the complete documentation index at: https://docs.deductive.ai/llms.txt
Use this file to discover all available pages before exploring further.
Who should do this
One person. Typically the team lead, an SRE, or a platform engineer with credentials access. You need to be the one who can either get or already has:- Admin access to your team’s Datadog / Grafana / Splunk / etc.
- Owner or admin access to your GitHub org (for the GitHub App install)
- Slack workspace admin (for installing the bot)
- A list of any internal alerting URL patterns your team uses
What you’ll do
Five short pages, in order:1. Sign in
Find your workspace URL (
app.deductive.ai for self-serve, or your <company>.deductive.ai Enterprise URL). Sign in.2. Connect your stack
Single comprehensive page. Walk through every connector your team needs in one sitting. Code, observability, incidents, infra, errors.
3. Connect Slack
Install the Deductive Slack app at the workspace level. Once. Everyone benefits.
4. Done-when checklist
Confirm the workspace is genuinely ready before sharing the user docs with the team.
How long this actually takes
| Phase | Active time | Realistic wall-clock |
|---|---|---|
| Sign in | 1 min | 1 min |
| Connect your stack | 15 min | 15–60 min (depends on how many credentials you have to hunt down) |
| Connect Slack | 5 min | 5 min |
| Verify with the checklist | 5 min | 5 min |
Hand-off when you’re done
Once the checklist is fully green:- Share Use Deductive → Welcome with your team. That’s the user-facing entry point.
- Optionally, drop a one-liner in your team channel: “Deductive is set up. Start at [link].”
- You’re done. Day-to-day use doesn’t require admin involvement; users configure their own per-channel alert routing, MCP installs in their IDEs, and feedback.
Try this next
Sign in
First step. Find your workspace URL and sign in.