There is no current method to pass information from a custom portal into Displayr.  Nor is it possible to set individual page names in reports to auto-generate links, for example.

It _is_ possible to create a document where you hide the navigation pane on the left of the screen (see, e.g. https://help.displayr.com/hc/en-us/articles/4407685536655-Customizing-Online-Reports-Dashboards?source=search&auth_token=eyJhbGciOiJIUzI1NiJ9.eyJhY2NvdW50X2lkIjoxNTA0NTA4LCJ1c2VyX2lkIjozNjE4MjcyNjU3MTUsInRpY2tldF9pZCI6OTc0MjQsImNoYW5uZWxfaWQiOjYzLCJ0eXBlIjoiU0VBUkNIIiwiZXhwIjoxNjYyNTI3MzQ2fQ.uRB8UO4GmBRKkunVPw7jR0W3bNRhcpvs9rmbmhLicl8,

https://help.displayr.com/hc/en-us/articles/4407308692111-How-to-Hide-Buttons-in-the-Export-Menu-in-View-Mode?source=search&auth_token=eyJhbGciOiJIUzI1NiJ9.eyJhY2NvdW50X2lkIjoxNTA0NTA4LCJ1c2VyX2lkIjozNjE4MjcyNjU3MTUsInRpY2tldF9pZCI6OTc0MjQsImNoYW5uZWxfaWQiOjYzLCJ0eXBlIjoiU0VBUkNIIiwiZXhwIjoxNjYyNTI3MzQ2fQ.uRB8UO4GmBRKkunVPw7jR0W3bNRhcpvs9rmbmhLicl8,

https://help.displayr.com/hc/en-us/articles/360003334396-How-to-Remove-the-Header-Strip-in-View-Mode?source=search&auth_token=eyJhbGciOiJIUzI1NiJ9.eyJhY2NvdW50X2lkIjoxNTA0NTA4LCJ1c2VyX2lkIjozNjE4MjcyNjU3MTUsInRpY2tldF9pZCI6OTc0MjQsImNoYW5uZWxfaWQiOjYzLCJ0eXBlIjoiU0VBUkNIIiwiZXhwIjoxNjYyNTI3MzQ2fQ.uRB8UO4GmBRKkunVPw7jR0W3bNRhcpvs9rmbmhLicl8 using CSS.  Using this, you could prevent someone with access to a single report's individual page from navigating around other pages in the report, meaning that you could create a single document with lots of pages in it and then link to each of those pages from another location, _without_ those pages providing access to other pages in the same document.

However, the above method would entail creating links for each individual page in your document (so, 1,000 unique links).  You can, in Displayr, use something called QScript (though this is an Enterprise feature) which can be used to generate a list of the GUID's for each page in your document which you could then use to create links, but of course you would need to be sure that you're matching the right page's GUID to the right person.

I should also mention that a single document with 1,000 pages in it is likely to be fairly slow to run, so a better solution would be to create multiple smaller documents, perhaps one for each business unit or similar.  Using this method, you would still need to create 1,000 pages, one for each individual.

As it stands, the only way to create a report that's filtered on a specific person's access level is to use Displayr's built-in access management system which would entail inviting the document users to Displayr and letting them log in to their individual report.  The significant benefit here is, of course, that you can manage all this pretty easily.  First up, you would only need a single report with a single set of pages.  Secondly, you can bulk-import users to invite them to access the report/account so you don't need to do that individually.  This step would also create the user group for that individual (each person would need an individual user group) and add it automatically, and you can then, finally, just import the same list as a data set into your document (which can be set to auto-update if your list is accessible via url) and read the user group (using the QViewModeUserGroups function in an R-based filter).  In this scenario, you would only need to maintain a .csv file of users, with the only thing to do manually being to delete users who should no longer have access.

To avoid having to set up 1000+ documents with a different hidden set filter in each doc, user is looking for a way to pass the value of a filter inside a document’s URL. That would allow him to change the URL parameter for a single document rather than having to manage 1000+ documents.