Self-hosted multi-platform broadcast newsroom for activist collectives: publishing pipeline with group approval and DST-proof scheduling, TweetDeck-style column wall with hostile-content-safe rendering, live control room with Auto Director, bridged chat governance with polls and quorum, distributed sandboxed transcode workers, encrypted content-addressed archive, monthly analytics. MIT licensed. See README.md and docs/.
29 lines
1.1 KiB
Markdown
29 lines
1.1 KiB
Markdown
---
|
|
title: Getting Started
|
|
lang: en
|
|
---
|
|
|
|
# Getting Started
|
|
|
|
## 1. Create your account
|
|
|
|
Go to `app.occupymedia.cc/onboarding` and fill in your display name, username, and password. Registering creates a personal workspace for you automatically — you are the Owner.
|
|
|
|
## 2. Understand your roles
|
|
|
|
The Hub has roles that control what each person can do:
|
|
|
|
| Role | Can do | Cannot do |
|
|
|------|--------|-----------|
|
|
| **Owner** | Everything, including deleting the workspace | — |
|
|
| **Admin** | Manage members, connections, and content | Delete the workspace |
|
|
| **Editor** | Draft, edit, and review content | Publish without approval |
|
|
| **Viewer** | Read-only access | Change anything |
|
|
|
|
## 3. Invite your crew
|
|
|
|
Go to **More → Team** and use the invite link. Share the link with your crew — they join the workspace with the role you assigned. No passwords shared, no admin phone in the loop.
|
|
|
|
## 4. Connect your first accounts
|
|
|
|
Go to **Connections** and add your platform accounts (Mastodon, Telegram, Bluesky, etc.). Each account's credentials are stored in an encrypted vault — the database never sees a plaintext key.
|