HTTP has no memory: every request arrives alone. If a shopper had to send a password with each click, the site would be unusable. So after a successful login at shop.example, the server creates a session and gives the browser a session id in a cookie.
From then on the browser sends that cookie automatically. The server looks the id up in its session store, finds the user it belongs to, and treats the request as theirs. The session id is therefore a temporary password: whoever holds it is that user.
💡Good to know
Passwords are covered in Passwords & Hashing. This lesson starts after the login succeeds.