Operate application access safely

Who this is for

This guide is for an authorised Abe platform operator reviewing an application and its recorded access. Being a clinic owner does not make you a platform operator. Clinic administration is explained in Administrator. No new external-channel outcome dashboard is proven by this guide.

Test funded access in an application

Choose the relevant application guide under Use Abe in other apps. Owner-sponsored funding removes the need for a purchase; it does not remove sign-in, personal permission or your own alert choices. Use the same screens a customer uses. Do not create a Stripe discount to work around a failed connection.

Give any outside application's developer the shared connection guide, website-widget guide and the relevant application instructions. Their team owns their application's code and deployment. Abe must first prove its provider connection in an Abe-owned test application; a named vendor guide is not proof that vendor is connected.

The shared display, secure hand-off and private update-reader have implementations. The owner terms writer and screen are deployed; a genuine owner submission and successful customer connection have not yet been verified. Saving terms does not establish service acceptance. A successful owner or paying-customer journey through connection, chosen-source browsing, pause, expiry and disconnection has not yet been verified. Subscription checkout testing is a separate step in Billing.

An owner-access correction has passed local checks using the actual terms-saving process and separately accepted test applications. Its database changes were installed and read back on 4 October 2026 (Brisbane). The application code is deployed. Your signed-in owner setup and successful connection still need verification. If the current access check reports unavailable, ask the Abe operator to check the saved terms and application acceptance. Buying a subscription or making a Stripe discount is not the remedy for that connection failure.

You do not need a Stripe account or a 100% discount to test the owner route. The remaining prerequisites are a genuine approved owner allocation, a verified registered test application, your separate permission and a successful current service-access check. The widget preview can demonstrate the layout now; it cannot grant access or prove those prerequisites.

To prepare customer subscriptions, follow Set up Abe products in Stripe, then give the Abe developer the payment connection requirements. You approve the package, price, tax treatment and commercial terms. The developer prepares the account and exact price mapping and proves the payment-to-access journey. Product creation and owner-funded access do not substitute for that proof.

Choose your owner access

Use Set up my owner access in your authorised platform-owner account:

1. Open Application access and check the current Abe workspace. Choose an existing owner allocation. Nothing is selected for you. If none exists, an authorised platform operator uses Record approved access: verify the customer organisation, expiry and actual evidence reference, choose First-party allocation under Licence evidence type, select the approved services and confirm only verified evidence. Read back the recorded allocation before opening Set up my owner access. A licence alone does not establish service acceptance; no invented evidence or Stripe discount can supply that missing check.
2. Tick the services you want. Official updates means supported government and regulator notices; it does not mean clinical-evidence updates. The original allocation restricts which services can be offered.
3. Enter the start and end dates and times, your allowances and the allowance period. Dates use your browser’s local time zone and must remain within the original allocation. Choose a start time after your approval so it does not pass while you review the form. The allowance period controls usage, not notification frequency.
4. Review Your choices and the displayed owner terms. Tick I approve these services, dates, limits and owner terms, then Save my owner terms.
5. Read the returned notice and Saved owner choices. These confirm retained terms only. Current service and source checks, a verified consumer and your separate connection permission remain required. No notification subscription is created.

If a save is unconfirmed, retry the same choices: the same retained operation is checked without silently creating a second approval. If the source or approval changed, reload and review the saved choices before another action. Earlier terms retain their original approval time. Reloading the page shows your retained choices.

This owner route is separate from a paid customer purchase. It preserves the ordinary connection and source checks. It does not prove checkout, delivery, pause or disconnection.

Course-source permission review — being verified

Reading current controls in Commercial source use was verified in a genuine signed-in owner account on 5 October 2026 (Brisbane). The screen now loads the selected source's controls and retained history. Approving or withdrawing course-source permission, including recovery after a lost reply, still needs live verification. Database installation and a successful read create no course-source permission or subscriber access.

The subscription backend checks course-source permissions against their owning records. Withdrawal closes the affected permission even if an older copy remains elsewhere. Source permission is one requirement: the exact information displayed, the application's accepted interface, usage limits and the subscriber's access still need their own checks. Installing database support does not make the customer service available.

Open Professional development sources. If Commercial source use is offered in your authorised platform-owner account:

1. Choose Owner workspace, then the source or provider to review. Select Read current controls. No workspace, source or decision is chosen for you.
2. Record the actual permission evidence, permitted page or path, selected information, application, review dates and reason. Provider identity is reviewed separately from permission to display its course information.
3. Review the displayed details. Confirm only the exact decision you intend to make. An approval does not purchase access or subscribe anyone to updates.
4. If the response is lost, keep the original request held. After reloading, choose the same workspace and read its controls to restore the original request. Select Read current controls and recover history to read the retained outcome.
5. If the outcome remains unresolved, either explicitly choose Resume this same request or Close this unresolved request. Resuming keeps the original details; closing prevents a late copy from creating a new approval. Closing does not withdraw an approval that already completed.
6. Review the retained outcome before allowing another review. If an approval must be withdrawn, use its separate Review withdrawal action. An older retained approval does not establish current display permission.

If browser storage or the retained outcome cannot be read, additional writes remain held. Do not clear browser storage to bypass recovery; ask the Abe operator to check the original request. Do not include patient information or credentials in permission evidence.

Start here

1. Sign in to Application access using your own authorised account. Check the application and organisation before changing anything.
2. Review its exact HTTPS origins, exact return URLs, requested features and ownership evidence. A registration is pending until verified; a registered application does not subscribe anyone to updates.
3. Only if the platform-owner controls are actually offered, provide the ownership evidence reference, select I verified the application owner and exact return URLs, then Activate verified application. Check the returned notice and application state.
4. Record only approved access through the controls offered to your authorised role. A first-party allocation or verified invoice is different from a processor-confirmed customer payment. Do not create a price or paid receipt from an administrative note.
5. For Rotate server credential, read the confirmation first: the existing credential stops working. Transfer the one-time result directly to the application's protected server secret store and use Hide credential. Never send it through support, chat, screenshots or browser storage.

Each person still approves their own permissions. Payment, application registration, source permission, customer-channel acceptance and notification activation are separate. Governance documents stay in their authorised organisation; sponsors do not gain staff private alert criteria. Do not put patient information into professional reference searches or delivery channels.

What success looks like

The current page confirms the specific registration, allocation, suspension or credential rotation you performed. Check the state again rather than treating an opened window as completion. A current service description or dated PD engine observation does not prove a vendor connection, complete source coverage or accepted paid operation.

Abe's owner course-search check is deployed in Application access for the independently configured platform owner. Find the relevant registered application card, check its displayed organisation and origins, and use Check the course service within that card. This control is offered only for an active application with professional-development access and current platform-owner permission. Choose the audience and expiry, then explicitly confirm the check. It checks real API responses and retains its own result; you do not supply a report or tick a “passed” box. A retained check must match the current application release and remain within its expiry; an earlier result cannot approve a later release. A completed engine check does not approve course-source permissions, fund access or establish the widget or payment journey. If a response is lost, inspect the retained original before trying again; do not repeat an uncertain operation.

There is also a locally tested operator check for an official-update source's already reviewed permissions. It records the exact source, selected use and review version; it cannot approve broader copying rights or activate notifications. A changed or expired source review prevents that old record from being used. Its operator implementation is deployed, and one AHPRA link-only source check was retained and independently read back on 5 October 2026. That dated observation must still pass current source-policy and expiry checks before use; it provides no subscriber funding or connection. Abe support operates this check; it is not a new button in your account. If its result is uncertain, the operator reconciles the retained operation ID before another attempt. You do not need to supply a passed report or run a command yourself.

For future approved external adapters, preserve these outcome distinctions:

Outcome	Meaning	Safe next action
Accepted	A real provider receipt exists for the intended destination. Accepted does not mean read by a person.	Keep the receipt; do not send the same operation again.
Unknown	The provider may have acted, but the result is unconfirmed.	Hold the outcome and ask support to reconcile the exact authorised destination. Do not blindly resend.
Failed	A definitive failure is recorded, distinct from an uncertain response.	Check the stated cause and whether a safe retry is permitted.

These are acceptance requirements and a recovery procedure, not claims that a new Telegram or Notion dashboard exists today. An in-flight provider call cannot be recalled by later revocation.

If it does not work

If the role, organisation, ownership evidence or result is wrong, stop. Ask support to check the application and approximate time without keys, patient data or private criteria. For an unknown send or payment, check existing records before another attempt. Do not invent a receipt or mark an uncertain result delivered.

For scheduling problems, distinguish daily source collection from each person's delivery choices. Check timezone, quiet hours and active preferences through Alerts; a fresh source poll does not authorise an immediate send. Test clock boundaries and revocation with an approved non-patient account before a new channel is offered.

Stop or change your choices

Suspend licence is available only to the permitted platform role and asks for confirmation. Verify the returned state; saved user choices are retained. A user disconnects their own app separately through Manage and cancel. Stop future affected operations after revocation, preserve unknown outcomes for review, and do not claim previously accepted messages were withdrawn. Hosting or publishing help requires its own approval.