Which role is assigned before launching the captive portal splash screen?

The pre-authentication role is assigned before launching the captive portal splash screen because it defines the initial access level and permissions granted to a user who has not yet completed the authentication process. When a user tries to connect to a network requiring authentication, they are placed in a pre-authentication role, which allows them to be directed to the captive portal. This portal is where they can provide their credentials or agree to terms and conditions to gain access to the network.

Assigning this role before the captive portal ensures that users are not granted any rights to access network resources until they complete the authentication process. This controlled access is crucial for maintaining network security and managing user permissions effectively. The other roles mentioned, like post-authentication, guest, and admin, apply to different stages or types of user access and would not be relevant at the point where the captive portal is first presented to the user.