Restricting blueprints within relations

Blueprints can be restricted so that a user only sees a certain part of that blueprint, dependent on the relation they are given. This affects what end users are able to tag their events with. 

Step-by-step guide

These restrictions are set up from the relations area of risr/advance.

1. The edit interface of a relation contains all the elements of that particular relation's hierarchy and structure. Against each element there is the option to set a blueprint.
   
   

   Open

   

   
   
   
   

2. Making a selection here will affect only the people who have this specific relation assigned to them. If nothing is selected (as is the default) then the user has visibility, and can tag, to the entirety of each blueprint as long as it has been set to be tag-able by end users.
   
   

3. Clicking the blueprint dropdown next to a relation element will display all the blueprints which have been defined in the system. Choosing one will allow you to select from a level of the hierarchy from which to limit.
   
   

4. When the end user is subsequently assigned this relation it will restrict their ability to select and/or tag against this blueprint to only the level to which you set here and below. 
   
   

5. The following example shows a curriculum blueprint which contains 3 different sub categories: General Curriculum, Respiratory and Cardiology. General Curriculum has been selected which means that when a user is assigned the relation of Training level - Level 1 they will only be able to tag against the General Curriculum area of the curriculum and Respiratory and Cardiology will be hidden to them.
   
   
   

   Open

   

Related articles