Hello, I'm tasked with filtering sales report data based on the user requesting the report. Certain internal people (who have access to the report) will have access to all sales data, meaning no filtering needs to take place. Regional sales managers will have access to all sales data for customers within their region. Customers themselves will be able to log into our portal and get sales reports for sales to that customer only. Now where in the world do I start? Should we have a separate report server instance for customer reporting, and should a separate customer report be created for this site? I assume I'd need a table of [customer] logins and the customer ID values for which they're authorized to view sales records, and this table would be joined in the original sales query. Should the login value be passed as an invisible parameter to the stored procedure? My boss--who has lots of ideas how reports should work but little working knowledge of SSRS--assumes one report should be able to handle all three levels of filtering, but I'm concerned that we're skipping over important considerations, like whether or not customers should ever be accessing the same Report Manager instance as internal users are accessing. In fact, the list of customer reports is very short; probably less than 3 for the first year, whereas the initial list of internal reports starts at over 30. Thanks, Eric

its possible accomplish this with one report. One way is to use the user id variable and check it against a user group table.

Thanks, Nehemiah. I'll give that a try. I was hoping to get more advice from more people. Are dynamically-filtered reports very rare?