# data[].attributes.headline
When grading games in impact, is there a checklist for what things need to be on the game?

# data[].attributes.subject
When grading games in impact, is there a checklist for what things need to be on the game?

# data[].attributes.body
By the time the project gets to you in the Sensei Portal, it has already passed the automatic validation. Therefore, you do not have to look specifically for the code requirements and check it against that level. However, we do recommend that you play the game to make sure it makes sense, and is not just putting the minimum required code blocks to pass auto-validation. The check list is in the Sensei Grading portal, and we ask that Senseis do check the game for creativity and a project that has a beginning, middle, and end. In the Sensei Portal, there is a list of main concepts and general tips that Senseis might use to guide a ninja as they're working on an adventure. I also recommend checking out the IMPACT training on Absorb as it covers Sensei Reviews in a much more detailed way.

# data[].attributes.headline
Where can I find solutions for Build and Solve activities?

# data[].attributes.subject
Where can I find solutions for Build and Solve activities?

# data[].attributes.body
The Sensei Portal has solutions for Build and Solve activities along with guiding questions and pro tips. Senseis will use the Support section to pull up the appropriate resources to support the ninja. The solutions for Build and Solve activities are for the Sensei to view while supporting the ninja, and not to be provided to ninjas as an “answer key” . Ninjas may have slight variations in code parameters.

# data[].attributes.body
The magic word for reset progress button: awesomeninja

# data[].attributes.headline
The gray color is showing up as black in the Pixel Art Editor

# data[].attributes.subject
The gray color is showing up as black in the Pixel Art Editor

# data[].attributes.body
The default transparent color shows up as "gray" but is actually transparent. If a ninja would like to use gray, there are several purple shades that can act as gray.

# data[].attributes.body
IMPACT MVP and Phase 2 Features.pdf

# data[].attributes.body
Currently, the only way to view submitted projects is for the Sensei to pull them up from the Sensei Portal. Ninjas will be able to show and share projects in future releases.

# data[].attributes.headline
If a Sensei is already in My Studio, How can they get Sensei Portal access?

# data[].attributes.subject
If a Sensei is already in My Studio, How can they get Sensei Portal access?

# data[].attributes.body
If a user is already in MyStudio, they have to be removed and readded. They will be able to keep their passwords and data.

# data[].attributes.body
Currently, a personnel (e.g. sensei, CD, owner) can only be assigned to one center for IMPACT.  IMPACT only allows a account to see one center's ninja projects. They would have to log in to a different Sensei Account to view the other center's ninja projects.

Each unique login (email address) is assigned to one specific center in IMPACT at this time. If an email account is added in MS for multiple centers, then the first center that the email gets added to, that's the center the account will be able to view.

Work Around: If you add a "+1" before the "@" on a gmail account, it goes to the same email but is recognized as a different account. ex: craig+1@gmail.com

# data[].attributes.body
Since My Studio has a 10 account limit, we do recommend that if you have more than that amount on staff, one account is created as a "center sensei" account which can be shared by multiple senseis. They can each log in to IMPACT on their own devices to the same account.

# data[].attributes.headline
After checking a ninja in, Ninjas are not able to log into IMPACT!

# data[].attributes.subject
After checking a ninja in, Ninjas are not able to log into IMPACT!

# data[].attributes.body
There is sometimes a very slight delay (no more than 10 seconds) between checking in and IMPACT access activating. Refresh, clear the cache, and try logging in again.

# data[].attributes.body
Delete their usernames on MyStudio, then re-add them and recheck them in.

# data[].attributes.headline
View the "Getting ready for Launch" IMPACT Short on WP or the Sensei Discord Channel!

# data[].attributes.subject
View the "Getting ready for Launch" IMPACT Short on WP or the Sensei Discord Channel!

# data[].attributes.body
GDP to IMPACT Transition Plan.pdf

# data[].attributes.body
MyStudio Instructions.pdf

# data[].attributes.body
IMPACT Tracker.xlsx

# data[].attributes.headline
Why isn't the Solve activity letting me pass?

# data[].attributes.subject
Why isn't the Solve activity letting me pass?

# data[].attributes.body
Restart the activity (top right corner) so that the correct starter code loads. Make sure to read the instructions carefully and change only the code that fixes the bug specified. Remind the ninja to check the hint. Any other unnecessary adjustments will lead the code to be incorrect.

# data[].attributes.body
https://padlet.com/cn_edu/IMPACT

# data[].attributes.body
Code Ninjas CS Standards Alignment.pdf

# data[].attributes.body
White Belt Planning Documents.pdf

# data[].attributes.body
WB Progress Tracking Sheet.pdf

# data[].attributes.headline
When fixing issues in the Build Activity can you fix and check an issue one at a time without any consequences to your path through the level? Or does the ninja need to fix all requirements all at once and then submit for a Code Check?

# data[].attributes.subject
When fixing issues in the Build Activity can you fix and check an issue one at a time without any consequences to your path through the level? Or does the ninja need to fix all requirements all at once and then submit for a Code Check?

# data[].attributes.body
After the first time ninjas click "submit", the "check code" button will be enabled. Ninjas can fix and check an issue one at a time without any consequences by clicking "check code".

# data[].attributes.headline
Will ninjas be limited to how many times they can try to "test out" of a section?  I worry about ninjas just doing it over and over and hoping that they eventually get it right vs just moving on to the other sections of the curriculum

# data[].attributes.subject
Will ninjas be limited to how many times they can try to "test out" of a section?  I worry about ninjas just doing it over and over and hoping that they eventually get it right vs just moving on to the other sections of the curriculum

# data[].attributes.body
Ninjas will have 2 chances to pass the Quest, after which they will be directed to the learn it path. Please view the Absorb training modules for more detailed information about the personalized learning paths.

# data[].attributes.headline
Are the Explore activities tightly coupled to the Build requirements that were not solved correctly? Or will the Explore activities cover both requirements they handled correctly and those they did not?

# data[].attributes.subject
Are the Explore activities tightly coupled to the Build requirements that were not solved correctly? Or will the Explore activities cover both requirements they handled correctly and those they did not?

# data[].attributes.body
Explore activities cover the requirements most important to the Build, which may include those that the Ninja handled correctly and incorrectly.

# data[].attributes.headline
Is there some kind of push notification for a ninja when an adventure project has been graded?

# data[].attributes.subject
Is there some kind of push notification for a ninja when an adventure project has been graded?

# data[].attributes.body
No, at launch, the ninja will be able to see that their adventure project has been graded in "Messages". A Pop up notification is in the list for future features. However, we also highly encourage the Code Sensei to personally notify the ninja once an Adventure project has been graded, to provide an opportunity to connect and guide.

# data[].attributes.headline
Is there an admin override for the lockout the Quest for either a given level or for the entire belt in case a Sensei or CD believes the platform incorrectly failed the ninjas Quest attempt(s)?

# data[].attributes.subject
Is there an admin override for the lockout the Quest for either a given level or for the entire belt in case a Sensei or CD believes the platform incorrectly failed the ninjas Quest attempt(s)?

# data[].attributes.body
There is not. If a Sensei or CD believes the platform incorrectly failed (has an error in code validation), a ZenDesk ticket needs to be submitted to describe the circumstances of the bug. Select "IMPACT Bugs," then "Report a Bug" so that any errors can be fixed system wide.

# data[].attributes.body
https://codeninjas.myabsorb.com/#/catalog/416be4ee-d03a-49fc-bac2-302fdb2cb456

# data[].attributes.body
All curriculum and processes remain unchanged. Unity belt projects will be submitted through the dojo.

# data[].attributes.headline
How long is the Absorb Training? Does it cover all the belts?

# data[].attributes.subject
How long is the Absorb Training? Does it cover all the belts?

# data[].attributes.body
The Absorb training will take no more than one hour total.

The training covers the IMPACT Tool and Curriculum, and does not go into the content of each individual belt.

Unlike the existing curriculum, the new curriculum does not require Senseis to have completed every single activity in order to assist ninjas. As long as they have completed the training modules on Absorb, and understand how to use the platform tools, they will be able to support ninjas on IMPACT. We on the education team encourage the process of "learning alongside the kids".

# data[].attributes.body
IMPACT Sensei Reference Sheet.pdf

# data[].attributes.body
Before reporting a bug, please do the following:

- Clear cache and refresh (we are constantly updating IMPACT and these updates may cause small loading errors).
- Try on an incognito tab.
- View the platform in full screen by pressing F11.
- look at all of the available resources linked in this Padlet to find similar issues.
- Check the IMPACT known issues Padlet for already reported bugs and possible temporary workaround solutions

If the issue is not answered, ask on the Sensei Discord or Work Place about a certain issue. If it is a bug, a Home Office representative will ask you to submit a ZenDesk ticket.

- Bugs should be reported via ZenDesk.
- Select IMPACT Bugs for platform bugs. Include as much information as possible, including ninja username, center location, screenshots of issue, and attempted solutions.
- Select IMPACT Curriculum Errors for curriculum bugs. Include as much information as possible, including the level, activity type, and step.