Settings

Review workspace readiness, auth state, and operating configuration

Onboarding
Workspace connectedReady

Current state for the active ReSeen workspace environment.

Channels attachedNeeds setup

Current state for the active ReSeen workspace environment.

Queue activityNo posts yet

Current state for the active ReSeen workspace environment.

Self-host auth pathDirect API key mode

Current state for the active ReSeen workspace environment.

Environment and session

Frontend URL

https://tintedapps.com

Backend URL

https://tintedapps.com/api

Postiz API key

Configured

OAuth client ID

Missing

OAuth client secret

Missing

Session secret

Configured

Auth mode

api_key

Organization

Unknown

Next configuration moves

Finish channel setup

Add or reconnect the social destinations that should actually publish from this workspace.

Set publishing defaults

Timezone, approval policy, and upload behavior are the next operational controls that need persistence.

Verify self-host backend

Confirm the always-on Postiz backend, Temporal stack, storage backend, and provider env are configured behind the branded frontend.

Open channelsReview onboarding

Self-host requirements

These are the infrastructure checks the Postiz docs make material for a real self-hosted deployment.

Long-running backend · Required

Postiz backend and worker cannot run only on Vercel/serverless. Keep the frontend on Vercel if you want, but the backend needs a real always-on host.

Temporal stack · Required

Scheduled posts and background workflows require Temporal from Postiz v2.12.0 onward.

Storage backend · Required

Choose local filesystem or Cloudflare R2 for uploaded media, then make sure public asset URLs resolve correctly.

Provider env · Required

No channels work by default. TikTok, LinkedIn, X, Instagram and others each need their own provider credentials configured in Postiz.

OIDC / Postiz OAuth · Optional

Only needed when ReSeen behaves like a separate frontend authenticating into Postiz. It is not required for the direct self-hosted API-key path.

Settings status

The settings view is now more operational, but some live workspace data failed: Postiz request failed (404): The page could not be found NOT_FOUND cle1:iad1::dlwjv-1784166524560-4fee0821dcd2 | Postiz request failed (404): The page could not be found NOT_FOUND cle1:iad1::plpcw-1784166524605-ca3aca019230 | Postiz request failed (404): The page could not be found NOT_FOUND cle1:iad1::86bx7-1784166524594-94d2ad35fb81