Named environment
A predictable Profile name can record an owner, project, purpose, or region without opening the session to guess what it contains.
Feature · Profiles
Persistent browser state with a name and an owner
An Agilelogin Profile gives one authorized workflow an identifiable browser environment that can be closed and revisited without depending on a pile of ordinary windows.
Product documentation · Last reviewed August 4, 2026Reviewed against the current public product scope by the Agilelogin product team.
What is an isolated browser Profile?
An isolated browser Profile is a named desktop environment whose cookies, storage, history, browser settings, network assignment, and automation context remain associated with that Profile. The separation makes session ownership easier to understand. It is a browser-state boundary, not a separate operating-system user, virtual machine, or permission to access an account.
What stays understandable
The value of a Profile is not simply another browser window. It is the ability to identify the state, purpose, and network assumptions of repeated work.
Persistent browser state
Cookies, site storage, history, and relevant browser settings stay associated with the Profile so an approved workflow can return to known state.
Visible network assignment
When a workflow uses a proxy, its configuration is managed with the Profile rather than being hidden in an unrelated browser extension or note.
One automation context
Approved automation can target a dedicated Profile, making it clearer which process owns the current browser state and when that ownership ends.
Profile boundary versus surrounding controls
A Profile is one layer in a wider operating model. Device access, credentials, backups, and platform rules remain separate decisions.
| Subject | Agilelogin boundary | Operator action |
|---|---|---|
| Cookies, storage, history, and settings | Associated with the Profile that created or received them | Decide retention, backup, deletion, and who may launch the Profile. |
| Account credentials and recovery | Used inside the browser session; no password-manager guarantee is claimed | Use approved secrets handling, strong authentication, and recovery controls. |
| Desktop and physical access | Outside the browser Profile boundary | Secure the operating-system account, disk, updates, and physical device. |
How to create a useful Profile boundary
Begin with authority and purpose, not with the number of Profiles you want to create.
- STEP 01
Confirm authorized work
Record the account owner, permitted task, applicable platform rules, and person responsible for the session.
- STEP 02
Choose a predictable name
Use a convention such as owner-purpose-region so the environment can be recognized before launch.
- STEP 03
Review state and network
Check the intended Profile and any proxy assignment before opening or resuming the browser session.
- STEP 04
Close with a known outcome
Record whether the session should be retained, handed over, or removed, and keep credentials out of ordinary notes.
What Profile isolation does not promise
Clear limits keep an organizational control from being mistaken for an internet-wide security claim.
- It does not create authorization for an account, service, or dataset.
- It does not replace operating-system isolation, device encryption, endpoint security, backups, or physical controls.
- It does not guarantee how a website, proxy provider, extension, or connected automation tool will behave.
Questions about isolated Profiles
Is a Profile the same as an incognito window?
No. Incognito or private browsing is usually temporary and discards selected local data when the session closes. An Agilelogin Profile is intended to remain named and reusable with its browser state attached. Exact private-mode behavior depends on the browser.
Does every account need its own Profile?
Use a separate Profile when a real state, ownership, or network boundary is needed. General browsing or short-lived work may not justify a persistent environment.
Can two operators change one Profile at the same time?
The current public scope does not promise concurrent multi-user editing. Treat one operator or approved workflow as the owner during a session and verify released behavior before adopting a team process.
Choose the smallest boundary that fits the work
Compare Profile workflows for multi-account operations, team handovers, and approved AI-agent automation.