Field manual
How Trustactic
works in Slack.
Learn how to install, start, join, and manage scene-first games in Slack without confusing gameplay with browser administration.
Product boundary
Slack gameplay
The game lives in Slack.
Commands, prompts, mission submissions, claim ceremonies, votes, private actions, and reveals all happen in team chat. The browser is not the play surface.
Browser administration
The webapp handles setup and control.
Install, billing, workspace defaults, usage, history, recaps, and support all belong here instead.
Quick start
Use this order for a first game.
The fastest safe path is install first, channel second, lobby third, and browser administration only after the Slack side is live.
First game path
Install the Slack app
Start from the Slack install flow so the workspace is connected to the installer browser session.
Add the app to a Slack channel
Choose the channel where the scene sequence will unfold.
Open the lobby
Run the first setup command in that channel.
/trustactic newLet players join
Each player joins from the same Slack channel.
/trustactic joinBegin the game
Start role reveal and the first live scene sequence once the lobby is ready.
/trustactic beginField note
Use the right reference next.
Once the game can open cleanly in Slack, use the deeper references below.
Install in Slack
Authorize the app and connect the workspace installer session.
Set up your first game
Follow the Slack-first setup path from install to lobby and begin.
Understand the player flow
See how lobby, role reveal, mission, discussion, decision, private action, reward claim, recap, reveal, and finale scenes work.
Read trust and legal
Privacy, terms, cancellation, and security boundaries for the hosted service.
Game flow
What the workspace experiences.
This is the public game rhythm customers need to understand before they install or host. It explains the scene sequence without exposing hidden role state.
Field note
Lobby
A workspace user opens a lobby in a Slack channel with `/trustactic new`. Players join from that same channel with `/trustactic join`.
Field note
Role reveal
When someone runs `/trustactic begin`, Trustactic sends private role information and the first prompts in Slack. Players stay in chat.
Field note
Mission
Formats that use missions present the task, submission, and adjudication flow in a mission scene.
Field note
Decision
The channel discusses public options in a decision scene while Trustactic tracks the current choice state.
Field note
Private action
Eligible players can take private actions or coordinate privately when the active format allows it.
Field note
Reward claim and finale
Eligible players can enter a claim ceremony when a format offers one, then the game closes with a recap, reveal, and finale scene when it ends.
Command reference
Public Slack commands only.
This field manual keeps the top-level command list focused on first-game setup and safe operational checks. Internal recovery tools and deeper scene-specific prompts are intentionally excluded from the public site.
Setup commands
These are the normal workspace commands used to open and start a game in Slack.
/trustactic newOpen a new game lobby in the current Slack channel.
If the workspace hits the free-plan gate, the response can include an upgrade path instead of creating a lobby.
/trustactic joinJoin the current lobby in that channel.
/trustactic beginBegin the game once enough players have joined the lobby.
This starts role reveal and the opening scene sequence in Slack.
/trustactic statusCheck the current game scene and safe progress information.
This is operationally useful without revealing hidden roles or private actions.
Console
What the browser is for.
Workspace admins use the console for configuration, billing, usage, history, and support. Players do not need web accounts to play.
Field note
Console for workspace admins
The console exists for the customer/operator path, not for gameplay.
No browser gameplay
Players stay in Slack.
The browser is not where votes, private actions, or player chat happen. That separation is part of the product design and privacy boundary.
Troubleshooting
First things to check when the game goes wrong.
These are the common issues a workspace organizer hits during install and the first live game.
Field note
Common issues
Trust and legal
Read the service boundaries before you install.
The legal/trust surfaces should be easy to reach and easy to read. They explain how the hosted service handles data, billing, cancellation, and support.
Field note
Frequently asked before install
These are the practical questions most teams need answered before they invite the app into a workspace.
FAQ
Is the game played in Slack or the browser?
Slack. The browser is for install, setup, billing, history, recaps, and workspace administration.
Do players need web accounts?
No. Players can join and play through Slack alone. The browser is mainly for the workspace admin path.
What does the Slack app need access to?
Enough Slack access to post scene announcements, send private prompts, handle commands, and operate the host flow cleanly.
How do plans affect games?
Free is for a first game in one workspace. Paid plans expand recurring access, history, and advanced hosted support.
Who can access the console?
The installer browser session and authorized workspace admin paths. Players do not need console access to play.
Why are debug commands missing here?
Public docs only describe supported customer-facing Slack commands. Internal recovery and operator tools do not belong on the public docs surface.
Field note
Trust pages and contact path
Read the service boundaries in plain language, then use the support route if a workspace-specific question remains.