# Slack guidelines

## General rules

**Threads** 

* Threads are your friend! If your message is responding to, or continuing/following up on a conversation about something that's already on Slack then it goes into that thread.

**DMs vs Channels**

* If you're having a general discussion about work, it should probably be in a DM. If it's not about a specific project that has a channel then put it in a DM. Work happens in channels.
* Keep channels public unless they are on confidential projects.
* Don't join channels you don't have to have to be in. You can still DM folks in a group, you can still be @ed in to a channel you are not in. 
* You can [forward important emails](https://slack.com/slack-tips/send-email-to-slack) to a channel as well.

**Security**

* Slack **IS *****NOT*** a secure platform, it's ***not***** for password sharing** (use Passbolt). 
* If you are working on a story where your threat model is one involving the state or other highly resourced gang/corporation/entity - best to keep that in Signal.

**Pinning posts vs Bookmarks**

* Make use of pinned posts for say latest minutes for the next meeting, or the doc about the topic.
* Links are great for long term project trackers and key links e.g. to the leave log.

## Naming conventions for Cable Slack

Each channel should start with the parent circle e.g. *media-production* is about production and is a Media team project. The next print channel name would be *media-edition100.*

Team-wide channels begin 'team', so *team-meeting* is only for team-meeting-related proposals.

## Useful links

{% embed url="<https://slack.com/intl/en-gb/blog/collaboration/slack-essentials-organize-your-work-and-conversations>" %}

{% embed url="<https://downloads.slack-edge.com/blog/Channel+Naming+Conventions.pdf>" %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://handbook.thebristolcable.org/staff-guides/slack-guidelines.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.