Dashboard setup, social API credentials, and prompt writing.

Oryginal is a content operating system for multi-step social production. You define the company context, connect the publishing accounts, write strategic prompts, add visual or knowledge assets, and let the platform turn those instructions into a structured content workflow.

The system works best when every layer is aligned: the dashboard defines the account-level logic, the prompts define role-level behavior, the knowledge base adds durable brand context, and the social calendar is where final review happens before publication.

1. Set the company name and website so the system knows the account identity.
2. Select the active social platforms that this brand should run inside Oryginal.
3. Enter the publishing account identifier and the matching publishing access token for each platform.
4. Write the strategy and prompt fields so every role in the chain receives clear instructions.
5. Enable reels only when you are ready to define a weekly short-form system with exactly two posting days.
6. Save the configuration, then move to assets and the social calendar to support and review execution.

If you want a deeper explanation of the credential fields, jump to Social API credentials. If you need stronger inputs for the text fields, jump to Prompt writing guide.

In Oryginal, each platform setup uses two credential values: one identifies the publishing account, and the other authorizes Oryginal to publish on that account.

This pattern stays consistent even if some database field names are generic. What matters is the meaning of the value: the account identity must point to the correct publisher, and the token must belong to the same publishing setup.

Oryginal works best when each field has a clear job. Good prompt writing is not about writing more. It is about assigning the right responsibility to the right field.

Use the strategy fields to set the weekly direction, use the system prompts to define role behavior, and use the reels fields to define short-form logic. Do not dump every instruction into one field. That creates overlap, inconsistency, and weak outputs.

The assets manager is not a side feature. It gives the generation pipeline more durable context. Brand identity images help visual consistency. Knowledge-base documents help the strategic and creative roles stay grounded in your actual brand, market, and editorial standards.

• Upload brand imagery when you want the visual system to stay closer to a reference identity.
• Upload documents when the prompts alone are not enough to capture the brand voice, audience, product logic, or positioning.
• Use prompts for instructions and the knowledge base for durable source material.

If the dashboard prompts start becoming too long because they are storing static brand facts, move those facts into the knowledge base and keep the prompts focused on operating rules.

The social calendar is the review surface for generated posts. It is where you read the draft, inspect the visual asset, and decide whether the output is ready for publication.

• Use the calendar to review text quality and alignment with the current strategy.
• Edit post text directly when the draft is close but not fully right.
• Use the no_post action when a generated slot should be intentionally cleared instead of published.

This is also the fastest place to detect a weak upstream setup. If the calendar keeps producing off-brand posts, the fix usually belongs in the dashboard prompts, the social credentials, or the supporting assets, not in repeated manual edits.