Assigning Report Viewers at Runtime

There are three settings in the report definition that determine how web reports are distributed at runtime:

Report Viewer List on the report definition security page.
Assign users and roles allowed to view the reports regardless of whether the report is bursted or not.
Security Join Table on the report definition bursting page.
Assign users that can view individual bursted report files based on security join tables. These users are combined with the users and roles defined on the security page.

Note: When security join tables are used, and the Allow viewer ID assignment at report runtime check box is selected, any users, roles or email addresses added at runtime will see all bursted reports. If roles or users are defined on the security page or at runtime, they can view all bursted reports ignoring the security join table.
Allow viewer ID assignment at report runtime check box on the report definition page.
Allows the users running the report the ability to modify (add or remove) additional roles, users or email addresses on the runtime report distribution page.

This table describes how viewers are selected for non-bursted reports based on the report definition security settings.

Report viewers assigned	Allow viewer ID assignment at report runtime	Viewers
Yes	No	Reports are distributed to all roles and users defined on the security page. Runtime overrides are not allowed.
Yes	Yes	Reports distributed to all users and roles defined on the security page. Runtime overrides are allowed.
No	Yes	Distribution list is assigned at runtime on the Process Scheduler distribution detail page. By default the requester is added.
No	No	No reports posted to Report Repository. Runtime overrides are not allowed.

This table describes how viewers are selected for bursted reports based on the combination report definition settings.

Report viewers assigned	Security join table implemented	Allow viewer ID assignment at report runtime	Viewers
Yes	No	No	All bursted reports are distributed to all roles and users defined on the security page. Runtime overrides are not allowed.
Yes	Yes	No	All users and roles defined on the security page will see all bursted reports. Users defined from the security join table will see only the bursted reports based on their join criteria. Runtime overrides are not allowed.
Yes	Yes	Yes	All users and roles identified at runtime will see all bursted reports. Users defined from the security join table will see only the bursted reports based on their join criteria. Runtime overrides are allowed. Any users, roles or email addresses entered on the Process Scheduler distribution detail page will see all bursted reports.
Yes	No	Yes	All bursted reports are distributed to all roles and users defined on the security page. All users, roles or email addresses identified at runtime will see all bursted reports. Runtime overrides are allowed
No	Yes	No	Users defined from the security join table will see only the bursted reports based on their join criteria. Runtime overrides are not allowed.
No	No	Yes	Assign distribution at runtime. By default requester is added. Any users, roles or email addresses entered on the Process Scheduler distribution detail page will see all bursted reports.
No	Yes	Yes	All users and roles identified at runtime will see all bursted reports. Runtime overrides are allowed. Users defined from the security join table will see only the bursted reports based on their join criteria.
No	No	No	No reports posted to Report Repository. Runtime overrides are not allowed.