You have at least three complex and independent entities: Student, University, Hostel.
Even if the database isn't empty, there are cases when some university or hostel isn't registered yet. And you'll face an issue again.
My suggestion is to allow creation of the entities "on the fly", when admin fills the Student form. So, the main flow is Student ...
If you have to get users to create an account when they check out then I would recommend:
reducing the data needed to create an account to a minimum (email and password)
being honest about it
So first screen you can set the scene
# You must create an account first
You have to create an account because of x and y.
Then the next screen can be ...
Placing the login modal after the user clicks Play is going to be very irritating to your users for a few reasons:
It interrupts the flow of what they're intending to do (nobody likes this)
It breaks the pattern that they're used to seeing on other video sites, where the user is informed that authentication is necessary before they engage with the video
I don't know if there's a best practice; for a 'reset password' form, best practice from a security perspective is not letting the user know whether the email address actually exists, i.e. something along the lines of "If an account with this email address exists, you'll receive an email with the reset link."
You could do it the way this site does ...
We've been experiencing some complains about some will mistype their email AND create a new account and not understand why they were not seeing their information in their User home.
I don't think you should let them create am account without validating the email (or at least you should have an internal differentiation between "good" emails and ...
Assuming you have a public website, there are following important points:
Sign up should be as easy as a button click and focus should be to introduce user to website features asap.
Allowing only Humans should be a priority.
You need to remember Users for further personalized communication(like feedback, offers etc.) even if they used the app one time. So ...
Is there a problem adding the message in the first screen together with the play button?
The play button can be visible but disabled, if the user click on it an alert pop up can appear to advice about the bottom steps. A way to simulate the forcing action because all the steps are shown at first.
A big part of users' concerns about creating an account has to do with the overhead, related to this. I'd consider all the additional data that you're collecting for registration that is not part of doing a checkout. Unless you have some other objectives in mind (and I would question whether it is reasonable to combine two different objectives in a single ...
I have seen a common scenario is:
User clicks link in their Email
A tab in their browser opens, with some text like "Account Successfully Activated".
And that's it, the screen stays in there with the message. It does
not redirect to the website. Slack, Zoom and other services to this. Or at least they acknowledge that they will redirect the user, ...
Even time expiration limit not necessary for each application usecase, there is not much difference when a user is logged in or out within this frame.
Simply first, it should be checked if user already logged in and if
not, user should asked to complete login informations which prompted
before redirecting the user to verification grant. That means not
I can't see any trick to force user registration.
It is clearly displayed if want to see video, one need to login.which is with maximum contrast in message and background. So no dark pattern.
Displaying play sign initially will help user to recognize there is playable content like video or audio.