Social is now standalone — Auth integration is optional
Create Social communities without an Auth app. Bring your own user table, manage actor identity however you like, and add Auth later if you ever want it.
Until today every Social community had to wrap an Auth app — Social used Auth as the source of end-user identity, so without an app you couldn't even create a community.
That's now optional. The New community modal in the console defaults to standalone — pick a name and a slug and you're live. Actors carry whatever external_id you assign (your own user table, opaque IDs, anything stable). Cross-tenant safety is unchanged: every read/write is still gated against the owning workspace. If you do want Auth's end-user identity, tick the Connect to an Auth app option in the modal and Social will verify the app belongs to your workspace before connecting it.
On the API: app_id is now optional in the body of POST /v1/workspaces/:workspaceId/communities. Existing Auth-backed communities keep working unchanged. See the Getting started guide for the new two-path flow.