Skip to main content
All CollectionsGUIDEContent & modules
Reference guide: Annotations
Reference guide: Annotations

A reference guide for the annotations feature

Ben Robinson avatar
Written by Ben Robinson
Updated over a week ago

Description

“Annotations” are a CybSafe feature that allow administrators to add supplementary notes to CybSafe content. Annotations can offer extra information on aspects of security that are unique to individual organisations, while incorporating your organisations tone of voice.

Annotations help to reinforce organisational procedures and policies, and can also help relate CybSafe content to everyday security practices at your organisation. You can either add information alongside CybSafe advice with annotations or use this feature to replace CybSafe content with your own.

What does an annotation look like?

When an annotation is published, all users will be able to see it (assuming the annotation has not been restricted to individual groups only).

Published annotations will be displayed in a highlighted box with a CybSafe logo next to it, just like you can see in the example below:


Navigation

You can see an overview of all your published and un-published annotations here.

You can navigate to the annotations page in the admin menu by selecting: GUIDE > Learning > Module library tab > View annotations

On this page, you can see the title and content of the annotations along with which module it is in. It will also inform you who created an annotation, when it was created, as well as it's published status.

You can filter annotations by module and published status using the filters at the top of the page.

Recommendations

  • Link your annotations back to your internal site (eg. policies in Sharepoint). This way you don’t need to update the annotations if a policy is updated.

  • The internal Sharepoint site should always circle back to recommending CybSafe content with a link if possible (eg. reporting phishing emails > Spear Phishing module)

  • Repeating information is key- don’t be afraid to annotate the same point multiple times if a module has a few pages with relevant information

  • Make the modules feel your organisation, inject your tone of voice to allow users to resonate more

  • Remember the same module can be annotated per group, reducing admin workload. Create create annotations/replace content in one place, then tweak to meet individual requirements. For example, perhaps reporting IT issues is different in APAC to the EU

  • Content can be replaced completely if it does not match the internal organisation guidance/policies. Itʼs worth checking that the information being replaced isnʼt something that will be tested in the Knowledge Check - [email protected] can help sense check this


Additional resources


Did this answer your question?