3da4a37231e4a0a1eed0e7492d9a5e0f7f6f1e40
FAQ/Questions/Applying-Security-to-Scheduled-Reports.md
| ... | ... | @@ -37,4 +37,9 @@ End Sub 'end method |
| 37 | 37 | |
| 38 | 38 | ##Limitations |
| 39 | 39 | |
| 40 | -The Email Scheduler in the reporting system does not have a way to provide authentication (login & password) to your SMTP server. For the email scheduler to send messages to an SMTP server, you would need to provide an open path via the web server's IP address to the SMTP server that would not require authentication. |
|
| ... | ... | \ No newline at end of file |
| 0 | +The Email Scheduler in the reporting system does not have a way to provide authentication (login & password) to your SMTP server. For the email scheduler to send messages to an SMTP server, you would need to provide an open path via the web server's IP address to the SMTP server that would not require authentication. |
|
| 1 | + |
|
| 2 | + |
|
| 3 | +##Per-user Security On Scheduled Reports |
|
| 4 | + |
|
| 5 | +Scheduled reports only supports per-user security using the Link format. Scheduled attachments will not apply hidden filters normally, but you can apply security through [[PreExecuteReportSet()|/FAQ/PreExecuteReportSet]] based on the security of the report owner. If per-user security is required, the Link format will require the user to login before seeing the report. |
|
| ... | ... | \ No newline at end of file |