Changes in 733a406: Updated Security (markdown)

				Integration/Tutorials/Security.md
			
          @@ -6,13 +6,13 @@ Izenda Reports fully integrates with the security of existing ASP.NET applicatio

           Type of security|Example|Implementation Details

           ----------------|-------|----------------------

          -[Login](#Login-Security) |Users must login before gaining access to reports.|[[RequireLogin]] [[CurrentUserName]] [[CurrentUserIsAdmin]] [[Your Login Page Integration]]

          -[Data Sources](#Data-Sources)|A specific user can only see certain data sources.|[[RequireLogin]] [[Basic Report Sharing]] [[VisibleDataSource]] [[Database Security]]

          -[User Driven Report Sharing](#User-Driven-Report-Sharing)|A user can save a report and decide if they want other users to see this report. They can also mark a report read-only meaning it can be viewed but not saved over.|[[Basic Report Sharing]] [[CurrentUserIsAdmin]] [[ReportsPath]] [[Read-Only & Shared Checkboxes]]

          -[Custom Report Control](#Custom-Report-Control)|Different departments can see different base reports.|[[VisibleDataSources hides reports for non-accessible datasources]] [[ReportsList may be overridden]] [[Storing Reports]] [[ReportsPath]]

          -[Overwriting and Deleting Reports](#Overwriting-and-Deleting-Reports)|Users can load shared or base reports, but should not be able to delete them or overwrite them.|[[AllowOverwritingReports]] [[AllowDeletingReports]] [[CurrentUserIsAdmin]]

          -[Altering Capabilities by Role](#Altering-Capabilities-by-Role)|Only power users should see the modify report button on the report viewer. Others will only access the report viewer.|[[ShowDesignLinks]] [[ShowModifyButton]] [[AllowOverwritingReports]] [[ShowAdminButton]]

          -[Field/Record or Tenant Level Security](#Field/Record-or-Tenant-Level-Security)|Salespeople look at the same report but see different data based on their territory and credentials. In a multi-tenant environment, reports and data for each customer, group, or tenant should be isolated.|[[PreExecuteReportSet - Hidden Filters]] [[ProcessEqualsSelectList]] [[Field & Record Level Security]]

          +[Login](#Login-Security) |Users must login before gaining access to reports.|[[RequireLogin]] <br> [[CurrentUserName]] <br> [[CurrentUserIsAdmin]] <br> [[Your Login Page Integration]]

          +[Data Sources](#Data-Sources)|A specific user can only see certain data sources.|[[RequireLogin]] <br> [[Basic Report Sharing]] <br> [[VisibleDataSource]] <br> [[Database Security]]

          +[User Driven Report Sharing](#User-Driven-Report-Sharing)|A user can save a report and decide if they want other users to see this report. They can also mark a report read-only meaning it can be viewed but not saved over.|[[Basic Report Sharing]] <br> [[CurrentUserIsAdmin]] <br> [[ReportsPath]] <br> [[Read-Only & Shared Checkboxes]]

          +[Custom Report Control](#Custom-Report-Control)|Different departments can see different base reports.|[[VisibleDataSources hides reports for non-accessible datasources]] <br>[[ReportsList may be overridden]] <br>[[Storing Reports]]<br> [[ReportsPath]]

          +[Overwriting and Deleting Reports](#Overwriting-and-Deleting-Reports)|Users can load shared or base reports, but should not be able to delete them or overwrite them.|[[AllowOverwritingReports]] <br>[[AllowDeletingReports]] <br>[[CurrentUserIsAdmin]]<br>

          +[Altering Capabilities by Role](#Altering-Capabilities-by-Role)|Only power users should see the modify report button on the report viewer. Others will only access the report viewer.|[[ShowDesignLinks]] [[ShowModifyButton]]<br> [[AllowOverwritingReports]] [[ShowAdminButton]]

          +[Field/Record or Tenant Level Security](#Field/Record-or-Tenant-Level-Security)|Salespeople look at the same report but see different data based on their territory and credentials. In a multi-tenant environment, reports and data for each customer, group, or tenant should be isolated.|[[PreExecuteReportSet - Hidden Filters]] <br>[[ProcessEqualsSelectList]] <br>[[Field & Record Level Security]]

           ###Login Security

...	...	@@ -6,13 +6,13 @@ Izenda Reports fully integrates with the security of existing ASP.NET applicatio
6	6
7	7	Type of security\|Example\|Implementation Details
8	8	----------------\|-------\|----------------------
9		-[Login](#Login-Security) \|Users must login before gaining access to reports.\|[[RequireLogin]] [[CurrentUserName]] [[CurrentUserIsAdmin]] [[Your Login Page Integration]]
10		-[Data Sources](#Data-Sources)\|A specific user can only see certain data sources.\|[[RequireLogin]] [[Basic Report Sharing]] [[VisibleDataSource]] [[Database Security]]
11		-[User Driven Report Sharing](#User-Driven-Report-Sharing)\|A user can save a report and decide if they want other users to see this report. They can also mark a report read-only meaning it can be viewed but not saved over.\|[[Basic Report Sharing]] [[CurrentUserIsAdmin]] [[ReportsPath]] [[Read-Only & Shared Checkboxes]]
12		-[Custom Report Control](#Custom-Report-Control)\|Different departments can see different base reports.\|[[VisibleDataSources hides reports for non-accessible datasources]] [[ReportsList may be overridden]] [[Storing Reports]] [[ReportsPath]]
13		-[Overwriting and Deleting Reports](#Overwriting-and-Deleting-Reports)\|Users can load shared or base reports, but should not be able to delete them or overwrite them.\|[[AllowOverwritingReports]] [[AllowDeletingReports]] [[CurrentUserIsAdmin]]
14		-[Altering Capabilities by Role](#Altering-Capabilities-by-Role)\|Only power users should see the modify report button on the report viewer. Others will only access the report viewer.\|[[ShowDesignLinks]] [[ShowModifyButton]] [[AllowOverwritingReports]] [[ShowAdminButton]]
15		-[Field/Record or Tenant Level Security](#Field/Record-or-Tenant-Level-Security)\|Salespeople look at the same report but see different data based on their territory and credentials. In a multi-tenant environment, reports and data for each customer, group, or tenant should be isolated.\|[[PreExecuteReportSet - Hidden Filters]] [[ProcessEqualsSelectList]] [[Field & Record Level Security]]
	9	+[Login](#Login-Security) \|Users must login before gaining access to reports.\|[[RequireLogin]] <br> [[CurrentUserName]] <br> [[CurrentUserIsAdmin]] <br> [[Your Login Page Integration]]
	10	+[Data Sources](#Data-Sources)\|A specific user can only see certain data sources.\|[[RequireLogin]] <br> [[Basic Report Sharing]] <br> [[VisibleDataSource]] <br> [[Database Security]]
	11	+[User Driven Report Sharing](#User-Driven-Report-Sharing)\|A user can save a report and decide if they want other users to see this report. They can also mark a report read-only meaning it can be viewed but not saved over.\|[[Basic Report Sharing]] <br> [[CurrentUserIsAdmin]] <br> [[ReportsPath]] <br> [[Read-Only & Shared Checkboxes]]
	12	+[Custom Report Control](#Custom-Report-Control)\|Different departments can see different base reports.\|[[VisibleDataSources hides reports for non-accessible datasources]] <br>[[ReportsList may be overridden]] <br>[[Storing Reports]]<br> [[ReportsPath]]
	13	+[Overwriting and Deleting Reports](#Overwriting-and-Deleting-Reports)\|Users can load shared or base reports, but should not be able to delete them or overwrite them.\|[[AllowOverwritingReports]] <br>[[AllowDeletingReports]] <br>[[CurrentUserIsAdmin]]<br>
	14	+[Altering Capabilities by Role](#Altering-Capabilities-by-Role)\|Only power users should see the modify report button on the report viewer. Others will only access the report viewer.\|[[ShowDesignLinks]] [[ShowModifyButton]]<br> [[AllowOverwritingReports]] [[ShowAdminButton]]
	15	+[Field/Record or Tenant Level Security](#Field/Record-or-Tenant-Level-Security)\|Salespeople look at the same report but see different data based on their territory and credentials. In a multi-tenant environment, reports and data for each customer, group, or tenant should be isolated.\|[[PreExecuteReportSet - Hidden Filters]] <br>[[ProcessEqualsSelectList]] <br>[[Field & Record Level Security]]
16	16
17	17	###Login Security
18	18