One watch list.
Your whole team, in the loop.
A workspace brings your monitors, captured changes, reviews, and notification channels together. Business includes five seats for $50 USD/month, or $500 USD/year, plus applicable tax.
Start with the pages you already watch.
- Sign in and check the workspace name above your dashboard. Existing accounts start with their own private workspace.
- The owner upgrades that workspace to Business on Pricing. Existing monitors, captures, and usage stay with it.
- Open Workspace, give it a recognizable name, and invite teammates.
- Connect a Slack channel or Teams Workflow, then enable delivery on the monitors your team wants to hear about.
Inviting someone shares all monitors and retained history in that workspace. Review existing URLs, capture steps, screenshots and AI settings first. Members can see captured content, so only share a workspace with people who should have that access.
Joining another workspace does not transfer your private monitors or cancel your personal subscription. Switch workspaces above the dashboard. Each workspace has its own subscription and usage. Creating extra owned workspaces, transferring monitors between workspaces, and self-service owner transfer are not part of this release.
Give each person the access they need.
| Permission | Owner | Admin | Member |
|---|---|---|---|
| View monitors, captures and history | Yes | Yes | Yes |
| Create, edit, pause and delete monitors | Yes | Yes | Yes |
| Mark changes reviewed / unreviewed | Yes | Yes | Yes |
| Choose delivery methods on a monitor | Yes | Yes | Yes |
| Enable monitor AI and grant capture consent | Yes | Yes | Yes |
| Manage workspace channels, email settings and API tokens | Yes | Yes | — |
| Invite or remove members | Yes | Yes | — |
| Invite, promote, demote or remove admins | Yes | — | — |
| Purchase, change or cancel the workspace plan | Yes | — | — |
There is one owner. Admins and members can leave; the owner cannot leave or remove themselves. There is no read-only or per-monitor permission role. Everyone in a workspace can delete a monitor, which removes its retained history. Only invite trusted collaborators.
Five seats, with no surprise seat charges.
The owner counts as one seat. Pending invitations reserve seats, so two admins cannot promise the last seat to different people. Invite by email as a member; owners can also invite admins. The recipient signs in with that exact email address and explicitly accepts.
Invitations expire after seven days. Resending replaces the previous link. Revoke an invitation to free its seat immediately; a delivered link then stops working. If an email is delayed, the inviter can copy the newly created link and share it directly with the invited person. A workspace can issue up to 20 invitations per day, with a one-minute wait before resending to the same address.
A person can belong to up to 20 workspaces, including their private workspace. Removing a person stops new access to the workspace. Removing or demoting an admin also revokes the API tokens and pending invitations they created. Workspace channel connections stay in place. Already delivered notifications and a request already in flight cannot be recalled.
One change. One shared review state.
Use the Changes inbox or a monitor’s history to mark a change reviewed. Teammates see the same state and the reviewer’s email. Marking it unreviewed clears that attribution; the latest action wins. Review does not dismiss a notification that has already been queued and does not change the monitor’s next comparison.
Workspace activity lists recent membership and integration changes for owners and admins. This is an operational activity list, not an immutable compliance archive. It keeps up to 90 days and 5,000 entries per workspace.
One generous, finite pool.
| Monitor slots | 250 webpages, PDFs, source watches and visual monitors combined |
|---|---|
| HTML / PDF checks | 200,000 per calendar month · 5-minute minimum |
| Browser checks | 15,000 per calendar month · 15-minute minimum |
| Visual monitoring | 25 active visual monitors · up to 30 days / 3 GiB image history |
| Text history | Up to 180 days / 1 GiB, whichever limit comes first |
| AI change summaries | 1000 per month · opt-in |
| AI monitor setup | 250 usable suggestions per month · opt-in |
| Recorded interactions | 20 steps per Browser monitor within existing capture limits |
| Email alerts | 2000 per month, then a daily workspace digest |
| Outbound channel attempts | 30,000 per month shared by webhooks, Slack and Teams, including retries and connection tests |
| Setup previews | 500 per month, up to 80 per UTC day |
| Public API | 120 requests/minute, 10,000/day, 250 MiB read data/day, 10 active tokens |
| Manual checks | 50 requests/day within normal check allowances |
Allowances are shared by all members and tokens; five seats do not multiply them. A slot does not promise continuous checks at the fastest interval. At the monthly check limit, monitoring waits for a reset or an upgrade. No automatic overage charges. Oldest history can be trimmed before its day limit when storage fills. See how usage is counted →
One owner manages the subscription.
Only the owner can open Stripe billing, view the saved billing location, or change the plan. Business is a fixed workspace subscription with quantity one; additional seat purchases are not available. Paid plans currently require a Canadian or US billing address.
Stripe shows prorated amounts before a plan or billing-frequency change. Cancellation takes effect at the end of the paid period. A downgrade ends collaborator access when the lower entitlement takes effect; the owner keeps access. Pending invitations and API tokens created by collaborators are revoked, and waiting Slack/Teams deliveries are cancelled. Existing memberships and saved integrations remain, so access and future channel delivery can resume after Business is restored. New API tokens and invitations must be issued.
Excess monitors pause and the lower plan’s history and storage limits apply. Restoring Business does not restore deleted history or replay cancelled notifications. Owners should export any records needed before downgrading.
Extension and API, in the same workspace.
Bring a selected element or recorded sequence from the Chrome extension into PageFluxer, check the workspace shown above the creation flow, and confirm the cloud preview. The extension does not gain access to cookies or team credentials. API tokens are issued for the selected workspace and cannot select a different one through a request parameter.
Business adds collaboration in the app; the public API continues to manage monitoring resources. Invitation, role, and billing administration are not exposed through API tokens.