Help center

1. Sign in from the header and choose a workspace (or create one).

2. Open a creation module: Studio, Social, Voice, or Media.

3. Fill in the form and start a job. Rivus creates a real workspace job with an idempotency key.

4. You are taken to Job Detail for that job.

5. Status moves through Queued → Processing → Completed or Failed.

6. Job Detail checks queued/processing jobs automatically for a short time. Activity still needs Refresh. Use Refresh on Job Detail if automatic checks stop before the job finishes.

Activity lists production history for the selected workspace. Open any row to reach Job Detail. Module pages for Social, Voice, and Media also show recent jobs for that module type.

Studio creates text drafts for posts, captions, ads, articles, and scripts. When the server is configured with AI_PROVIDER=openai, Studio returns AI-written title and body on the draft canvas. When the demo provider is selected, Studio still runs a real job lifecycle. Studio does not publish content — publish to Instagram from Job Detail or Publishing after approval.

Social creates text draft jobs for platform captions and posts. When the server is configured with AI_PROVIDER=openai, completed jobs can include AI-written draft copy on Job Detail (like Studio). With the demo provider, Social still runs a real job lifecycle but does not call an external model. Recent social jobs for the current workspace appear on the Social page. After approving a draft on Job Detail, owners and admins can publish to Instagram or schedule a future post — see Publishing. Schedule on Social creates a real Rivus automation that enqueues Social draft jobs on an interval — it does not post to networks.

Voice creates a real workspace job from your script and voice settings. When VOICE_PROVIDER=openai and OPENAI_API_KEY are configured on the server, completed jobs include playable MP3 audio on Job detail via a signed asset URL. With the demo provider, Voice still runs a real job lifecycle but does not generate audio files. Job completed is not the same as audio generated unless audio_generated is true on the result.

Media creates a real workspace job from your image or video brief. Images use OpenAI when MEDIA_IMAGE_PROVIDER=openai is configured. Video defaults to Runway when VIDEO_PROVIDER=runway; Google Veo (Gemini) can be selected per job when Gemini credentials are configured. Completed jobs include image or video previews on Job detail via signed asset URLs. With the demo provider, Media still runs a real job lifecycle but does not generate files. Job completed is not the same as media generated unless media_generated is true on the result. Generated files also appear in Media Library for reuse in content.

Media Library stores workspace uploads and AI-generated assets. Open Media to browse, preview images/video/audio, upload files, and attach assets when creating content. Assets are workspace-scoped and served through short-lived signed URLs. Assets referenced by content cannot be deleted until those references are removed.

After approving a draft on Job Detail or Publishing, owners and admins can publish to a connected Instagram account. Instagram image posts and Reels are supported; Reels require MP4 video. Publishing uses workspace-owned media only and refreshes signed media URLs before Meta fetch. Rivus does not claim unsupported networks.

Schedule approved content for a future time in your workspace timezone. Past dates are rejected. The worker publishes when due, with retries for temporary Meta processing delays. Duplicate prevention stops double-publishing the same schedule. Failed schedules stay visible with a safe error state so you can fix media or reconnect and try again.

Queued — the job is waiting for a worker.

Processing — a worker is handling the job.

Completed — the job finished. Check Job Detail for the result that was actually produced (text draft, demo echo, and so on).

Failed — the job could not complete. Rivus shows a safe failure message; retry from the creation form.

Job Detail automatically rechecks queued and processing jobs for a bounded time. Activity does not auto-refresh — use Refresh there. After Job Detail stops checking, use Refresh to check again.

Jobs and history are scoped to the authenticated workspace you select. Switch or create workspaces from the header or Settings. The selected workspace is remembered in this browser. You only see workspaces you belong to.

Starter, Business, Growth, and Pro plans include a 30-day credit pack: text costs 1 credit, images 30, and video 200. Open Billing to see your balance, usage, and upgrade options. Checkout uses PayU when configured; activation and credits are applied only after server-side payment verification.

Owners and admins can open Team from the sidebar to view members, send email invitations, change roles, or remove members. Invitations expire after a few days and must be accepted while signed in with the invited email. Members can view the roster but cannot invite or change roles.

Sign-in uses a server-managed session cookie. AI provider credentials stay on the server and are never shown in the UI or Settings. Workspace membership controls what you can open. Rivus does not expose API keys in Help or client pages.

If you forget your password, use Forgot password from the sign-in dialog. Rivus sends reset instructions only when email delivery is configured on the server. The link expires after a short time and can be used once. After resetting, sign in again with your new password — existing sessions are signed out.

Open Job Detail — it rechecks queued/processing jobs automatically for a few minutes. If you see a message to refresh, use Refresh, or check Activity. Workers process jobs asynchronously. If the job remains stuck after several refreshes, try creating again from the module form once the previous attempt has failed or completed.

Sign in again from the header. On Settings you can also Refresh session. After signing in, re-select a workspace if needed.

Create a job from Studio, Social, Voice, or Media while a workspace is selected. Empty lists mean this workspace has no jobs yet — they are not mock placeholders.

Failed jobs show a safe failure state without leaking internal errors. Return to the relevant creation module, adjust the input if needed, and start a new job.