Profile-level context
The expected proxy sits with the Profile that uses it, keeping session identity and network configuration in the same operational record.
Feature · Network
Keep the intended network route attached to the work
Agilelogin manages proxy configuration alongside each Profile so operators can inspect the expected route before launching an authorized browser session.
Product documentation · Last reviewed August 4, 2026Reviewed against the current public product scope by the Agilelogin product team.
What is per-Profile proxy configuration?
Per-Profile proxy configuration is the practice of associating an operator-selected proxy endpoint and its connection settings with one named browser Profile. This makes the intended route easier to identify across sessions. Agilelogin manages the assignment; the proxy network, credentials, traffic handling, availability, and legal terms remain with the chosen provider and operator.
What the assignment helps control
A visible assignment reduces configuration guesswork, but it should always be checked against the actual needs of the workflow.
Pre-launch review
An operator can verify that the selected endpoint, protocol, and credentials match the documented workflow before opening the session.
Provider choice remains explicit
Agilelogin does not turn an external proxy service into part of its own trust boundary; provider selection remains an operator decision.
Direct routes stay valid
Not every workflow needs a proxy. A direct connection can be the correct documented choice when no alternate route is required.
Who controls each part of the route?
Separate the desktop assignment from the network service and destination website processing.
| Subject | Agilelogin boundary | Operator action |
|---|---|---|
| Endpoint, protocol, and Profile assignment | Configured in the desktop workspace for the selected Profile | Enter the intended values and verify them before use. |
| Proxy credentials and provider account | External service credentials used by the configured route | Protect, rotate, revoke, and purchase credentials through an approved provider. |
| Traffic, logs, location, and availability | Handled by the proxy provider and destination network | Review provider practices, applicable law, service health, and the actual observed route. |
How to assign a proxy responsibly
Treat the proxy as a separate service dependency, not as a universal privacy switch.
- STEP 01
Document the route requirement
Confirm why the workflow needs a proxy, which location or endpoint is permitted, and who approved the provider.
- STEP 02
Add the connection details
Enter the supported protocol, host, port, and credentials without placing secrets in Profile names or handover notes.
- STEP 03
Verify before launch
Check that the assignment belongs to the intended Profile and validate the route using an approved method.
- STEP 04
Handle failures explicitly
Stop or reroute according to policy when credentials fail, the endpoint changes, or the provider becomes unavailable.
What a proxy assignment cannot establish
Changing a network route does not settle every privacy, security, or authorization question.
- A proxy does not make the operator anonymous or remove other data a website may receive.
- Agilelogin cannot guarantee an external provider's logging, retention, location accuracy, uptime, or security.
- A different route does not grant permission to access a service or override its terms and controls.
Questions about Profile proxies
Does every Profile require a proxy?
No. Assign one only when the authorized workflow requires a specific network route. The important control is that the chosen route is intentional and reviewable.
Does Agilelogin provide the proxy network?
No proxy service is claimed in the current public scope. Agilelogin manages configuration for operator-selected endpoints; the external provider supplies and operates the network service.
Does a successful connection prove the proxy is trustworthy?
No. Connectivity proves only that a route responded. Provider ownership, retention, security, location, and contractual terms require separate verification.
Review the route with the Profile
See how network configuration fits into Agilelogin's wider security and shared-responsibility model.