Get started with iorad

Before your creators jump in and before onboarding sessions begin, there are a few foundational setup items that will make everything smoother—for you, your admins, and your creators.

This guide walks you through some of the essential configuration steps that help cement a clean, scalable environment from day one.

You’ll find:

• What needs to be setup 
• Why it matters
• How to do it (with tutorials of course!)
• Best-practice suggestions tailored to your use case 
• Linked tutorials and resources for each step 

This is your "ready to launch" checklist. 

💡For examples of specific use cases and to learn how others use the tool, check out our use cases hub here. 

Quick Start Checklist

Before inviting creators, complete the following:

✅ SSO configured and tested (if applicable)

✅ Custom brand theme created

✅ Team-wide tutorial settings selected and locked (optional but recommended)

✅ Initial categories and naming convention drafted (optional but recommended)

Purpose: Aligns tutorials with your internal brand look-and-feel, reinforces company identity, and improves end-user trust.

What you'll need: 

• Logo and favicon
• Brand colors
• Brand fonts

Process:

• Setup a Custom Theme for all of your Tutorials - walks through each step of the theme creation process. 
• Finalize and save

Best practices:

• To apply your theme to all existing tutorials, select and bulk apply the custom theme
• To ensure the theme is applied to all team tutorials moving forward, lock down the Theme setting via the Team Admin Lock Settings (More on this under Tutorial Template for Consistency)

Purpose: Ensures all tutorials created across the team have consistent settings, such as Layout, Theme, Privacy, etc.

Primary settings to consider locking down: 

• Default tutorial privacy (such as removing the "public" option
• Theme application
• Use of background music 

Process: 

• Team Admin Lock Settings - walks through how to lock or unlock certain settings across the team; includes tips on how to leverage these settings for a tutorial review process

Best practices: 

• Unless there is intent to have some tutorial content be made public, turn off the public option to avoid any accidental public tutorials
• Locking settings will lock for all tutorials created moving forward; to bulk apply settings to existing tutorials: 
  • Bulk Update Layout Options
  • Bulk Apply Custom Theme
  • Bulk Privacy Change 

Purpose: Sets up long-term scalability and prevents messy tutorial UI as you grow.

Decisions to make:

• Categories (functional area, product, workflow, region, etc.)
• Sub-categories (if needed)
• Naming convention for tutorials
• Optional tags

Steps to complete: 

1. Review how to organize tutorials in iorad and the difference between categories, subcategories, and tags
2. Determine how tutorials should be categorized (product, business unit, end learner/audience, etc.)
3. Draft a category, subcategory, and tag structure 
   1. We've created this blueprint to help think through and map your structure 
4. Create initial categories, subcategories, and tags
5. Share organizational process with team

Best practices: 

• Keep names short and clear
• Make categories broad, but not vague 
• Categories and tags are not permanent; you can rename, create new, and move tutorials around as needed 
• Consider implementing a tutorial naming convention to make identifying tutorials easier across the team: 
  • [Team] - How to X
  • [Product Area] - Creating Y
  • [Workflow] - Completing Z

Purpose: Make onboarding sessions less of a demo and more productive by ensuring your creators walk into a ready-to-use environment, have been given access to iorad, and have created at least one test tutorial to try it out.

Steps to complete: 

• Invite Creators to your Team 
• Have each creator make 1 tutorial (capture a simple process to practice) - this gets folks comfortable with iorad before we meet. 
• Schedule onboarding call 
  • We recommend an audience of approx. 10 creators per call to give folks time and space to ask questions. 
  • Feel free to schedule multiple calls to ensure everyone can join an onboarding call. 

Once everything above is set, complete a quick review:

• Branding looks correct 

• SSO tested

• Categories drafted and documented 

• All creators identified, invited, and confirm they have access

• First onboarding session scheduled