RoboKind Central Organizational Structure Considerations & Itinerancy Support

Example of a Simple/Flat Organization Structure:

In this model, all teachers, students, facilitators, and robots are added at the same root organization level. This is the simplest structure to plan and implement, but for large numbers of students, classrooms and robots, this structure may not meet an organizations needs.

Example of a Multi-Tiered Organization Structure:

In this example, the organization has been structured according to a hypothetical need to organize into districts and schools, which can each have their own user accounts, students, classrooms, and teachers/facilitators.

Considerations for a Multi-Tiered Organization:

• See RoboKind Central Role Permissionswhen planning which security levels to assign to user accounts being created.

• Usually there will be one or two administrator accounts at the top level of the organization.

• User accounts who should be only able to manage a specific child organization would often be created as manager level accounts within the organization in question.

• When adding Users/Students/Classrooms to a child organization, be sure to use the context menu and “Create new child” menu under the desired organization; the Add New button under Quick Actions is only for objects to be added at the top level of the organization.

  

Classroom Considerations:

• Classrooms organize students into groups for teaching.

  • Students who are not in a classroom will not be able to be selected in order to start a lesson.

  • In cases where the concept of classrooms does not seem to apply to the situation, we recommend creating the classrooms according to how you would like to see the data grouped together for reporting purposes, for example a teacher might group their students into one classroom.

• A common missed point when configuring accounts is the step of adding facilitators to a classroom; be sure to check the Facilitators tab when configuring a classroom, where you can select a teacher, click Add to Classroom, and then Save Classroom. If the facilitator to be assigned to the classroom is in a different child organization, then toggle the “all” button to be able to add facilitators from other levels of the organization to the selected classroom.

  

Robot Considerations:

• By default, robots are available to teachers in the same root or child organization as the robot.

• In cases where a robot is temporarily unavailable, the RoboKind Companion app also supports teaching lessons in Avatar mode.

• If one educator/facilitator has the companion app open and connected to a robot, then that robot will not be visible to other teachers until that connection is closed.

• It is highly recommended that friendly & useful aliases be assigned to each robot, and that robots also be physically labeled with that name. This will make it easier for educators to quickly identify the correct robot for lessons.

Itinerancy Considerations:

• In cases where educators/therapists are itinerant (i.e. traveling and assisting students at multiple campuses), then there are multiple ways in which this can be managed.

  • Some teachers might have a robot with a traveling case, and they might bring the robot with them when visiting alternate campuses. In this case, the robot, itinerant teacher, and students all could be grouped under a single child organization.

  • In cases where each location has on site staff that works with RoboKind in addition to itinerant educators/therapists who might travel between campuses, then RoboKind Central allows the account to be structured according to the physical locations, and then robot and user settings can be adjusted for the robots & users who might sometimes be exceptions to that structure.

Changing Robot Availability Settings:

• Use the RoboKind Central Organization List to view/edit properties for Robots & Avatars.

• Choose View/Edit on the robot in question.

  

• Adjust the Robot Accessibility field according to the following matrix:

  

Changing User Availability Settings:

• Use the RoboKind Central Organization List to view/edit properties for Facilitators.

• Choose View/Edit on the facilitator in question.

  

• Adjust the Robot Accessibility field for the facilitator according to the following matrix: