External collaboration through Slack
Collaboration with people outside of TTS falls into one of two categories:
We use different setups for each.
Collaborators may include:
- Vendors under contract (not just a Terms of Service) with TTS
- Vendors with GSA who are working on a project with TTS, for which we have an Memorandum of Understanding (MOU)
- Partners at federal agencies whose projects are under an Interagency Agreement with TTS, or at state or local agencies whose projects are under an Intergovernmental Collaboration Act agreement with TTS.
Note this does not include:
- The general public, for which we have dedicated channels
- Other feds who we are not working with directly
Contractors’ level of access will be determined by the Contracting Officer (CO). By default, contractors who are “embedded” in TTS (working on TTS projects most or full-time) can be added as full members, while other collaborators should be added as single or multi-channel guests, as appropriate.
Additonal exceptions, including a small number of close TTS collaborators at GSA, may be added as full Slack members at the discretion of the Technology Director. Examples might include the Chief Information Officer or FAS Commissioner. Ask in #admins-slack if you’d like to add someone to this category.
You may want to invite partners, contractors, etc. to specific project channels to foster collaboration and asynchronous communication with the team. Projects often create specific channels that end with
- Create a
<project>-partnerschannel, if you don’t want them in an existing channel.
- Add the partners to the channel, either:
- Through Slack Connect (preferred; see below)
- Individually, through the user request form
Slack offers this mechanism to connect channels between different workspaces. If our partner has their own Slack workspace, this is the preferred method for collaborating with them from TTS Slack, since:
- It offloads user management to the partner
- The partners can use their existing Slack accounts
- The partner is able to retain the history
- The history shows up in searches of their Slack workspace
- It saves TTS money
TTS has specific channels in Slack that are open to the public to join. These channels end with
-public. (Note: In Slack’s parlance, all channels in a workspace are either
public, allowing any full member to find/join, or
private. However, when we say “public channels” on this page, we mean channels open to all members of the public.)
.mil email addresses who aren’t collaborating on a project can be invited into public channels. Fill out the user request form.
Treat these public channels like you would a livestreamed event on GSA’s YouTube page or other type of public meeting open to guests. Materials and documents that are not otherwise public should not be shared only in public channels; instead, they should be published on TTS websites and then linked to from the public channels so that access to Slack isn’t required to see the document.
Members of the public must also comply with GSA standards and the TTS Code of Conduct.
Add a new public channel
See the instructions.
Usage of other Slack workspaces
You may be invited to other Slack workspaces operated by government entities, or entities under contract to the government. You’re allowed to join those workspaces as necessary for your work. You should join those workspaces with your government email address and ensure your avatar and profile information are consistent across Slack workspaces. If you’re invited to Slack workspaces unrelated to your job, you must join those workspaces with a personal email address.