Protected Tables in the ReportWriter

To comply with legal restrictions on accessing medical data, all of the "medical" tables are protected by a special level of security in the ReportWriter.  All medical tables (all tables containing student medical data) cannot be accessed normally in ReportWriter.  Special access must be granted.

Access to these tables is protected this way specifically to comply with legal restrictions and such access requires multiple individual actions to grant any user access to the protected tables.

Granting ReportWriter Access to Protected Tables

 There is a special "ReportWriter Security" setting about 3/4 of the way down the Setup->Security->Policy screen: 

The default, as shown, is not to grant any access to these tables:  Specific actions have to be taken to grant access:

1. Optionally create a Role specitically to grant access to the protected tables.
2. Assign the Role to the users who be developing the ReportWriter reports accessing the protected tables.
3. Go to the Setup->Security->Policy screen and assign that Role in the "Report Writer Security" parameter:

Only a single Role can be granted this action:  the Report Writer Security parameter only accepts a single Role.   Any user who needs the access should be granted that Role.

System Administrator Access

It is possible, but not preferrable, to grant this access to the sysadmin Role:

Without this specific granting of access, even users with the sysadmin (system administration) Role cannot access the protected tables.  That is: users with the sysadmin Role do not have automatic access to the protected tables:  they need to be assigned a Role which does grant access, or - again not preferably - the sysadmin roles can be the Role granted the access.

Creating a "Access to Protected Tables" Role

If you create a special Role in order to grant access to the protected tables, which we recommend doing, the Securable Locations it includes are actually not important:

The sample Role shown here includes access to the ReportWriter module tabs - but what is important is simply that the Role is used a tool to grant the access to the protected tables.

It's better (legally), to create a special Role just for granting access to the protected tables and to give users who need to write these reports that Role. (In other words, don't use sysadmin - preferably).