# Do you use Discourse as a non-community tool?

**URL:** <https://meta.discourse.org/t/do-you-use-discourse-as-a-non-community-tool/356509>\
**Category:** General\
**Created:** [March 9, 2025, 8:53pm UTC](https://meta.discourse.org/t/do-you-use-discourse-as-a-non-community-tool/356509 "2025-03-09T20:53:44Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![thepolytrack](https://avatars.discourse-cdn.com/v4/letter/t/e79b87/32.png) [@thepolytrack](https://meta.discourse.org/u/thepolytrack)\
**Post date:** [November 19, 2026, 11:18pm UTC](https://meta.discourse.org/t/do-you-use-discourse-as-a-non-community-tool/356509/7 "2026-11-19T23:18:41Z")

</div>

Kind of! I run a small forum for the people who play and build tracks for PolyTrack (a browser racing game with unofficial fan sites like mine, [https://thepolytrack.com/](https://thepolytrack.com/)), and the private staff side has quietly become my workspace: a category for draft posts, one for bug reports from players, and one that is just links and screenshots I want to keep.

What made it stick for me was that the composer handles Markdown, pasted screenshots and drafts (even saved server-side) without any extra setup, so writing a half-finished note costs nothing. And the permissions model means the notes stay put: only staff groups see those categories, and I can share a single topic with a group when someone else needs it instead of moving files around.

The nice side effect is that the same interface is used for both jobs. No second app to learn, and when a public discussion turns into something I need to keep, it is already there.

---

_[View the full topic](https://meta.discourse.org/t/do-you-use-discourse-as-a-non-community-tool/356509)._
