From a useful alert
to a shared review.

Start with the job your monitor should do.

These schedules are starting points, not recommended response deadlines. Adjust the goal, selected content, label and interval for the page. Checks use ordinary plan allowances; a workflow starter does not create another type of monitor or use AI credits.

For visual checks, preview a consistent region and tune masks and noise controls. For text checks, select a stable section when a whole page includes unrelated movement. See selections and alert rules.

A small review routine that stays manageable.

1. Choose the workspace first. New monitors belong to the selected workspace. On Business, everyone in it shares the monitors and their retained captures.
2. Start with a few pages. For a competitor, begin with pricing and product pages. For a vendor, use separate monitors for terms and privacy. For bids, pair a New items index with separate detail-page or PDF monitors for shortlisted notices.
3. Name and label by subject. Use names such as “Acme · pricing” or “Vendor · privacy policy.” Add a company, campaign or opportunity label alongside the starter label. Filter the watch list when reviewing a particular group.
4. Agree who reviews each group. Pick that responsibility within your team. PageFluxer currently has shared reviewed/unreviewed state, rather than built-in task assignment or approval stages.
5. Review the source, then mark the change. Open before-and-after captures, follow the source page when needed, and mark the event reviewed in Changes or monitor history. Teammates see the same state and the reviewer.

AI summaries can help explain a captured text change when separately enabled with consent and allowance. They do not establish legal meaning, grant eligibility or whether a visual change is a defect.

Keep setup quick. Choose delivery after saving.

Use Notifications for this monitor on its details page. Email, signed webhooks, Slack and Teams are independent delivery methods. Selecting a workflow starter does not turn on a new channel, grant AI consent or replace existing notification defaults.

On Business, an owner or admin connects a workspace destination first. A member can then enable it on a monitor. Each workspace currently has one Slack destination when available, one Teams Workflow destination and one generic webhook endpoint; it does not route each label to its own channel automatically.

Email goes to the workspace owner’s address using the workspace or per-monitor schedule. Inviting someone does not subscribe them to a separate email copy. Channel cards follow matching changes independently of email digests and quiet hours.

Connect Slack or Microsoft Teams → · Set email and webhook delivery →

Choose Business for collaboration.

Starters themselves are available on every plan. Ordinary webpage New items rules are available across plans; RSS, Atom and sitemap source watches require Pro or Business. Visual checks use Browser access and active visual-monitor limits, with Free’s existing one-time trial. PDF monitors have their own active limits within total monitor slots.

Business includes 5 seats and shared check allowances. Text history is kept for up to 180 days and image history for up to 30 days, each subject to storage limits. History is a working reference, not an unlimited or certified archive.

Everyone in a Business workspace can see, edit and delete its monitors. Labels organize work; they do not hide one client’s or department’s captures from another. There is no per-monitor permission boundary or multi-client portal.

Use public pages that the cloud can access. Recorded steps can prepare supported public views; they do not import a browser login or bypass access challenges. A page linking to a document does not automatically monitor that document, so add its direct URL separately.