FAQ
No.
We don't ask for code permissions in your GitHub repositories. We do ask for access to your issue templates, which are stored in the
.github/ISSUE_TEMPLATE
folder of your repository, so we can integrate with your existing templates. We'll never push anything to these issue template files without explicit approval from someone on your team.No. When you install Fabric on a Slack workspace, we ask you to connect one GitHub organization (not personal account).
This ensures that all your actions in the Slack workspace are scoped to that organization.
No problem! You don't need a personal GitHub account to create issues.
There are two types of accounts users on your team can have: GitHub-linked accounts, and Guest accounts.
For GitHub-linked accounts, users can only create issues in repositories that they have
write
permissions to.For Guest accounts, users can create issue in any repository that the admin has authorized and connected to Fabric. When a Guest account user create issues and comments in Slack, the bot will take that action and add a small note with the user's name, ex.
Created by Michelle from Slack
.To sign up for a guest account, when you're signing up for Fabric, simply click
I don't have a GitHub account
. Note: The admin who initially sets up the GitHub integration needs a personal GitHub account. They'll need to use an organization GitHub account, and their own individual GitHub account.
Fabric works seamlessly with issues created either in Slack or GitHub.
Leave the
Also send issues created in GitHub
checkbox checked to send issues that match those labels to the Issue Feed as well. Your Issue Feed channel will show all new issues in the connected repository that match the label filters.
When an Issue Room is created for an issue, we always link the channel in the description of the issue. See
Discuss in #tech-2927-update-readme-to-improve-onboarding
below.This makes it really easy for anyone who encounters the issue in GitHub to hop into the discussion.
Not currently, but we make it easy to import your current templates.
Unlike GitHub templates, Fabric templates are multi-repository, so you only have to create one template of each type.
Read more about Templates.
First, go to your Fabric Dashboard.
To get to your Fabric Dashboard, click
Fabric
under Apps
in your Slack sidebar.If you don't see
Fabric
there, search for Fabric
in your Slack search bar, and then click on the Home
tab.
Find Fabric in the Slack sidebar or search for it in the Fabric search bar.
Click on
Templates
.Next to the template you'd like to export, click
Export to GitHub
.
Click "Export to GitHub"
You'll see instructions on adding this template to your GitHub repository.

Go to your Fabric Dashboard in the Slack sidebar, and click
Invite teammates
.First, go to your Fabric Dashboard.
To get to your Fabric Dashboard, click
Fabric
under Apps
in your Slack sidebar.If you don't see
Fabric
there, search for Fabric
in your Slack search bar, and then click on the Home
tab.
Find Fabric in the Slack sidebar or search for it in the Fabric search bar.
If you're not signed up on Fabric, you'll see a prompt to sign up.

Click on
Link GitHub account
or I don't have a GitHub account
.When you click
Link GitHub account
, you'll be prompted to authorize your personal GitHub account, so Fabric can create issues attributed to you.
Right now, there are 4 ways to add images.
- 1.Before you create the issue, you can send a message with images in it, hover over the message, click on the three dots, and choose "create issue". See creating an issue from an existing message.
- 2.After the issue is created, you can click the
Add image 🖼
button on the issue message and drop the image in the thread. - 3.After the issue is created, you can open the threadand type your message and an image, prefaced with🧵
add
. - 4.After the issue is created, if you click the
Create Issue Room 🛋
button on the issue message to create a channel, you can use theadd
command to add images to the body.
Method #3: Adding images in the thread using the
add
command.Right now, there are 4 ways to create issues.
- 1.With a slash command, you can type
/issue
. - 2.From an existing message by clicking on the three dots.
- 3.From an existing message by reacting with the 🆕 emoji.
- 4.From the Fabric dashboard in Slack.
To create an issue, type in the
/issue
command in the compose message box of any Slack channel or DM.
You can enter a title, like
/issue Allow users to change their email
.
To create an issue from a message, hover over the message and select the three-dot button.
When the menu expands, click
Create an issue
.
Click "Create an issue...". You may have to click "More message shortcuts" the first time.
To create issues even faster, you can react on a message with the 🆕 emoji!
Note: The Fabric bot can only listen to emoji reactions in channels it's invited to. To invite the bot to a channel, type the/invite @Fabric
slash command in a channel.
This is great for quickly converting multiple messages at once into issues.

Once you create the issue, Fabric will link to your new issue in the thread, making it really easy to see where your issue went.
Pro Tip: Go to slack.com/customize/emoji and add the 🆕 emoji as a one-click reaction for your team, to make issue creation even faster.
To get to your Fabric Dashboard, click
Fabric
under Apps
in your Slack sidebar.If you don't see
Fabric
there, search for Fabric
in your Slack search bar, and then click on the Home
tab.
Find Fabric in the Slack sidebar or search for it in the Fabric search bar.
Click
Create an issue
on the main page to create an issue.
To create an issue directly from a template, click on
Templates
, click the three dots (...
) next to your template, and choose Create an issue
.

You can set a team-wide default Slack channel in your settings.
When a teammate creates an issue in Slack, it will go to the specified channel by default.

If you choose
#fabric-issues
as your team-wide default channel, new issues will go to this channel.If the issue is being created with a template, the issue will be sent to the channel connected to the template. If there's no channel connected to the template, the issue will go to the team-wide default channels.

If your template has a channel connected to it, new issues will go to that channel.
Setting a team-wide default channel.
Absolutely. Some of our customers have 100s of active Issue Room channels.
Fabric cleans up channels for you by archivesing Issue Rooms when issues close.
With Slack channels, unless you've joined, you won't get notified about updates on a channel, and it won't show up in your sidebar. You can also mute any channel that you are a member of.
The reaction for creating issues only works in channels that the Fabric bot is invited to, for privacy reasons.
To invite the Fabric bot to the channel, type
🆕
/invite @Fabric
.

We recommend doing this for all channels you'd like to use Fabric in.
First, you want to unlink your installation from GitHub, and then relink your new installation.
To uninstall from your GitHub organization, go to your organization and click
Settings
.
Click the "Settings" tab on your GitHub organization page.
Click
Configure
next to the Fabric app.
Click "Configure" next to "Fabric for GitHub".
Scroll to the bottom of the page and click
Uninstall
.
Click "Uninstall" at the bottom of the page.
This will remove the GitHub organization authorizations, as well as any personal authorizations tied to your GitHub organization.
Then, go to your Fabric Dashboard.
To get to your Fabric Dashboard, click
Fabric
under Apps
in your Slack sidebar.If you don't see
Fabric
there, search for Fabric
in your Slack search bar, and then click on the Home
tab.
Find Fabric in the Slack sidebar or search for it in the Fabric search bar.
Follow the prompts to connect your new GitHub organization.

To reinstall your Fabric Slack App, go to
app.tryfabric.com/onboarding
.
Select your Slack workspace to install.

Next, follow the prompts to connect GitHub.

If you have any further questions, email us at [email protected]
If you want to switch the account that Fabric uses to create issues on your behalf, first go to GitHub, click your profile picture in the top right corner, and click
Settings
.
Next, click
Application
on the sidebar, and Authorized GitHub Apps
.
Click
Revoke
and then go to your Fabric Dashboard in Slack.To get to your Fabric Dashboard, click
Fabric
under Apps
in your Slack sidebar.If you don't see
Fabric
there, search for Fabric
in your Slack search bar, and then click on the Home
tab.
Find Fabric in the Slack sidebar or search for it in the Fabric search bar.
There, you'll see a prompt to connect your personal account again.

Click on
Link GitHub account
or I don't have a GitHub account
.When you click
Link GitHub account
, you'll be prompted to authorize your personal GitHub account, so Fabric can create issues attributed to you.
If you're not able to create an issue in a repository with Fabric, you may not have the right GitHub permissions. You'll need
write
permissions on the repo.
Accept the invitation from your admin to create issues in the repository.
Keep in mind you may have to accept the repository invitation to have access. GitHub should send you an email with a link to accept.
To uninstall from Slack, go to your Fabric app in Slack.
Click on the
App
tab and click Configuration
.
Click on "Configuration".
At the bottom of the next page, click
Remove App
.
Click "Remove App".
To uninstall from your GitHub organization, go to your organization and click
Settings
.
Click the "Settings" tab on your GitHub organization page.
Click
Configure
next to the Fabric app.
Click "Configure" next to "Fabric for GitHub".
Scroll to the bottom of the page and click
Uninstall
.
Click "Uninstall" at the bottom of the page.
This will remove the GitHub organization authorizations, as well as any personal authorizations tied to your GitHub organization.
To give feedback or ask questions, email us at [email protected]
Last modified 7mo ago