Hey Daniel James, I believe currently Hosted content requires some specific HTML structure / link to be passed to secure it. If you don't have such specific pattern and if its prone to be changing, you can assign data-ms-content attribute to gate the video elements or any element on the page which you don't want users to access based on the plan they are assigned.
And along with that you can keep such content hidden by default and add this data-ms-bind:style="display:block" custom attribute to it. So essentially, the relevant elements are hidden already and when Memberstack loads, it checks whether the user definitely has permission to such element and only then displays it. You can use this approach if you are not handling with sensitive info and just want to gate access to the elements.
Here's a guide on the use of such style based custom attribute. Does this help your use-case?
Comments
1 comment
Hey Daniel James, I believe currently Hosted content requires some specific HTML structure / link to be passed to secure it. If you don't have such specific pattern and if its prone to be changing, you can assign data-ms-content attribute to gate the video elements or any element on the page which you don't want users to access based on the plan they are assigned.
And along with that you can keep such content hidden by default and add this data-ms-bind:style="display:block" custom attribute to it. So essentially, the relevant elements are hidden already and when Memberstack loads, it checks whether the user definitely has permission to such element and only then displays it. You can use this approach if you are not handling with sensitive info and just want to gate access to the elements.
Here's a guide on the use of such style based custom attribute. Does this help your use-case?
Please sign in to leave a comment.