# Quick Start setup guide

This guide is for an **administrator** setting up Sleuth for the first time. It takes only 15 minutes as long as you have:

* **Jira** admin API token (and email address)
* **GitHub** admin access (with permission to install GitHub apps)

{% hint style="info" %}
Don't use these tools? No problem! Sleuth supports lots of others, and you can find their prerequisites [here](https://help.sleuth.io/pulse/broken-reference).
{% endhint %}

### Connect your Issue Tracker and Git tool

Your issue tracker and Git repository give Sleuth most of what it needs to understand the work teams are doing, so start with these. Refer to [Integrations](https://help.sleuth.io/pulse/broken-reference) for details on how to connect these and other integrations. 

### Create a Review

Create a test review to confirm that issues and pull requests are flowing into Sleuth.

1. [Sign in](https://app.pulse.sleuth.io/sign-in) to Pulse. 
2. Click **New review** in the top-right corner of the home screen.

   <div align="left"><figure><img src="https://2832637360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1bR_-Od0islbiOl4G0%2Fuploads%2FKn0L3p8HK9OXo3aBdQ9d%2Fimage.png?alt=media&#x26;token=a74e3443-b038-4574-b835-d806be880621" alt="" width="130"><figcaption></figcaption></figure></div>
3. Select the **Monthly State of Engineering** review template.

   <figure><img src="https://2832637360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1bR_-Od0islbiOl4G0%2Fuploads%2FyA0KCSBmgy9ELf6aM6R5%2Fimage.png?alt=media&#x26;token=d501b09b-f4d9-4fd2-b283-9dc22784869d" alt=""><figcaption></figcaption></figure>
4. Wait a few seconds for the review to load, then scroll down to the ***DORA*** section. If you see data in these widgets, then your pull requests are flowing into Sleuth.&#x20;

   <figure><img src="https://2832637360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1bR_-Od0islbiOl4G0%2Fuploads%2FUPpCPqX8QgnSQ70YMhSk%2Fimage.png?alt=media&#x26;token=59ddf9fe-1451-4e7e-8aa7-62ef3acd1c4c" alt=""><figcaption></figcaption></figure>
5. Scroll down to the ***Delivery activity*** section of the review. If you see data in the widgets in this section, then your issues are flowing into Sleuth.&#x20;

   <figure><img src="https://2832637360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1bR_-Od0islbiOl4G0%2Fuploads%2Fdpr4t68Q2B3UlnGhc4hq%2Fimage.png?alt=media&#x26;token=94ee27b5-6c00-4c82-98bb-fd1ab123478d" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
If the widgets in either of the sections above are empty, [contact support](mailto:support@sleuth.io).&#x20;
{% endhint %}

### What next?

Depending on how you plan to roll out Sleuth, common next steps might be to connect [Slack](https://help.sleuth.io/pulse/broken-reference), invite [users](https://help.sleuth.io/pulse/broken-reference), or create [Teamspaces](https://help.sleuth.io/pulse/broken-reference).&#x20;