About Slack for UITS

  • UITS staff, to view additional information below, log into both IU Login and the Knowledge Base (see Log into the IU Knowledge Base (KB)).
  • Automatic group management and permissioning (for instance, by ADS group) is not currently available, but is being actively pursued and should be available in the future.

On this page:


Slack for UITS includes a number of channels for work-related discussions and casual conversation. There is no fee to UITS teams to join Slack for UITS, and teams who migrate from their existing Slack instances into Slack for UITS may be eligible for an ERC credit.

To access Slack for UITS, go to iu-uits.slack.com. For additional installation and configuration instructions, see Install and configure Slack for UITS.

For help or to submit requests relevant to Slack for UITS, join #slack-requests. The following are examples of questions appropriate to submit to the #slack-requests channel:

Etiquette guidelines

Be professional:

  • Keep your comments work appropriate, because everything you post will be publicly visible to all channel members.
  • Stay on topic. Posts should be relevant to their channel.
  • Use work-appropriate profile photos and custom emojis.
  • Be civil. Slack is a great platform for offering praise but a terrible platform for offering criticism.
  • Before you create a channel, consider the institutional data sensitivity classification needs of that channel, and whether Slack is an appropriate platform. In addition, consider the data classification of any information you post in Slack.

Be respectful:

  • Be welcoming. Many members are new to Slack and will make mistakes, and you can help them learn.
  • Be considerate. Slack encourages debate and discussion, but you should avoid controversial issues, politics, religion, and gossip. Avoid spamming channels and members. If a member or group is unresponsive, consider sending email instead.
  • Know the difference between @here, @channel, and mentions (in other words, @username):
    • @here sends a notification to all active channel members. This is best used for non-urgent announcements.
    • @channel sends a notification and email to all channel members. This is best used for emergencies or channel-wide announcements.
    • @username sends a notification to the specified user. This is best used for getting someone's attention.
  • When creating a new channel, consider who actually needs membership. Inviting more people than necessary leads to channel clutter and spam.


Access for non-UITS staff

Individuals and groups that are not part of UITS or Indiana University can share channels with Slack for UITS. To do so, interested groups need pre-existing access to a paid Slack instance. For other requirements, see Slack Connect guide: work with external organizations. To request the creation of a shared channel in Slack for UITS, post in the #slack-requests channel. If you don't have access to Slack for UITS, an existing Slack for UITS member must submit the request on your behalf.

Access for group accounts

By default, only personal accounts are granted access to Slack for UITS. Each active account has a fee, so group accounts (or "service accounts") are authorized for access only when there is a clear need or institutional benefit. If you wish to request access to Slack for UITS on behalf of a group or service account, post your request in the #slack-requests channel.

Install and configure Slack for UITS

You can access Slack via a web browser or a number of applications. When prompted, enter iu-uits for the workspace, and then log in with your IU username and passphrase.

Desktop app

In your browser

To access Slack for UITS in your browser, navigate to https://iu-uits.slack.com.

Mobile apps

Notification settings

By default, Slack applications will send you notifications when you receive a direct message, when someone mentions you, when someone notifies a channel you're in, and more. You may wish to adjust your settings to minimize the notifications you receive to only those you consider priority. For more about desktop notifications, see

UITS recommends that you consider the following notification options:

Display settings

Slack provides a number of options for adjusting your display settings. For help, see:

Complete your profile and set your status

Update your profile in Slack to let your colleagues know who you are and when you're available. For instructions, see:

Create and join channels in Slack for UITS

Members of Slack for UITS may create private channels as needed. Before you create a private channel, consider visiting and searching #slack-news to determine whether a similar public channel already exists.

If you would like to request the creation of a public channel, post your request in #slack-requests. Include the preferred channel name using one of the prefixes below, as well as the channel's purpose. A Slack for UITS admin will review your request and, if there is no other channel with that name or purpose, create the public channel.

Channel names

When you request a new public channel, use one of the prefixes described below in your proposed channel name. If you are creating a new private channel, UITS recommends using one of the prefixes below so that like channels are kept together when viewed alphabetically, but this is not required.

Prefix Purpose
#shared- For channels that are shared with other workspaces, or with non-UITS Slack members
#topic- For channels dedicated to discussion of a topic, typically broadly applicable across the department, such as diversity and inclusion or professional development
#offtopic- For channels dedicated to discussion of a non-work topic
#club- For channels related to formal or informal common-interest groups, such as the Living Green Team (formal group) or UITS Frisbee (informal club)
#proj- For channels related to a specific project or effort. This prefix is a good option when members from different teams need a place to collaborate.
#service- For channels related to a specific IT service. This prefix is a good way to scope a channel for discussion among adopters, service owners, and support.
#team- For collaboration within a team (in other words, a group with a common manager). Many teams will have a private "general" channel using this convention.
#unit- For discussion within a unit (in other words, a group with a common director)
#reg- For discussion within a regional campus
#div- For discussion within a division (in other words, a group with a common AVP)

For more about Slack channels, see:

Shared channel creation

Channels may be shared to Slack for UITS from existing paid workspaces. For requirements, see Slack Connect guide: work with external organizations. To request the creation of a shared channel in Slack for UITS, post in the #slack-requests channel.

Get help

  • If you wish to report harassment or abuse that has occurred in Slack, contact UITS HR.
  • To report a security or privacy violation that has occurred in Slack, follow IU guidelines to Report an IT incident .
  • For general questions about Slack, visit the Slack Help Center, or see the #slack-discussion channel. This channel is intended for questions don't require intervention by admins, such as how to use Slack, how to customize your profile and settings, how to manage notifications, and how to get the most value out of the tool. Be sure to search the channel history before asking a question, as someone may have already answered it.
  • If your issue requires assistance from Slack admins, post in #slack-requests. Members of the Slack Team (volunteers who help maintain Slack for UITS) will respond to your request as soon as possible.

This is document azoh in the Knowledge Base.
Last modified on 2023-09-26 13:29:05.