Customize your content

Who can change your content

Client Admins can change everything on this page for their own organization. A Creator is a capability a Client Admin can give to any person on top of their role. Platform Superusers, the Stride team, can act for your organization and are the only people who can edit shared Stride content.

• Client Admin: all settings, imports, review decisions, archive decisions, challenge operations, and readiness.
• Creator: author quests, challenges, trainings, micro-learnings, and resources, send their own drafts of the first four to review, submit workbooks, add synthetic data, and use Authoring Prompts. A Client Admin approves or returns what Creators send.
• Managers and learners: cannot author governed content. Learners share prompts for review from the Prompt Library, and Managers recommend or request changes on a direct report's prompt.
• Review rule: a different person must approve content from the one who wrote it or sent it to review, Platform Superusers excepted.

Shared and organization content

Learners see shared Stride content and the content your organization owns. These settings control both.

• Shared Stride content. Where: Content > Overview, in the Shared Stride content card. Who: Client Admin. Default: all three groups are on. Effect: three checkboxes, Resources and trainings, Microlearnings, quests and challenges, and Prompt library, show or hide the preloaded Stride content in learner catalogs. Your own content and learners' history stay available, and learning already started can be finished. Choose Save content choices to apply.
• Organization content. Where: Content > Challenges, Quests, Micro-learnings, Training & Resources, and Prompt Library, and Resources in the sidebar. Who: Client Admin, and Creator for quests, challenges, trainings, micro-learnings, and resources. Default: your organization starts with no content of its own. Effect: new items start as Draft and reach learners only after review and approval, except resources a Client Admin adds, which are approved right away.
• Duplicate. Where: the Duplicate button on a shared challenge, micro-learning, or prompt. Who: Client Admin only. Default: not applicable. Effect: copies an approved shared item into your organization as an editable Draft. If your organization already has a copy, that copy opens instead. Shared quests, trainings, and resources have no Duplicate button.
• Creator access. Where: Users, open a person, then the Creator switch in the Capabilities card, then Save Creator. Who: Client Admin. Default: off. Effect: gives that person the Creator area on top of their role without changing the role.

Where fit hides content and where it only ranks

Fit settings do not work the same way for every type of content. Only challenges are hidden from learners who do not match.

• Challenges: hidden from people who do not match. A learner sees a challenge only when their role group and subrole fit its role fit and their own level matches the challenge's Level.
• Quests: only changes recommendations. Every quest stays in the library for everyone. A quest appears in a learner's Recommended lane when its role, subrole, skills, level, and industry match that learner, and a Universal quest is recommended to everyone when its Assignment pool is Assigned.
• Micro-learnings and trainings: only changes ranking. Items that match a learner's role, subrole, skills, level, and industry are listed first, and the rest stay available.
• Prompts: does not change what a learner sees. Role and level fit describe the prompt, but learners see every approved prompt that passes the tool and Shared Stride content settings.
• Resources: not targeted by role. A resource's Audience, User or Admin, decides whether learners see it.
• Every type: the AI tool setting and the Shared Stride content groups can hide an item.

Audience and targeting

These fields live on each item's own form. Content is not targeted by team, organization unit, or region.

• Role and subrole fit. Where: Governed role fit on challenges, Exact role and subrole fit on quests and prompts, and Explicit role fit on micro-learnings and trainings. Who: Client Admin and Creator (governed prompts: Client Admin only). Default: you must choose, and All roles is an explicit choice. Effect: learners who do not match do not see a challenge. For quests, micro-learnings, and trainings it only changes recommendations and order, and for prompts it does not change what learners see. The choices come from the roles on your Roles page.
• Competition scope. Where: Competition scope on a challenge. Who: Client Admin and Creator. Default: Cohort. Effect: Cohort is every role, Role is exactly one role or subrole, and Role set is one or more role groups. It decides who sees the challenge and who competes together.
• Level. Where: Level on challenges and quests, Learning level on micro-learnings and trainings, and Prompt level on prompts. Who: Client Admin and Creator. Default: you choose a level, and a challenge takes the level of its linked micro-learning. Effect: learners see only the challenges that match their own level. For quests, micro-learnings, and trainings, level only changes recommendations and order, and prompt level does not change what learners see.
• AI tool. Where: Target tool on quests, AI tools on micro-learnings and trainings, Governed tools on prompts, and Platform on challenges. Who: Client Admin and Creator. Default: you choose one or more tools or Any tool, and challenges start as Agnostic. Effect: content made for one tool is hidden from learners unless your organization has that tool turned on under AI Providers and Tools in Settings. Content for any tool always shows, and Resources are never hidden by tool.
• Skills, industry fit, and other tags. Where: Skills on quests, micro-learnings, trainings, and prompts, Industry fit on micro-learnings, trainings, and prompts, Controlled industries on Specialized quests, Discipline on challenges and quests, and Assignment pool and Behavioral fit on quests. Who: Client Admin and Creator. Default: industry fit is empty, which means no industry limit, and the Assignment pool starts as Master library. Effect: skills and industry fit only change which quests, micro-learnings, and trainings are recommended, and they never hide an item. Assigned quests are ranked ahead of Master library quests, and a Universal quest is recommended only when it is Assigned. Discipline and Behavioral fit are recorded on the item and do not decide who sees it.

Publishing and review

Nothing your organization writes reaches learners until it is reviewed and approved. These settings control that path.

• Review and approval. Where: Content > Overview, in the Organization review queue. Who: Client Admin. Default: every new or changed item needs review. Effect: a draft is sent to review, by a Creator for their own work or by a Client Admin, and a different Client Admin approves it. Whoever wrote it, sent it to review, or helped write it cannot approve it, Platform Superusers excepted. The approver ticks a checklist for the exact version.
• Request changes and Archive. Where: the item drawer in the Organization review queue. Who: Client Admin. Default: not applicable. Effect: Request changes sends an item back to its author and needs a note. Archive takes a draft or a waiting item out of use.
• Archive requests. Where: the archive button beside an item on a Creator's dashboard or catalog, and the Organization review queue. Who: a Creator asks and a Client Admin decides. Default: none pending. Effect: approving a request archives the item even if it is Approved, and rejecting it leaves the item as it is.
• Active switch. Where: Active on the challenge, quest, micro-learning, and resource forms. Who: Client Admin and Creator. Default: on. Effect: inactive items are hidden from learners, and learners see an item only when its current Approved version is also Active.
• Versions and history. Where: Show history on each catalog page. Who: Client Admin and Creator. Default: history is hidden. Effect: an Approved version cannot be changed. Editing it creates a new Draft version, and approving that version makes the old one Superseded. Show history adds Superseded and Archived versions to the list.
• Pending approvals. Where: the Pending approvals panel on the Challenges, Quests, Micro-learnings, and Training & Resources pages. Who: Client Admin. Default: shown only when Creators have items waiting. Effect: lists the Creators' items that are waiting for review and opens the review queue.

Challenge schedule, points, and rules

• Release at, Program week, and Window (days). Where: the Admin Only block of a challenge form, and Release Timeline in Challenge Ops. Who: Client Admin only, because Creators see these fields turned off, and you cannot schedule a shared Stride challenge, so duplicate it first. Default: Release at is blank, which keeps the challenge a draft, Program week is blank, and Window is 14 days. Effect: a challenge goes live at its Release at time and earns points for its window, from 1 to 90 days. Program week groups challenges, and a challenge needs one to earn team-winner XP.
• Challenge point settings. Where: Challenge Ops > Point Settings. Who: Client Admin. Default: Stride's standard values, listed in Challenge Operations. Effect: live as soon as you save. Sets participation XP and BUX for four levels, XP for a like and a reply, the First-10 and Featured multipliers, the featuring cap, and the streak bonus. XP and BUX are paid only while Enable gamification and Points and rewards are on in Settings, under Gamification.
• Reward and team scoring rules. Where: Reward and team scoring in the Admin Only block of a challenge. Who: Client Admin only. Default: Advanced variance rule and Team winner rule are Disabled, base participation XP and BUX are blank so the Point Settings values apply, and the recognition choice starts empty. Effect: sets a challenge's advanced-variant XP, team winner rule and XP, and any recognition you provide. Each version carries its own rules, and team winner XP is paid only for challenges that have a Program week.
• Moderation. Where: Challenge Ops > Overview, Manage submissions on a challenge. Who: Client Admin. Default: not applicable. Effect: Feature applies the Featured multiplier up to the cap, and Unfeature reverses it. Hide removes a submission from the feed with no point change. Remove withdraws it and takes back the XP and BUX it earned.

Libraries and catalogs

• Resources. Where: Resources in the sidebar. Who: Client Admin for everything, and Creator to create and edit. Default: new resources use the User audience and the Generic provider, and are Active. Effect: a resource a Client Admin adds is approved right away, while a Creator's new or edited resource stays Pending until a Client Admin approves it. Resources with the Admin audience do not show in learners' Resources. Only Client Admins can disable, restore, or re-check a link.
• Rewards and badges. Where: Content > Rewards & Badges, on the Rewards and Badges tabs. Who: Client Admin. Default: new items are Active. Effect: a reward has a title, a type (digital, physical, or experience), a BUX cost, optional inventory, and an optional image. A badge has a title, category, rarity (a display label only), an icon, and an optional auto-award rule such as Complete N challenges or Reach N-day streak. Inactive rewards and badges are hidden, and an inactive badge is not awarded.
• Skills library. Where: Content > Skills. Who: Client Admin. Default: nothing is pending. Effect: approve a skill submission to publish it to your library, or reject it with review notes, which are required.
• Authoring Prompts. Where: Content > Prompt Library on the Authoring Prompts (for creators) tab, and the Authoring Prompts action in the Creator area. Who: Client Admin and Creator. Default: empty. Effect: prompts you copy into your own AI tools while you write Stride content. They are not shown to learners and save without review, and any author in your organization can edit or delete them.
• Synthetic data. Where: Data > Synthetic Data, Content & Data in the Creator area, and the Resources section of a challenge or quest form. Who: Client Admin for everything, and Creator to add files and attach them to their own drafts. Default: no folders. Effect: learners download the attached folder from the challenge or quest. Items a Creator adds stay hidden until a Client Admin approves them.
• Content import. Where: Data > Content import, and Content & Data in the Creator area. Who: Client Admin, and Creator from Content & Data. Default: nothing is imported. Effect: adds content in bulk from an Excel workbook of up to 4,500 content and synthetic-data rows and 4 MB. Most uploads wait for review before learners see them.

Readiness and health

• Launch Readiness requirements. Where: Content > Overview, in Launch Readiness. Who: Client Admin, and a different Client Admin reviews each change. Default: the report uses the reviewed requirements already in effect, and says so when none are set. Effect: defines the challenge themes and prompt use cases your launch report checks for.
• Legacy Readiness. Where: Data > Legacy Readiness. Who: Client Admin, and a different administrator reviews a version you contributed to. Default: each legacy version waits for a decision. Effect: you record each legacy version as reviewed ready or successor required.
• Content status. Where: Challenge Ops > Status, and the Status item in the sidebar. Who: Client Admin. Default: not applicable. Effect: lists quests, challenges, and learning modules that are blocked for learners, with an Open button for each.
• Setup guide content steps. Where: Setup, in the Content phase. Who: Client Admin. Default: each step starts pending. Effect: five steps open the pages above: Shared Stride content, Organization content, Content review, Content coverage, and Challenge schedule.

What you cannot customize

• Targeting by team, organization unit, or region. Content is targeted by role, subrole, level, tool, skill, and industry only.
• Shared Stride content itself. Only Platform Superusers edit shared items. You can switch a group off, or duplicate a challenge, micro-learning, or prompt to make your own copy.
• Approved versions. A change always creates a new version that needs review.
• The review rule. A different person must approve, and you cannot turn this off. Platform Superusers are excepted.
• Dates for content other than challenges. Only challenges have a Release at time and a window. Other content has no scheduled start or expiry.
• Translations. Stride translates your organization's content into German, Spanish, French, and Italian automatically and shows English when a translation is not ready. You cannot edit or turn off translation, and it never changes who can see an item.
• Writing content inside Stride with AI. Content written with an outside AI tool arrives through Content import, and adapted or generated content always needs independent review.