# Publish Choose the learners who can use it. ## The user journey from an assembled build to a published version Confirm the build, choose who can access it, optionally translate and review it, then publish and open the published version. 01 ### Confirm the current build 1. After testing, return to the same project and select Deploy. 2. If Source changed — rebuild recommended appears, return to Simulation to rebuild and test. 3. Publish the content you last checked, not an earlier preview. 02 ### Choose the audience 1. Choose the intended audience. 2. For selected internal staff, choose By Tags and then the actual tags; choose All Organization Members only when everyone should have access. 3. By Tags without any selected tags blocks publishing. 4. If there are no tags, return to SpeedL Team Members to arrange them. 5. Choose Public only for material suitable for public sharing. For internal policy training, follow your organization’s sharing rules. Do not make internal training public simply to simplify a test. **Why this matters**An available public option does not mean the content is appropriate to share publicly. **Check the result**The audience matches the sharing and training purpose. Not the expected result? Resolve audience or permission mismatches with an administrator; do not use public sharing as a workaround. 03 ### Translate and review when needed 1. Skip this step when the primary language is sufficient. 2. Otherwise, under Other Languages select Select languages..., tick the languages, then Confirm; the Translate button appears only after languages are selected. 3. To keep terminology consistent, expand Translation Style Guide (optional) and upload a PDF, TXT, or DOCX file, or paste text. 4. Select Translate and wait for the result, then select Review Translation, check dialogue, choices, and endings, then Confirm Translation. 5. Save & Close leaves review work to finish later. 6. If some languages fail, address those languages rather than treating partial completion as full success. **Why this matters**A mistranslated negation or condition can reverse the intended decision. **Check the result**Every language being delivered has been reviewed. Not the expected result? Correct semantic errors and retest affected paths; translated text alone is not sufficient. 04 ### Publish and open the version 1. After checking the audience and languages, select Publish to open Review game information. 2. Check Game name and enter or edit Description. For AI help, select AI generate description · SP billed by usage, review and edit the AI draft, then select Use this draft or Discard draft. The SP charged is shown below the draft. If Generate the full plan before creating a description. appears, complete the plan first; if generation fails, you can select Report error. 3. Select Save and publish: the name and description are saved to the project before publishing starts. Wait for the published status and version details, then select Launch Published. 4. Check the customer-service text and choices in the published version. 5. If a button is unavailable, check the build, changed sources, translation review, audience tags, and whether description generation or an unhandled draft is blocking the information dialog. 6. Only after publication should you return to SpeedL to add the simulation to a training journey. **Why this matters**Simulation publication and journey activation are separate. Publishing source changes does not prove an existing journey binding changed automatically. **Check the result**The published version is usable and identifiable in the journey content picker. Not the expected result? Resolve publication errors and verify again. For existing journeys, follow version/replay guidance rather than asking learners to erase history. ## Add the published material to training Published material is not yet a training journey. Return to SpeedL, open the intended journey, and add a simulation stage using this material and version. Continue with the linked guide. ### Control access Choose organization-wide, tag-based, or public access for the published version. ### Review language versions Translate selected languages and inspect the results before they become part of the published experience. ### Verify the published version Use the published status, version number, and Launch Published action for a final check. **What you will see when completed**The version is published for the selected audience and can be opened for a final check. After publishing the material, open the published version to check the learner experience. To use it in a training journey, add a simulation stage, select this published material, set the clear rule, and publish the journey. Publishing the material and publishing the journey are separate steps. [Build your first training journey](creator-journeys.md) [Add content and order the stages](creator-journey-stages.md)