What a profile holds
Without profiles, every workflow has to rebuild the same setup: sign in, clear the same popups, wait for the same cookies, cope with how the portal shows a PDF. That setup is fragile and it is not the business task.
In Ramain those choices live in the workflow's browser settings. A workflow can keep its saved login between runs, so a portal that remembers trusted sessions does not ask for a fresh sign-in every time, or it can start clean on every run when that is safer.
Network location is a setting
Some partner portals only accept connections from an approved network, a known IP address or a country. In Ramain, how the browser reaches a site is configured with the browser, not written into the workflow, and the workflow never sees network credentials.
What it is not
Profiles and network settings are not a way around a site's security. Digital workers sign in the way your staff do, with credentials you provide from the vault. For one-time codes they read a code sent to an inbox you control, and when a site requires a person, the run pauses and asks one.
Runs that share a profile
If several runs of one workflow save the same login state at once, Ramain warns you, because they can overwrite each other. Coordinate those runs when keeping a particular session matters.