glass beadian
b8671113f5
Engineering guide: session/refresh/logout architecture, publish-governance and amplify gating sections, file map to migrations 001-034. Admin guide: governance administration, files-SSO operations, verification harnesses, migration list + deploy order + 034 session note. User manual: calendar receipt badges, boost gating, connections governance note (replaces the stale 'stub' statuses). Design doc 2026-10-13: marked implemented with the as-shipped phase 2. Wiki (EN/ES): Drive sign-in + boosts/approvals. README: governance + Files SSO bullets.
1.9 KiB
| title | lang |
|---|---|
| Getting Started | 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.
5. Sign in to Files (your Drive)
Open Files from the Hub — no second password. Files (your cloud drive) uses your Hub sign-in: the first time, your account is created in the Drive automatically. If the Hub signs you out, the Drive follows within the hour. Same account, same crew, no extra credentials to leak.
6. Boosts and approvals
Boosting someone else's post works like publishing your own: the proposal is approved first, and if your collective enabled publish approval for that account, admins get a second vote before anything leaves. You'll see "awaiting publish approval" while it waits — resend once approved. Whether an account auto-publishes, needs one admin, a majority, or full consensus is your collective's choice (admins: see the admin guide).