Create the workspace
Create an account, verify the email address and finish onboarding. The first owner can invite teammates later, but every person should keep an individual account and the smallest role they need.
- Name the workspace and choose the game family used by the store.
- Keep the generated development subdomain until the first release is reviewed.
- Open Dashboard → Builder and confirm that the private draft loads before changing commerce settings.
Connect and design
Connect the Tebex store from Dashboard → Integrations. Sprytto reads provider-owned catalogue and checkout data; it does not become the merchant of record.
- Save the Tebex credentials only in the protected integration form.
- Run the first catalogue sync and confirm categories, packages and prices against Tebex.
- Choose a starter theme, add reviewed components and edit Czech or English content in Studio.
- Check desktop, tablet and mobile previews before requesting a release review.
Never paste a private key or webhook secret into page content, custom CSS, a support message or a browser console.
Publish safely
Publishing compiles an immutable release from the current draft. Diagnostics must pass, required approvals must be present and the target environment must still match the reviewed revision.
- Resolve broken links, missing translations, inaccessible labels and stale media references.
- Preview the exact release and request approval when workspace policy requires it.
- Promote to production, then verify the public store, one package page and Tebex checkout hand-off.
- Use the release history for rollback; do not repair a production release by editing stored release data.