Use Abe as an individual

Who this is for

This guide is for a person choosing professional information for their own work. You may have personally funded access or employer-funded access; these are separate ways to fund a service. Neither funding route supplies your app permissions or optional alerts.

Start here

1. Choose the service you need in Services and access. You can try the existing professional-development finder directly.
2. Check which services your current account may use. If you need a personal workspace, open My Abe workspace and follow Account contexts. The screen offers Create my personal workspace and confirms Workspace verified; creating it does not buy services. There is no new personal or site selector on that page. The complete individual purchase and cross-host overlap journey is not yet accepted; do not buy again to repair an unavailable module.
3. If an application presents Abe's consent screen, check the displayed application and organisation identifiers, requested permissions and expiry. Select only the access you want, then explicitly confirm it. Decline if the application or purpose is wrong.
4. Select a supported service in that application only after its access is confirmed. Use Abe directly where supported if the host has no accepted connection.
5. Choose optional alerts separately in Alerts. Set your own criteria, timing and offered destination; browsing does not require alerts.

The same person using several hosts should not need to repurchase rights already covered by valid funding. That is the intended purchase safeguard; the complete new self-service journey is not yet a demonstrated customer flow. An employer allocation is not evidence of a payment by you.

Official updates include AHPRA, NMBA, TGA, MBS and Department of Health links and permitted dates, plus PBS schedule and change metadata. Read Source coverage for the recorded checks and remaining gaps. These announcements are not clinical evidence or patient-treatment advice. A working course search does not prove automatic provider refresh, assurance checks or delivery of your selected alerts.

Connect from another application

Abe's own test application is implemented, but its genuine subscriber journey is still unverified. Start with Try the Abe reference application. An authorised member account and genuinely accepted, funded services are prerequisites. The 5 October production check found an active reference registration but no accepted deployment or subscriber grants; registration alone cannot open a service. Sign-in currently uses approved member accounts; these instructions do not promise public account registration.

The universal widget is not ready for general customer release. The preview demonstrates the layout. It cannot connect your account, grant service access or take payment. The following steps apply after the particular application and service pass their access checks. An outside application's developer owns that application's installation and acceptance.

The shared display and connection controls are built and deployed in Abe. That does not establish an accepted, funded service or a successful subscriber connection in another application. Follow the reference application's current prerequisites rather than treating a preview or registration as access.

1. Sign in to the application you normally use. Open its Abe feature or connection page. Each application chooses the location and label; Abe's help does not promise a sidebar button in every product.
2. Choose the Abe features you want, then start the connection from that application. Do not copy a key or paste a preview address into it.
3. Sign in to your own Abe account in the permission window. Check the displayed application and organisation identifiers, requested permissions and expiry. Approve only your choices, or decline. A paid subscription or employer allocation does not approve this connection for you.
4. Return to the original application. Wait for a confirmed connection to the intended account and services. If access is missing, check Billing and service funding before purchasing; the application must recognise independently valid funded access.
5. Open a permitted search, course finder or update feed. Check source links and any coverage limits. An unavailable service should say why; it must not appear as a working feature merely because a package contains it.
6. If you want notifications, open Alerts and choose sources, topics, exclusions, timing, timezone and an offered destination. Preview matches and explicitly activate your choices. You may browse with no notifications. Automatic delivery at your chosen time still needs its complete acceptance test.

You do not need a Stripe account to use these steps. Your owner or employer allocation must be genuinely recorded; ownership of the business alone does not create it. To test a paid subscription, Abe's operator prepares a Stripe sandbox separately. There is no need for a live 100% discount.

For a software owner arranging the connection, send your developer the global Developer guidance and Website widget guides. The developer changes their own application; Abe supplies its service and connection contract.

What success looks like

You see the intended service result or an explicit access limitation. On a permission screen, success means the selected access was approved and appears in your application permissions. A paid receipt, app permission and alert activation need their own confirmation. A successful search does not prove a notification arrived.

If it does not work

Check the application permissions and current funding state before making another purchase. If the service works in Abe but not in a host, use the direct route and ask about that host's acceptance. Missing personal context or employer access needs support, not a different person's sign-in. Use Troubleshooting.

Stop or change your choices

Pause your alerts, disconnect an application or manage paid funding independently in Manage and cancel. Leaving an employer closes that employer's authority. Separate personal access remains only while its own funding and permissions are valid.