Global Admin Settings in Slack

Updated by Marie Casabonne

Looking to set up Jira Service Management chat? Visit to find guides and more.

User permissions

Halp has three main types of users:

  • Admin
  • Agent
  • Non-billed admin


The user who installs the app on Slack automatically becomes the first Halp Admin. They'll have a settings gear icon in the top right corner next to their avatar on Halp web. Selecting this icon will allow them to edit all settings.

Admins can turn any existing agent into an admin under the Admins & Agents section. While admins can manage all global settings for Halp, they can only view tickets for the triage channels they are members of.


Agents are any Slack user who is a member of a triage channel. These users can be assigned tickets, access the Halp web app, add private notes to tickets, and perform a variety of other actions. If your team has multiple triage channels set up, agents can only view the tickets where they're added.

If a ticket lives in the #hr-issues triage channel in Slack, then an agent who is only in the #it-help triage channel wouldn't be able to view the ticket.

Non-billed admin

Non-billed admins are users that can only access Halp settings. Non-billed admins won't increase your agent count, since they aren't members of any triage channels. They can't view any tickets or metrics. Learn more about creating non-billed admins.

Halp doesn't charge for requesters — those users that open tickets. These users can't be assigned tickets, can't read or write private notes, and can't access the Halp web interface.

Triage channels

A triage channel is where your agents see and interact with tickets in Slack. These should always be a private channel in Slack, as it's how we determine who is an agent. We recommend that every team using Halp (IT, marketing, product, etc.) have their own triage channel.

Each triage channel is connected to a queue. When a ticket is created in a queue, all updates and messages related to that ticket will be synced to the triage channel. This enables agents to manage and work on tickets directly from the triage channel in Slack.

Learn more about triage channels.


Queues are a vital part of Halp — they are the backend place where tickets live on the web app. Each queue is mapped to a triage channel in Slack.

Queues have their own forms, fields, routing recipes, and can have a request team associated with them. They also have settings and configuration options that are specific to that queue.

You can have a queue for your IT, HR, legal, facilities, and any other teams in your org. Learn more about queue configuration.

Request channels

Request channels are where requesters ask for help. Any tickets created from a request channel can be directed to a preferred queue by default. We recommend these channels be public, so anyone can join and open a ticket.

Learn more about creating request channels.

Adding agents

In Halp, managing agents is as simple as adding and removing members from a Slack channel. When you first set up a triage channel, you map it to a queue. Any members of the triage channel are automatically configured as agents on the corresponding queue.

A few things to note
- When you create a new triage channel, existing members will now be considered agents in the corresponding queue.
- When you add members to an existing triage channel, they will automatically be added as an agent in the corresponding queue.
- When you remove members from an existing triage channel, they will be automatically removed as an Agent on the corresponding queue.
- If a user needs to work on multiple queues as an agent, you can simply add them to multiple triage channels. For billing purposes, they will only be counted once. Learn more about how agents affect your bill.

Invite the users you want to be agents to the triage channel using /invite or by @-mentioning the user in the channel.

Removing an agent

Halp counts any members of a triage channel as an agent. You can see a full list of your agents and edit their permission levels from Halp Web by going to Settings > Admins & Agents. Here you can also see which triage channels the user is a member of.

To remove an agent, head to the triage channel in Slack. Type /remove @[user] in the main text. Using the channel details side panel to remove the user may result in them not properly being removed, so be sure to use the slash command.

A few things to note
- If the user you are trying to remove is a Halp Admin, you'll first need to change their permission level to agent from the Settings > Admins & Agents page, then remove them from the triage channel.
- To fully remove an existing agent, you must remove the user from every triage channel they are a member of in Slack.
- After the agent has been removed from the triage channel, refresh the Settings > Admins & Agents page to confirm they are no longer listed as an agent.

Customize the bot

You can customize the Assist bot name and messaging that requesters get from the bot. Learn more about bot customization.

General settings

These settings are Global settings for all Halp users and Queues

Bot notifications

Control the direct messages sent in Slack to ticket contributors (requesters, assignee, and followers) from Assist.

  • When set to "Send ticket notifications to all contributors," requester, assignee, and followers will get direct message notifications from Assist whenever a new message is sent to the ticket thread
  • When set to "Only send ticket notifications to contributors that haven't participated on the ticket thread in Slack," users will only get direct message notifications from Assist if they haven't commented in the ticket thread yet. This will prevent double notifications in Slack from the Assist Slack bot and the thread notification for active ticket participants


Who can create tickets from reactions (using the 🎫 emoji)?

You can control if only agents and admins can create tickets from emoji reactions (or reactjis) or if all users can. Do you want to review messages before a ticket is created? If so, you can prevent requesters from creating tickets using emoji reactions, while still allowing admins and agents to make them. 

Allow any Slack user to close tickets

If you want to limit who can close tickets to agents and admins, set this to 'Disabled'.


Default agent reply type
This feature is going away on March 27, 2024. Starting on February 29, 2024, Assist will start sending whisper Slack messages to agents to tell them that their comments will soon default to public. We’ll also remind them to use the lock emoji (🔒) to send private comments.

If your team works in a way that the majority of conversation on a ticket is internal, you can set it so agent replies are automatically private.

  • When this is enabled, all messages will default to private. You can post a public message to the end-user by starting it with the megaphone emoji :mega: 📣
  • When this is disabled, all messages will default to public. You can post a private message to fellow agents in the private Triage Channel by starting it with the lock emoji :lock: 🔒
Which Slack name should show for users in Halp Web?

You can control which Slack name — full name or display name — is shown for all users on Halp Web. Do you have team members with Slack display names like “Peanut Butter,” “The Real Matt,” or “CWatt”? Make it easy on your team by selecting full name. That way, it’s quick to know who needs help, which user to add as a follower, or which agent to assign a ticket to.

Working hours

If your team has set working hours, like 8am-6pm ET, you can set those here. Working hours impact:

  • Halp reporting for First Response Time and Issue Resolution Time
  • SLAs

How did we do?