Importing and publishing

Importing an assessment

Import copies the whole assessment into your account — its sections, its questions and their settings — as a new draft you own.

It is a copy, not a link. Editing your version never affects the original, and updates to the library original never reach your copy. That is what makes it safe to change, and it means an imported assessment does not silently shift under a funnel that is already running.

It arrives as a draft on purpose: review it before anyone sits it. Check the question set matches the role, the time limit suits your process, and — for code questions — that you agree with the test cases. See Creating assessments.

An assessment can only be imported once per company. A second attempt is refused, because the common cause is two people importing the same thing without realising, and ending up with two diverging copies of one assessment is worse than the mild annoyance of being told no. If you genuinely want a second variant, duplicate the copy you already have.

Importing a question

Two ways:

• Into your question bank, where it becomes an ordinary question available to any assessment.
• Straight into an existing draft assessment, from the question's card in the library.

The second only offers draft assessments as targets. Adding a question to an assessment candidates are already sitting would change the assessment mid-funnel, so published assessments are not offered.

A question already present in the target assessment is refused rather than duplicated.

Tier refusals

If an item is above your plan's tier, the import is refused and the card shows which plan unlocks it. Professional and above removes the restriction entirely — see The Library.

Publishing your own

You can publish your own assessments and questions to your company library, making them available to your colleagues. Unpublishing removes them again.

This is worth doing deliberately rather than by default. A shared library is only useful if what is in it is trusted — five maintained assessments beat forty that nobody is sure about, and an assessment published while still half-written will be used by someone in a hurry.

Before publishing, check the same things you would check on an import: the questions are correct, the code questions have been previewed, and the description says what role it is for.

Publishing to the public library is not open to customers. The public catalogue is written and maintained by Test Utopia; your published content stays within your own company.

Tracking

Imports are recorded, which is what drives the Most Cloned sort in the library. It is a signal about what other teams found useful, not a quality ranking — popular material is popular partly because it is broadly applicable, which is not the same as being right for your role.