1. Help Centre
  2. Using PebblePad
  3. Blocks & Properties

Shared block properties

Content blocks share many common properties. They can each be adjusted to change how a block is viewed and completed by a user, including role restriction. 





Custom properties are listed on the individual block's guide.




In-field hints


A hint is the description text used to instruct or guide users.  By default, the hint appears below the block’s title, where the text can be formatted.


Enabling in-field hints will place the text within the response field to help condense the page. Here the text cannot be formatted, and any customisation will be removed when activated.







Hints on asset view


A block is visible to all roles in all versions of the asset. Unticking this option will remove hint fields when the asset is viewed by assessors in ATLAS, or when in its published state - e.g. shared with people or the web.





Useful when: instruction is needed to guide learners, but can be hidden from assessors to shorten or tidy a page.







Show empty fields in view


By default, a block is always visible to all roles in all versions of the asset, even when a response has not yet provided. Unticking this option will remove an empty block from view to an assessor in ATLAS, or when shared with people or the web.





Useful when: an assessor should only see completed fields.







Include evidence


In addition to providing a response within the block, enabling activates the Add evidence button. Learners will be able to attach evidence from their assets.





Enabling evidence does not activate mapping or approvals, which are exclusive to capability blocks.







Role restriction


Role restriction specifies who is able to complete the block - either a learner or assessor. One content block cannot be completed by both roles.



No restriction

This is the default option. It sets the block to be completed by a learner, who must open the asset from their Asset Store in Pebble+. Their response will appear as read-only to an assessor in ATLAS.





Any assessor can complete

This sets the block to be completed by any assessor role (including Externals if granted permission), who must open the asset from the ATLAS workspace. Their response will appear as read-only to a learner in Pebble+.





Specify which assessor roles can complete

This sets the block to be completed by specific assessor roles, who must open the asset from the ATLAS workspace. Their response will appear as read-only to a learner in Pebble+.




The assessor field label can be customised by clicking on the text and retyping.







Privacy state


As a template or workbook may contain a variety of information, it's feasible the overall asset can be shared but allow privacy to be retained on individual blocks.



Not private

A block is visible to all roles in all versions of the asset.




Allow user to mark as private

Allows the learner the option to mark their response as private. If they do the block will be:


  • hidden to assessors when viewed in ATLAS, 
  • hidden when shared with people or the web.





User completes, assessor can view (confidential)

The option marks the learner's response as confidential and means the block will be:


  • shown to assessors when viewed in ATLAS - and marked as confidential 
  • hidden when shared with people or the web.








Mandatory for progress


This works in conjunction with progress tracking for workbooks, which itself must be enabled to operate correctly. 


When Mandatory for progress is ticked, the learner is unable to mark the page as complete until a response has been added to this specific block.





This option does not prevent the learner from saving or sharing the asset in any way.






Duplicate block


Make an exact duplicate copy of a block on the same page, along with matching title, hint text and properties.





A block cannot be saved individually or copied to another page.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article