Add Justinian to Slack so legal, policy, and regulatory teams can ask questions, analyze uploaded files, stream visible thinking, and receive generated artifacts without leaving the conversation.
Example
#legal-research
Justinian is working...
Thinking through the relevant jurisdiction, sources, and uploaded files.
Checking statutes, regulations, cases, and thread context before drafting.
Research memo.docx
Uploaded back to the Slack thread
Production workflow
The same Justinian account, now available from Slack.
Mention Justinian in any channel
Invite the app, @Justinian in a thread, and get the answer back where the work is already happening.
Reasoning controls
Use flags like --effort high, --effort max, --model, --provider, and --mode without leaving Slack.
Files in, artifacts out
Attach source documents from Slack and receive generated DOCX, PDF, spreadsheet, and other artifacts back in the response thread.
Each Slack user maps to their account
Workspace users are resolved by Slack email to their Justinian account, organization, and customer workspace.
Thread-aware continuity
Follow-ups in the same Slack thread continue the same Justinian chat for that user, preserving context.
Production OAuth install
Admins install through Slack OAuth. Tokens and thread bindings are stored in Justinian production infrastructure.
Install
Add the app in minutes.
A Slack workspace admin approves the app once. After that, each user invokes Justinian with their own Slack identity and Justinian account.
Click Add to Slack.
Approve Justinian in your Slack workspace.
Invite @Justinian to a test channel.
Ask a question or attach a file in a thread.
Use the full app when you need the full workspace.
Slack is for thread-native requests, files, and artifacts. The web app remains the command center for multi-session work, project spaces, and deeper document workflows.