video1.0<iframe src="https://www.loom.com/embed/28d3c43c593b4088b7582f5cbefb0cf3" frameborder="0" width="1920" height="1440" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>14401920Loomhttps://www.loom.com14401920https://cdn.loom.com/sessions/thumbnails/28d3c43c593b4088b7582f5cbefb0cf3-9df4a138158aae49.gif414.466667This Loom maps the admin setup steps for the Dash 360 risk module, showing what each setting controls and the recommended order. It explains that end users manage risks in the risk register, where fields like ID, category, type, spread type, and the labels “Risk” versus “Mitigated Risk” come from admin configuration. In project settings, only four tabs drive the risk module: risk register, uncertainty classes, spread types, and calendar, with properties determining reporting on calendar versus fiscal year and other plumbing. The order recommended is registry set and calendar first, then prefixes, categories and types, then thresholds, uncertainty classes and basis code mapping, and spread types last, emphasizing completion before handing the project to control account managers to avoid re-ranking after changes.