Hi Reemali,

Try using the Microflow URL instead of the Page URL. This will allow you to implement custom logic within the microflow, such as restricting users based on their email ID or specific user accounts, to achieve the desired outcome.

Regards,

Sathish Kumar

Hi Reemali Patil

Since you don't want new roles, the best pattern is to control access inside the page itself using a Nanoflow/Microflow check on page load that validates if the current user is in your allowed list, and redirects them away if not show some message like unauthorized. This is easy and simple to do.

I hope this helps

This is how I implemented this capability:

A. Create entity AnonymousStatus

B. Create a page for anonymous users that has this entity on it

C. When the user clicks the top button, they get this page

D. Which uses this entity

E. After providing their email address and name in the popup window, the app checks the email address against a list of approved addresses and/or domains. If successful, the user receives a token via email.

F. On this page, they fill out their email address and token. Then this microflow validates their credentials

After successful validation, the AnonymousStatus object is updated to indicate they are validated.

One note: after validation, you should take the user to a separate page with the content you want them to see. Or if they don't validate, you can display a message indicating that.

Hope that gives you enough to get started.