Data Resource Component
A Data Resource is a table of structured data — think of it as a spreadsheet embedded inside your simulation. Use it to give participants reference material (a supplier list, a customer database, a set of applications to review) or as a live dataset that updates as the simulation progresses.
What it’s for
Common uses:
- Reference data — a price list, an org chart, a set of candidate profiles, historical sales figures.
- A working dataset — a table of job applicants, support tickets, or inventory that changes over the course of the simulation as teams (or the AI) act on it.
- Evidence for a decision — attach a data resource to a task so participants have the exact records they need to complete it, without hunting through a separate document.
Building a Data Resource
In the builder, a Data Resource has:
- Rows and columns — define your columns (name, type) and add rows, or import from a CSV.
- Visibility — each Data Resource can be set to:
- Public — every participant/team can see it.
- Team only — visible only to the owning team.
- Hidden — not shown to participants at all (useful for data the simulation uses internally, or that’s revealed later via an unlock).
- Scope — attach it at the simulation, round, subround, or task level, so it only appears where it’s relevant.
What participants see
On the player dashboard, a Data Resource renders as a read-only table:
- Participants can view and scroll through rows, but cannot add, edit, or delete anything — the table only changes through the simulation’s own logic (an AI conversation writing to it, a trigger, a facilitator action).
- Large tables have a column picker — participants can show/hide columns and use “select all” to bring back the full set, and columns are resizable to fit what they’re reading.
- If a table has more rows than fit on screen, it scrolls independently rather than pushing the rest of the page down.
- Locked Data Resources (attached to a locked round/task) are hidden or blurred along with the rest of that locked content until it’s unlocked.
How other components interact with it
A Data Resource isn’t just static content — other components can read from and write to it:
- AI Conversation components can be configured to read specific rows/columns into the AI’s context, and (if permitted) update specific columns based on the conversation’s outcome — see AI Conversation for details.
- Triggers can react to row changes (a row being created, updated, or deleted, or a row count crossing a threshold) to unlock content or adjust metrics elsewhere in the simulation.
- Submission requirements and rubrics can reference specific data resource fields when scoring a participant’s submission.
Tips
- Keep visibility as tight as you can — default to team only or hidden unless every participant genuinely needs to see the same data, so you don’t accidentally leak information one team shouldn’t have yet.
- If you plan to have an AI conversation update rows, give each row a clear, stable ID so it can be targeted reliably.
- Use CSV import for large reference tables rather than typing them in by hand.
Last updated on