Skip to main content

Publishing and Access

A story built in the editor doesn't automatically become visible to players — publishing and the access level are managed separately.

Where a story is stored​

A story isn't saved as a file in a git repository, but directly on the pdanetwork backend, through the admin API (/pdanetwork/api/v1/admin/quest/storage). The editor can:

  • save/publish a story to the server;
  • download a story back from the server (including archived versions) — useful if someone once worked on a story as a file and now needs to continue in the UI;
  • import/export a story as a local JSON file — for backups, moving between environments (dev/prod), or reviewing it "by eye" outside the editor.

The pda-quests repository, in this setup, serves more as a storage of examples and drafts as files, rather than the single source of truth — the current state of published stories lives on the server.

Access levels (access)​

RoleWho sees the story
USERAll players — a public release
TESTEROnly accounts with the tester role or higher — for checking before release
MODERATORModerators and administrators
ADMINAdministrators only

A typical story lifecycle: create it with access: TESTER → play through the story yourself in the game under a test account → fix any issues found → raise it to access: USER once the story is ready for everyone.

Logging into the editor​

Logging into the editor requires an account with a role of at least TESTER — the same role system used for access to the backend's Swagger UI and admin panel. Use the dev environment for experiments and production for the final publish; the editor's home page lets you pick the environment when downloading a story.

Next​