A URL does not carry your signed-in session.
When you open a supplier portal, the website uses session information to decide what you may see. A separate Cloud capture does not automatically have that session. It might receive a login page, an empty application shell or a different account’s public view.
PageFluxer provides two approaches for supported pages you are authorized to monitor. Local uses your existing Chrome profile. Cloud Browser can use an explicitly approved workspace site connection. Neither is a promise that every portal works, and neither removes the website’s access restrictions.
| Question | PageFluxer Local | Cloud Browser with a site connection |
|---|---|---|
| Where does it run? | Your Chrome profile, in temporary inactive tabs. | A separate capture on PageFluxer infrastructure. |
| How is access supplied? | Chrome uses its own existing website session. | An owner or admin explicitly supplies a supported cookie session in Site connections. |
| Must your computer stay on? | Yes: awake, online and running Chrome. | No, but the approved source session must remain valid. |
| What can it capture here? | Supported text, prices, stock and new links. | Supported webpage text and visual captures; Cloud Browser limits apply. |
Set up a Local monitor with a meaningful access check.
Sign in normally on the source website.
Use an account with only the access needed for the page. Complete the website’s login and MFA yourself. Never record passwords or login submissions as page-preparation steps.
Connect the correct browser and workspace.
Open the PageFluxer extension, choose Local and connect the browser. An owner or admin approves it in PageFluxer. Return to the extension and finish connecting.
Select the useful content and a signed-in marker.
Choose the price, notice or status you want to capture. Add a unique visible CSS selector that appears only when signed in. A generic heading that also exists on the login screen is a poor marker.
Test in a fresh inactive tab.
Grant access to the individual site and confirm selected-content sharing. Test & start Local monitor verifies the actual background flow. A page working in your original tab does not guarantee it works in a fresh one.
Choose delivery and keep the browser available.
Open History & notifications to configure available destinations. You can close the original tab and side panel, but Chrome must remain running on an awake desktop.
Keep the access marker separate from the watched value.
A supplier portal changes its delivery estimate
What this meansWatch the dispatch element. Verify a separate account-navigation marker before accepting the capture, so a login redirect is treated as an access problem.
A selector such as #account-navigation is only an example: it must match your actual page uniquely. The watched element might be #dispatch-estimate. Choose selectors from the visible page and check them again after a redesign.
Some applications keep essential state in the original tab’s session storage, depend on foreground interaction or render content inside unsupported frames. A Local test may fail even though you are signed in. Do not make the access marker less specific simply to force a successful test.
Use a Cloud site connection when that model fits.
For a supported cookie-based page, a paid-plan site connection can supply an expiring session for one exact HTTPS origin. Set it up in PageFluxer’s protected Site connections flow, verify its signed-in marker, then create a Cloud Browser monitor using that connection. The site connection documentation gives the exact setup and limits.
This is a deliberate credential-sharing step. The extension does not export your cookies automatically. Never paste a Cookie header, password or token into a chat, recorded action or support message.
Authenticated Cloud captures enforce same-origin, GET-only access. Cross-origin dependencies, POST-based data APIs, browser-storage authentication and device-bound sessions can make a portal unsupported. Direct PDFs and feed sources remain public-only. Choose a method because its tested capture works, not because a page happens to show a padlock in the address bar.
Review who can see the selected content.
Local keeps website cookies, passwords and authentication storage on the device. Selected text and links, URLs, titles, monitor settings and recorded non-sensitive values are sent to PageFluxer for comparison, history and notifications. A small selection can still contain sensitive information.
Review workspace members and enabled notification destinations. Authorized API clients or connected assistants may be able to read retained captures. Local and authenticated captures are excluded from PageFluxer’s AI processing in this release, but that exclusion does not prevent an authorized assistant connection from reading content you share through it.
Read Local limits and recovery and data handling before monitoring a private source.