Abe on your website

Who this is for

This guide is for practice managers, software vendors (for example a clinical scribe) and their web developers who want Abe's official health updates on a website. It also covers people using Abe inside a website.

There are two ways to show Abe Updates on a website:

	Free preview	Subscriber panel for Abe Updates
Who it is for	Anyone who wants to see it or paste it into a page	A practice or software vendor with an Abe Updates subscription
Account needed	No. No personal details are collected.	Yes. An Abe account and an Abe Updates subscription.
What it shows	The latest official links from each source, and 3 searches	The full panel, linked to your Abe account
How you add it	Copy the embed code from the Try page	Register your website in Abe, then your web developer adds the panel (see below)

The free preview has a copy-and-paste embed code. The subscriber panel has no public installation snippet: a universal customer-ready installation is not yet implemented, and the complete subscriber journey on an outside website is not yet verified by Abe. Your developer follows the connection steps below instead.

Abe provides the panel and checks who may see it. Your own developer adds it to your website; Abe does not change your software. Abe shows official announcements and links to them. It is not clinical advice, and the panel is not for patient details.

Start here

1. See it first. Open Try Abe Updates. Everything in the preview is live and needs no account.
2. Make it yours. Use the Make it yours settings on that page, then copy the embed code. See Try it free and copy the embed code.
3. Subscribe if you want the full panel. See Subscribe to Abe Updates.
4. Connect your website. Follow Connect the panel to your practice website. Your web developer then follows For your web developer.
5. Not ready to connect? You can use Abe directly without a website embed. Open the professional-development finder or the evidence library.
6. Keep service credentials on your server. Never put a service key, client secret or long-lived user token into website code, a page address or browser storage.

Try it free and copy the embed code

Open Try Abe Updates. The preview sits inside a made-up example clinic website, so you can see how it would look on a real page. The clinic is not real. The free preview needs no account. It shows the latest official links from each source and allows 3 searches.

Under Make it yours, choose how your website should start. Visitors can still change layout, items, size and tabs themselves from the Display button in the panel.

Setting	Choices
Layout	Search first, Day timeline, Sources side panel
Items	Compact rows, Cards
Size	Automatic (fits the space it is placed in), Phone, Sidebar, Desktop panel, Full page
Colours	Light, Dark, Match your website (uses your accent colour, corners and font on a clear background)
Accent colour, Corners and Font	A set of accent colours or Your colour; corner style; Atkinson Hyperlegible, your device's font or a serif font
Tabs and their order	Tick which tabs to show and move them up or down
Sources switched on at first	One or more sources, or All
Opens on, Dates shown first	Whether it opens on official updates, and Any time, Today, This week or This month
Show Share on each update	Tick to show the Share button

Start again returns every setting to the default.

Below the preview, Embed code shows the code for exactly the settings you chose. Select Copy code, then paste it into your website's page editor where the updates should appear. The code changes as you change the settings. The page says Copied once it has been copied; if your browser blocks copying, select the code and copy it yourself.

The embed code is an iframe that loads https://www.abeai.com.au/embed/abe-demo, with your settings in the web address (for example layout, style, size, theme, accent, tabs, sources, range and share). It is the free preview. It does not connect to anyone's Abe account, so it cannot show subscriber-only features.

What the updates panel does

These features are in the free preview and in the subscriber panel.

• Source toggles. The sources are All, TGA, PBS, Medicare/MBS, Health, AHPRA/NMBA and State. Tick one or more to combine them into one feed, newest first. Each source shows how many updates are new in the last 7 days, or its latest date. State reads Not covered because Abe has no official state or territory source yet. It never shows state items.
• Three layouts. Search first puts the search box at the top. Day timeline groups updates by day. Sources side panel lists the sources down the side.
• Compact rows or cards. Compact rows fit more on screen. Cards give each update more room.
• Sizes. Fit automatically, Phone, Sidebar, Desktop panel or Full page.
• Filters. The Filters button opens the Date (Any time, Today, This week, This month or Choose dates) and Topic choices. Active filters show as chips, with Clear all.
• Search. Search matches word forms, so a plural or other form of a word still finds the update. Use public words and do not enter patient details. After the 3 free searches, the preview invites you to subscribe.
• Share. On every update, Share opens the phone's share sheet where the browser offers one. Otherwise it offers Copy link, Email and Copy for Teams or Slack. Every option shares the official source link, never an Abe page that needs a sign-in. If an update has no usable official link, it says The official link is not available.
• Open official page. Each update links to the official website, where the full update is published.
• Themes. Light, Dark or Match your website.
• Display menu. The Display button lets each visitor choose their own Layout, Items, Size and Tabs. Done closes it. Use the website's settings puts back the website owner's choices. A visitor's choices are kept in their own browser.
• PD courses tab. It shows Coming soon, with a blurred preview of courses (examples where live courses are not available). It has no price and no purchase link. Use the course finder directly in the meantime.

Connect the panel to your practice website

This is for a practice manager or software vendor. You do not need to be technical for these steps. Your web developer does the last part.

1. Subscribe. Sign in to Abe and subscribe to Abe Updates (see Subscribe to Abe Updates). The package includes showing the updates on your practice website once your site is linked to Abe.
2. Ask to connect your website. Open Application access and find Register an application. Your organisation owner can request access.
   • Application ID: a short name for your website or product.
   • Exact HTTPS origins: your website's own address, one per line, for example https://www.yourclinic.com.au. This is your website's address, not Abe's.
   • Exact return URLs: the web address on your site where people return after approving the connection, one per line. Your web developer can give you this.
   • Features: tick Browse Medicare, PBS, AHPRA, TGA and Health Department updates. Nothing is ticked for you. Only tick what you need.
3. Select Request access. The screen says Application registered. Access is pending ownership verification. Registering does not switch anything on and does not turn on alerts.
4. Abe checks your website belongs to your practice. Your connection stays pending until Abe has verified it. Until then it cannot connect.
5. Your web developer adds the panel. Give them this page and the developer guide. The next section is written for them.
6. Each visitor chooses what the panel may show. A person who signs in sees an Abe permission screen, Choose what this app can access, and approves only the access they want, with an expiry. Paying does not change which apps can see anyone's account, and alerts stay off until a person turns them on.

If a step shows a message you do not understand, copy the message without any private details and use Troubleshooting.

For your web developer

This section is the technical summary. The full contract is in Develop an authorised Abe connection.

• Free preview. Embed https://www.abeai.com.au/embed/abe-demo?v=... in an iframe. The query string is produced by the configurator on the Try page. Use the generated code rather than writing the query by hand. Give the frame a title and a height that suits the chosen size.
• Subscriber panel. It is a private Abe frame loaded at /embed/abe for your registered origin. The frame address selects your registered application and parent origin and identifies no subscriber. Never add a user token or credential to it.
• Registration. The organisation owner registers the application at Application access with exact HTTPS origins and exact return URLs. Registration stays pending until Abe verifies ownership. Keep the provisioned application credential on your server only. It must never appear in a browser bundle, URL, log or screenshot. Rotating it invalidates the previous one.
• Permission request. From your authenticated session your backend sends POST /api/connect/requests with the registered appId, exact redirectUri, scopes and a random host-bound state. For browsing only, send version: 2 and scopes: ["updates:read"]. The application credential goes in the x-abe-client-secret header. Open the returned consentUrl in a popup. The person chooses permissions and expiry, or declines.
• Accept the return. Check the popup window, the exact Abe origin, message type abe-connect-approved, version 1 and your original state. Send the short-lived code only to the same signed-in user's backend. Your backend then calls POST /api/connect/link with appId, your exact origin and the one-use code, and stores the result encrypted.
• Hand-off. Your backend calls POST /api/connect/widget/bootstrap with a contextId from that connection (server to server, with x-abe-client-secret, x-abe-evidence-session and the exact registered x-abe-evidence-origin). Load the returned frameUrl. When the frame sends ready from the exact frame window and Abe origin, post the one-use nonce to that window with Abe's exact origin as the target. Never use a wildcard target.
• Host client. The reference host logic is in src/lib/connect-abe/widget-host.ts. It refuses any frame address that is not on Abe's origin at /embed/abe with your registered host origin, and it expires an unused hand-off within 60 seconds. The parent page never receives the frame's private session, search results or snapshot.
• Your responsibilities. Navigation, mapping your signed-in user to the connection, clearing old content when the connection ends or the account changes, and confirming disconnection. Do not iframe the signed-in Abe console or identify a subscriber from an email address.

Abe's own reference application, Abe integration test application, shows the full flow. Its success does not certify another website. See What has been checked for the current limits.

What success looks like

An accepted integration shows only services that the customer can actually use, and explains unavailable services without encouraging another purchase. The shared component and authenticated frame let the user hide or reorder modules; display preferences do not revoke permissions, change payment or activate notifications. Current funding, personal permission, permitted source representation and exact application/channel checks remain independent. Expired snapshots remove service content until access is refreshed. Local component, hand-off and database tests do not establish a deployed website connection. Existing partner course access remains a separate route with its own scope and evidence.

Browsing without notifications

The browsing-only connection is deployed in Abe’s reference application. On 6 October 2026, the owner account saved the explicit browsing display choice and its native browse request returned HTTP 200 after the feed repair. Visible-result and saved-layout reopening checks remain incomplete; paid access and an outside application need separate acceptance. It lets a person read permitted official notices without granting notification delivery permission. Payment or employer funding does not subscribe anyone to alerts.

The display control is Add official update browsing. It changes the saved display only; existing choices remain until the person changes them. The person must separately approve the application permission. If a request loses its reply, retry the same search before changing filters; the prepared reader retains the original request so recovery does not consume another allowance. These steps still need the complete signed-in browser test before they establish a customer-ready installation.

What Abe's operator completes first

You do not need to create a Stripe account or a 100% discount to test your own approved owner access. A real purchase is a separate test. Abe's operator must first complete service and source checks for the registered application; a normal subscriber should not be asked to configure these checks or handle credentials.

The owner screen provides Check the course service under an active course-enabled application in Application access. Sign in as Abe's approved operator, choose the audience and an expiry within the next day, approve that bounded check, then select Run course service check. Opening the panel performs no check. This records the course engine's observed version only. It does not finish the embedded-widget, funding, source-use or personal-permission steps, and it does not subscribe anybody to updates. See the operator contract.

For no-charge owner testing, the operator uses Record approved access, selects First-party allocation and Browse official updates, and records the approved allocation for the correct Abe workspace. In Set up my owner access, the owner then chooses the services, access dates, allowance and period, reviews the displayed terms and saves them. These steps create funding records; they do not complete service acceptance, connect the person or turn on notifications. Never enter an invoice reference unless it was actually verified.

What the application developer needs

Send your developer Develop an authorised Abe connection, especially its widget implementation contract. That is the shared provider guide for any website or software product. Application-specific examples are separate; an example is not permission to reuse another application's registration or credentials.

The owner supplies the services, intended audience and exact application address. The host developer registers their app, keeps credentials on its server, lets each user approve the connection and displays Abe's private frame only through the verified hand-off. Abe supplies the frame, access enforcement, source boundaries and shared service. The host developer owns the navigation and integration changes in their application.

The panel's Official updates section is for regulator announcements and Department news; Rules and standards is for legislation, registration and professional requirements. Professional development finds courses; Practice governance reads authorised organisational records. This product does not provide clinical evidence updates or patient-treatment advice. Read Source coverage for the collected feeds and their limits.

The update reader now checks the sources covered by the selected access package and their current permissions. Link-only access shows official links and permitted dates; it does not unlock copied headlines or summaries. Specifically permitted PBS metadata remains available. This repair is deployed and still needs the complete subscriber test; paying for access does not turn on notifications.

The deployed browsing-only reader shows notices by the official publication date, newest first, rather than the date Abe collected an archive. Notices without a usable, permitted publication date appear after dated notices. Published is the source's date; Detected or Last checked describes Abe's collection. Reading another page keeps the same snapshot. This date ordering has isolated checks; its complete real-subscriber journey remains unproved.

Opening course details

In the local authenticated implementation, choose Find courses, run your search and select Open course details. That button requires your separate course-detail permission and an available package allowance. Loading course details uses your package's search allowance. The panel shows only currently permitted course information, provider links and required source credits. Choose Close course details to clear it. While a request is pending, Cancel course details cancels your browser request; a query already completed can still count towards your allowance. An uncertain response is not automatically retried. Choose Check previous request to ask Abe about that same request. This does not start a replacement request or use a second allowance for a retained completed result. That option lasts while this panel stays open; closing details, changing the search or leaving the panel clears the local request reference. If Abe still cannot confirm the outcome, it keeps the result unavailable.

These controls and allowance checks have passed isolated tests. Their deployed, signed-in subscriber journey remains unverified, so this section describes the implemented local behaviour rather than promising that every website can use it now. Listed course hours do not establish professional recognition or earned CPD credit.

Question	Current answer
Can I review the expandable layout?	Yes, use the widget preview. It uses illustrative access rather than a subscriber account.
Can an ordinary subscriber install and use the complete widget now?	No complete customer acceptance yet. The provider and reference consumer are deployed, and genuine no-charge owner allocation has been recorded. The complete registered-app journey remains unfinished. The reference app's server configuration and signed-in entry were verified on 6 October 2026. Accepted service access and the complete subscriber journey still need verification.
Does creating Stripe products finish it?	No. Approved Abe offers, verified funding, personal consent and the accepted interface remain required.
Can I test your owner access without a Stripe discount?	A genuine no-charge owner allocation is recorded for the owner test. The complete content and saved-display journey still needs proof. That access test does not prove a customer payment.
Can a clinician browse without receiving notifications?	The implemented update reader separates browsing from delivery. The completed normal subscriber journey must prove that separation.

For the person's steps, use Connect from another application. For the operator's steps, use Stripe product setup. A developer should not direct users to pay for an unfinished connection.

Local implementation preview

The Abe development preview at /connect-abe/widget-preview demonstrates illustrative packages, display controls and updates states. Its funding and source checks are synthetic examples. It does not connect an account, charge money, save subscriber settings or activate alerts. Package names and prices are not approved offers. Use it to assess the layout; use a real authenticated integration and actual receipts to test the customer journey when those steps become available.

The account preference endpoint is a same-origin, signed-in Abe account operation. The separate frame preference endpoint uses the current private frame connection; it does not need browser cookies or accept a posted user identity. Neither endpoint is a public widget installation endpoint. The widget preference and hand-off database schema has been applied to Abe’s hosted database. Database application alone does not establish a completed subscriber connection or a usable external installation. An external application's developer owns their application's changes; Abe supplies the shared interface, approved connection contract and tested setup guide.

The secure hand-off has transport and browser lifecycle implementations. They refuse replay, keep frame credentials out of the parent website and clear old results when a connection changes or expires. The neutral frame document checks the selected application against Abe's registered origins; it does not identify a subscriber from a website link. The provider transport routes are registered with confidential app credentials, retained personal permissions, membership and current funding checks. Their default account-access reader now uses those existing authorities. The update-feed route and frame renderer are deployed. A user can select a source or public topic and browse retained source-linked announcements without giving notification permission. Pausing notifications preserves browsing. This is not a verified customer installation: the complete content journey, other embedded operations and the normal registered customer journey remain unfinished. A developer cannot yet install the full service by pasting a script into a website; the complete registered connection and ordinary subscriber test must come first.

Try the Abe reference application

This test belongs to Abe. An outside application developer does not need to change their software to inspect it, and Abe does not change that software.

The page offers Application and owner access setup, View the layout preview and My application permissions. Use setup for the operator's prerequisites, the preview for sample layout, and application permissions to inspect or revoke your own grant. These are different destinations; opening one does not complete the others.

Under Select access to test, choose only what you want. Nothing is preselected:

Choice on the test page	What you are requesting
Search rules and standards	Permission for Abe's rules-and-standards read service. Its current panel link opens that service in Abe.
Browse Medicare, PBS, AHPRA, TGA and Health Department updates	Permission to browse supported official announcements covered by your access and current source permissions. This does not activate notifications.
Read my saved update choices	Permission to read your existing preferences. Browsing is a separate choice.
Edit my update choices	Permission to edit preferences; it does not select topics or timing for you.
Allow delivery of updates I separately select	Permission for delivery only after your separate criteria, timing and supported destination choices.
Browse professional development	Permission to search the permitted course catalogue.
Read course details	Separate permission to open permitted course details. For the panel journey, also select Browse professional development.
Read my organisation’s governance records	Permission for the authorised workspace's records; its current panel link opens Abe.

The separate browsing choice is deployed in the explicit version-two connection. The genuine signed-in subscriber check remains unfinished. Existing connections are not automatically upgraded.

These choices request access. They do not buy a package, supply missing source permission or establish that the service can operate.

1. Have the Abe operator complete the reference application setup. If the page says setup is required, it cannot connect yet.
2. Sign in and open Abe integration test application. It uses the workspace resolved by your Abe session. Check the displayed workspace and decline if it is wrong; this test page does not offer a workspace selector. An authorised member account is required; public registration is not offered by this journey.
3. Tick only the access you want and press Connect selected access. Nothing is preselected. If you close the popup, use Cancel pending connection before starting another attempt.
4. In the Abe permission window, review Choose what this app can access. You can choose fewer permissions than you requested. Set Connection expiry, tick I approve only the selected access, then press Approve selected access or Decline. The permissions, expiry and confirmation start empty. Return to the application. A linked permission does not prove that its services have current funded access.
5. Press Open widget. Abe checks current membership, funding, personal permission, service acceptance and source availability before displaying a module. It may explain why a selected service is unavailable.
6. Expand Your display choices. If Add official update browsing is offered, select it and wait for the saved confirmation. This keeps your existing choices and adds browsing to the panel.
7. Under Browse official news links, optionally enter public terms in Search news links and choose Source, then press Browse or search. Read the source-linked notices and use Show more news links when offered. Browsing and notification delivery are separate. To manage notifications, open My update choices. Pause applies to an existing active choice; if you have none, there is no pause outcome to test. New alerts require separately chosen criteria, timing and a supported destination followed by explicit activation. Do not supply patient information.
8. Choose Disconnect test application and confirm the prompt. Abe clears the frame locally before asking to revoke the connection. Treat a pending or failed reply as unconfirmed remote revocation; inspect My application permissions before assuming the grant has ended. Pause notifications and cancel any paid access separately.

Moving focus between the reference page and widget preserves the frame while Abe conceals it and rechecks your user and workspace. A hidden page, changed identity, failed verification or expired connection clears access; choose Open widget to reconnect. The reference application uses Abe's login and origin. Its success would not prove another vendor's sign-in, browser restrictions or installation.

These are implementation steps, not a record of a successful real subscriber test. You do not need a personal Stripe account or a discount to test genuinely allocated owner access. A purchase test is a separate test using Abe's merchant sandbox.

Refreshing an open panel

The latest local implementation lets Abe refresh an idle connection while you keep the panel open. Your typed course-search choices stay in the same frame. Previous results are hidden during refresh; Abe checks your current access before showing the refreshed services. Refreshing does not run another course search, spend another search allowance or turn on notifications.

If a request was interrupted and Abe cannot confirm its outcome, automatic refresh is refused. Do not assume a cancelled request never completed. The existing deliberate previous-request controls are separate from refresh, and do not prove every interrupted operation is recoverable. Closing the frame or changing account clears the local draft.

The latest local repair makes Check previous search one deliberate continuation. Abe first checks whether that exact original request completed, refreshes the same connection with current access, then asks the original result owner for the retained result. It preserves the original filters, page and request identity; it does not create another search. Editing the form, disconnecting, changing account or losing current access cancels the continuation and withholds late results. An unfinished or unconfirmed original remains unavailable. Changed funding or source rights can still prevent recovery; this is not a promise that every old search can be reopened.

This recovery passed a synthetic browser journey and independent local review. It has not proved real subscriber authentication, payment settlement or recovery after a payment change.

This describes local implementation awaiting release and a genuine subscriber test. A preview or a synthetic browser test does not establish that your account can use the complete paid service.

Who completes each step

The latest local Application access registration screen offers Browse Medicare, PBS, AHPRA, TGA and Health Department updates separately from Manage selected updates. An organisation owner can request just browsing; nothing is selected automatically. Registration still requires ownership verification and current funded service access. The available sources are those independently permitted for that person and application, not a promise of complete coverage of every named source.

This separate browsing connection is deployed; the completed reference-application test remains outstanding. The developer instructions for its explicit permission request are in the connection contract. The existing steps above do not yet prove the new browsing request can be completed in the live example application.

Person	Responsibility
Abe operator	Verify the registered application, protected server setup, independently approved services and source use, and genuine funded allocation. Retain acceptance for that exact application and deployment before offering it to subscribers.
Website or software developer	Connect their authenticated user to the exact registered origin and return address, protect server credentials, implement the hand-off and navigation, clear old content, and verify disconnection. Abe's own reference application does not verify their host.
Subscriber	Choose access, expiry and consent; open the widget; choose what to display; deliberately search or open details. Choose any alerts separately and disconnect the intended application when required.

No subscriber needs to enter a secret or configure Stripe. An unavailable service needs its named access or source prerequisite resolved; another purchase does not establish a missing interface check.

What has been checked

Boundary	Evidence and remaining limit
Illustrative preview	Demonstration packages and layout only. It does not retain your subscriber preferences, funding or consent.
Owning local checks	The actual confidential connection and private preference owners retained Hide, Show, reorder and reopen for a synthetic ordinary member/workspace, while independent access, source, usage and alert records remained unchanged. Actual course search/detail and deliberate same-request recovery also passed local owning checks. These are disposable fixtures, not real customer records.
Local browser journey	The Abe-owned course test passed search, details, deliberate same-request recovery, source-withdrawal refusal, genuine disconnect confirmation and revocation. Authentication, source permissions and funding were synthetic fixtures; the production components and local database owners performed the operations. This does not prove real sign-in or a deployed customer installation.
Deployed signed-in acceptance	The complete ordinary subscriber journey has not passed. Real sign-in, current approved source access, package allocation and the deployed application still need acceptance together. Payment and chosen-time delivery need their separate checks.

The local preference and browser proofs do not close deployed acceptance. An operator still needs the exact signed-in deployed journey, current source rights, real access allocation and current app acceptance. This guide does not certify an outside website.

Arrange your panel

After a verified connection opens, expand Your display choices. If Add official update browsing is offered, select it and wait for the saved confirmation before browsing. Use Hide or Show for a service and Up or Down to arrange it. The panel saves these choices to your Abe account in the selected workspace. Reopening the connection reads the retained choices. Hiding every service leaves the display controls available so you can show one again.

These controls change the panel only. To choose sources, topics, timing and destinations, open your separate update choices in Abe. To pause notifications, revoke application permission or cancel paid access, use those separate controls. Hiding a service does none of those things.

If saving is interrupted, the frame clears and asks you to reconnect. Your choice may already have been saved. Reopen the widget and inspect the retained display before trying again; the app does not automatically repeat the write. A changed account, expired connection or withdrawn permission cannot receive a late result from the previous connection.

Rules-and-standards and governance work currently open in Abe through the panel's links. Those links do not perform an embedded search or governance action. The ordinary production subscriber acceptance test remains outstanding.

Find courses in the panel

The shared frame now includes the existing professional-development catalogue search. It appears only when your current connection, selected catalogue permission, funded access and service/source checks allow it. This is an implemented operation; the normal subscriber acceptance test is still outstanding.

In the local implementation, course searches select only the sources covered by your access package, before choosing results. An unrelated course outside that package cannot block the whole page. Abe still checks which course details and links it may display. If your permission or the source permission is withdrawn during a search, Abe withholds that response, including an empty result page. These repairs are independently tested locally and await release; they do not establish a completed subscription or embedded installation.

1. In Find courses, enter public course terms. Optionally choose a profession, delivery method and maximum course price. Empty fields apply no extra preference. These choices do not subscribe you to alerts.
2. Press Find courses. Nothing runs when you merely open the panel. Each new search or next page uses your package's search allowance. Changing a field clears the previous results and cancels the browser request; a search already completed can still count towards your allowance.
3. Read the information and checking dates shown for each course. Abe shows only the fields permitted for that source and connection, with any required source credit. Some results show Course link without a title or provider. See course page for price means no price is displayed; it does not mean the course is free. Use View course to check the provider's current information. Course information does not establish enrolment, available places, professional recognition or earned CPD credit.
4. Read the relevance-check state. Relevance check unavailable means an automatic Jev check was not completed; catalogue results remain distinct from a checked recommendation. Combining result pages does not give earlier results the newest page's check.
5. Use More courses when available. If a reply is interrupted, choose Check previous search before starting another search. Abe checks that same request and its original filters. A retained completed result does not start another query or use another allowance; an unconfirmed result stays unavailable. The panel does not retry automatically. Editing a filter or closing the whole connection clears its temporary recovery reference.
6. If the connection expires or you disconnect, reopen it from your application; old search work cannot return results into a new connection.

Search allowance and interrupted-request recovery have passed isolated tests through the default widget server path. They have not established the deployed, signed-in subscriber journey. This guide describes the local implementation until that separate test passes.

The latest local repair keeps your four course-search choices when you hide and show the course section or successfully rearrange the same panel. Previous results and course details disappear; reopening does not run a search. If a search was interrupted, Check previous search remains a deliberate choice. This behaviour has passed an isolated browser test and awaits release.

A new connection, expired connection or changed account clears those temporary course choices and the interrupted-search reference. Saved panel visibility and order are separate account settings. Keeping a form choice never supplies permission, confirms payment or turns on notifications.

The operation reuses Abe's existing course finder. Rules-and-standards search and practice-governance operations inside the shared frame remain separate work; their availability labels do not execute those services.

Each course shows its own relevance result. Checked, irrelevant and unchecked courses have separate labels. More courses retains the original check and catalogue date for courses already shown; the latest-page date applies only to the latest page. Missing or duplicate check records are shown as needing review.

Permission to display a course link is separate from permission to process its information for a relevance check. A link can remain useful while its relevance check is unavailable. These display cases have been verified locally with synthetic source permissions; the normal signed-in subscriber journey and production relevance checking remain unverified.

If it does not work

Use direct companion access. A missing widget cannot be repaired by copying another partner's credentials or framing a protected console page. Cookie restrictions, changed origin, expired connection and unavailable source need their own verified recovery paths before release. Contact support through Troubleshooting. For a healthcare website, public professional information and patient-specific advice also have different intended purposes and publication requirements.

Stop or change your choices

Users remove an app permission through My application permissions. Pause alerts separately. Website owners can remove their own displayed link or installation when one exists, but that does not itself confirm remote permission removal or cancel customer billing. Review Manage and cancel. A future widget disconnect must be verified on the next protected operation, with personal preferences retained.

Testing without a payment

An owner service-access test does not require a 100% Stripe coupon or discount. Use a genuine, explicitly approved no-charge owner allocation and the registered connection. This allocation has been recorded for Abe’s current owner test. This is funded service access; it is not a settled customer purchase. The recorded allocation does not demonstrate a successful paid-subscriber journey.

Abe must independently verify source permission, personal consent and alert choices. Funding supplies none of them. The normal connection must pass sign-in, selected-source browsing, pagination, saved display choices, pause, expiry, account change and confirmed disconnection in the Abe-owned test application. Those complete deployed customer acceptance steps have not yet passed. The outside application's developer must then verify the same provider contract on their own host.

Use Abe's Stripe sandbox separately to prove purchasing: checkout, payment processing, access read-back, renewal, failed payment, refund or dispute, supported changes and cancellation. Abe has a locally tested initial payment-to-funding application. Events whose independent checks cannot complete still remain pending, with associations suspended; a signed event or a paid observation alone is not active funding. No-charge access testing does not activate payments or approve source use. Sandbox acceptance also does not activate live payments. A preview grants no access, and a 100% live discount is not a substitute for either acceptance journey. Follow the operator's billing guide.

Owner: prepare an official-updates implementation check

For a deployed release containing these controls, the owner panel appears under an active application with official-updates capability in Application access, after Abe verifies your current owner account and workspace. Opening it starts no service check.

1. Expand Check the official updates service. Explicitly choose the audience supported by your current verified owner workspace: individual for a personal workspace, or organisation for an organisation or site workspace. Software-partner checks are not offered by this operation. Then press Load reviewed sources and choose one source; an empty list means no currently reviewed source is available for that application and audience. An unavailable or non-owner workspace does not offer this panel.
2. Set Check expires at within the next day and the source’s reviewed validity. Tick I approve this bounded source and updates service check, then press Run source and updates check. Abe records the existing source permission observation, then checks the actual current updates service. This does not grant new source rights, funding, customer permission or notification delivery.
3. After both checks are confirmed, use Download owner check selection. Upload that file to the separate owner implementation check. The file selects the recorded engine and source originals; it does not certify the widget interface, origin or subscriber journey.

An interrupted or unconfirmed check holds further attempts. Keep the displayed source and engine operation IDs and ask Abe support to reconcile those exact records before continuing. Reloading the same tab retains the hold for that verified account, workspace and application. There is no automatic retry or local release control; changing account does not clear the earlier account’s pending record. The browser reference is not a server receipt, and clearing browser storage does not establish that a check failed or undo a retained record.

Use this flow only after confirming that release is deployed. These are owner implementation checks; they do not establish accepted embed/origin evidence, funded subscriber access or a completed customer journey.