Hi Alena! Depending on your use case this might be possible but probably wont be the most secure.

Here are the steps that I’m thinking might work for you:

1. Enable custom branding on the panorama
   1. This custom branding (logo, colors, etc) will apply to any TI hosted page when viewed as a learner in that panorama
   2. This will also allow you to separate the dashboard and landing page from the main
2. Create the desired page(s) in your main instance
   1. To restrict access to this page as much as possible you can:
      1. Limit to only logged in users
      2. Only put link to page on the custom learner dashboard for your panorama (doesn’t block other people from accessing but does reduce the likelyhood of unintended people finding it)
      3. If there is any content that only people in this panorama will have access to, then you might be able to use that as prerequisite content for this page (the newly released auto-assignment rules might help with this)
      4. If you are hoping to use these pages as catalogs, you can set the catalogs to only display content the user has access to
3. Publish page
4. Share link to page to desired groups (visibility of button or link limited to the custom learner dashboard or email to group

None of this guarantees that only this panorama will have access to this page though so it is still kind of a cross your fingers moment. I’m interested to see if other people have processes that have worked for them!

If you ​@Alena follow the above then a Learner would have to know the specific URL to get to a page not intended for them.  In nearly 7 years, I have yet to see people even recognize that the URL reads /pages and not /learn for custom pages so no worries or even odds.  Pages are just all in one repository and you create the nav to get their in your Learner Dashboard.  Hope this helps.

Thank you so much for your help. It is exactly what I was looking for!

Thank you,

Alena