# Settings

Your team's settings can be configured in the Fabric Dashboard in Slack.

## GitHub Settings

### Default GitHub Repo

This setting determines which repository will show first when users create issues from scratch.

<div align="center"><img src="https://content.gitbook.com/content/D1GCmv3PztplZI6PqlYq/blobs/HjrJiEDIQjvp0Wds34JQ/CleanShot%202021-09-09%20at%2018.08.43@2x.png" alt=""></div>

### Fabric's Repo Access

To control what repositories Fabric has access to, or to remove a repository from Fabric, go to your GitHub Organization as an admin > Settings > GitHub Apps > Configure > Only select repositories.

![Settings](https://content.gitbook.com/content/D1GCmv3PztplZI6PqlYq/blobs/PI59ZnV7uOFB9Zd4nJbd/Repo%20Access%201.png)

![GitHub Apps](https://content.gitbook.com/content/D1GCmv3PztplZI6PqlYq/blobs/96HqSZaPwO9wArDl8JiV/Repo%20Access%202.png)

![Configure](https://content.gitbook.com/content/D1GCmv3PztplZI6PqlYq/blobs/MFvEV9G1kXEfE4CGUif5/Repo%20Access%203.png)

![Only select repositories](https://content.gitbook.com/content/D1GCmv3PztplZI6PqlYq/blobs/MzVwPQUuqpuR8sUCkwrK/Repo%20Access%204.png)

## Slack Settings

### Default Issue Channel

When you set a default issue channel, newly created issues will be sent to that channel by default.

![Issues will be sent to #fabric-issues by default.](https://content.gitbook.com/content/D1GCmv3PztplZI6PqlYq/blobs/iMyP3aEd3hgatwaBYVVy/CleanShot%202022-01-25%20at%2013.27.30@2x.png)

## Issue Settings

Issue field settings can be set for your entire team, and then overridden by [Template](../reference/templates) settings.

![](https://content.gitbook.com/content/D1GCmv3PztplZI6PqlYq/blobs/rOfXBfqXLDXyZu7mruME/CleanShot%202021-09-09%20at%2018.08.57@2x.png)

**When you show an issue field,** it means that the corresponding dropdown will show on the issue creation message:

![The top of the issue message, with all fields enabled.](https://content.gitbook.com/content/D1GCmv3PztplZI6PqlYq/blobs/2eey2o1G1fwJWnNQGUWq/Screen_Shot_2021-06-16_at_11.48.32_AM.png)

**When you&#x20;**_**require**_**&#x20;an issue field**, it just means that a message like `This issue needs at least one label` will show on the issue message.

### The assignee field

![](https://content.gitbook.com/content/D1GCmv3PztplZI6PqlYq/blobs/mJE829wO7a9zP4jCL5N7/Screen_Shot_2021-06-16_at_11.52.45_AM.png)

### The milestone field

![](https://content.gitbook.com/content/D1GCmv3PztplZI6PqlYq/blobs/nT1d61UssIsX6uOmBcXk/Screen_Shot_2021-06-16_at_11.52.56_AM.png)

### The label field

![](https://content.gitbook.com/content/D1GCmv3PztplZI6PqlYq/blobs/1OQPdIzYKQzz2JM5RNfX/Screen_Shot_2021-06-16_at_11.53.07_AM.png)

### The project field

![](https://content.gitbook.com/content/D1GCmv3PztplZI6PqlYq/blobs/4lUrqTHng4b9Ap1Pe36W/Screen_Shot_2021-06-16_at_11.53.18_AM.png)

## Issue Room Settings

![](https://content.gitbook.com/content/D1GCmv3PztplZI6PqlYq/blobs/XVZn8Md6ribvwCZRq2fh/CleanShot%202022-02-28%20at%2010.46.59@2x.png)

### Auto-creating Issue Rooms

When this setting is on, we'll automatically create a new Issue Room when an  issue in created in a connected GitHub repository.

When this setting is off, you can create Issue Rooms by clicking the `Create Issue Room` button on the issue message.

This setting can also be configured at a [Template](../reference/templates)-level.

### Auto-inviting assignees to Issue Rooms

When this setting is on, we'll automatically invite all assignees and the issue creator to an Issue Room when it's opened.

### Auto-archiving Issue Rooms

When this setting is on, we'll automatically archive Issue Rooms when their corresponding issue is closed.

When this setting is off, we won't archive any Issue Rooms.

## Feature Settings

![](https://content.gitbook.com/content/D1GCmv3PztplZI6PqlYq/blobs/z3IgedUgepTVRUT1S2Fz/CleanShot%202021-09-09%20at%2018.09.18@2x.png)

### Linking Google Docs to issues

When this setting is on, we will show a button on the issue message to link a Google Doc.

![](https://content.gitbook.com/content/D1GCmv3PztplZI6PqlYq/blobs/W35HxxvWYCjjmIGEo5VH/Screen_Shot_2021-06-16_at_11.58.35_AM.png)

![You can add an existing doc or click "create one."](https://content.gitbook.com/content/D1GCmv3PztplZI6PqlYq/blobs/lYPj4RsghmYZtzyG96Le/screen_shot_2021-06-16_at_11.59.18_am%20\(1\).png)

![If you click "create one," we'll create a new doc with the it](https://content.gitbook.com/content/D1GCmv3PztplZI6PqlYq/blobs/4BLjJjkcrEzyfgSJ18D9/Screen_Shot_2021-06-16_at_12.04.08_PM.png)

### Allow creating an issue with 🆕

**To create issues even faster,** you can react on a message with the 🆕 emoji!

Fabric will prompt you to create the issue, and will thread a link to the newly created issue, right on the message.

This is great for **quickly converting multiple messages at once into issues.**

![Reacting with the 🆕 emoji on a message lets you quickly create an issue.](https://content.gitbook.com/content/D1GCmv3PztplZI6PqlYq/blobs/HmM7pXZsEzV7C2ZcQwji/Screen_Shot_2021-06-16_at_12.11.12_PM.png)

![Once you create the issue, Fabric will link to your new issue.](https://content.gitbook.com/content/D1GCmv3PztplZI6PqlYq/blobs/UefsL15QVfCEDLhuQnqt/screen_shot_2021-06-16_at_12.11.30_pm%20\(1\).png)

{% hint style="info" %}
**Pro Tip:** Go to [slack.com/customize/emoji](http://slack.com/customize/emoji) and add the 🆕 emoji as a one-click reaction for your team, to make issue creation even faster.
{% endhint %}

## &#x20;Channel Settings

To edit your channel settings, while in a channel, type `/fabric-settings`.

### Default Channel Repository

Your channel default repository will be the first one displayed when you create an issue from scratch in a channel.

![](https://content.gitbook.com/content/D1GCmv3PztplZI6PqlYq/blobs/rzZxRz2kv9N44MEhDA4Q/CleanShot%202021-10-06%20at%2011.50.09.gif)
