From graduate records to a qualification check.
Institutions supply the source. Providers apply independently. OgaPass checks the claim.
Private development environment. Fictional records are for demonstration only. Real partner API access and outgoing synchronisation remain disabled. Independent record approval, ownership checks, protective suspension, independently approved restoration/removal and operations cases are implemented in this review build with database regression coverage. Private qualification update notices, material change holds and redacted audit checkpoint export are also implemented. Browser acceptance across separate staff accounts and remaining pilot readiness controls are still open. Real partner activation is not authorised by this guide.
Which account should I use?
Use your existing application account for the role assigned to you. Institution staff need an explicit membership and MFA. Platform operations needs a separate operations assignment. Creating another ordinary account does not grant either role. Ask your platform administrator to assign the appropriate role through the approved onboarding process.
Access to this private website through ChatGPT and signing into OgaPass are separate checks. Being allowed to open the website does not create an institution membership. This guide does not publish test login addresses, passwords or authenticator codes.
Platform operations
Approves institutional participation, verification authority, service scopes and named staff. Operations access is assigned separately; owning an ordinary provider account does not grant it.
Institution staff
Use their own assigned accounts and authenticator. Supply completed graduate records, maintain sources and review submitted qualifications within their assigned scope.
Provider
Creates an ordinary account and profile independently, adds their service and submits certificate details. No graduate invitation is required.
Customer
Sees the provider’s published, scoped qualification result and its limits. Cannot browse graduate registers or private evidence.
The qualification process
Supply the completed graduate register
Institution staff upload a CSV or enter records with certificate reference, holder name, qualification, service scope, completion outcome and dates. Only completed or passed records can support qualification confirmation. Source freshness and withdrawal matter. A successful upload does not prove ownership of a platform account.
Provider submits their qualification
In the provider app, open My business, then Qualifications and verification. Choose the institution, service and qualification type, enter the certificate reference and relevant details, review and submit. The provider can do this after ordinary signup, without an invitation.
OgaPass checks the claim
The system checks current institution authority, source status, service scope, record details and account ownership. For an individual provider, choose Check current institution register after submission. Automatic ownership matching requires the confirmed account email to match a holder contact supplied from official institutional records and approved by a different administrator, plus a normalised holder name and matching certificate scope, title and dates. A number or name alone cannot grant confirmation. Ambiguous or unbound submissions remain pending for authorised review. Business qualifications use documented review rather than assuming a personal certificate belongs to an organisation.
Resolve an exception
Assigned reviewers request clarification or propose a documented ownership and qualification check. A different current institution administrator must approve a positive confirmation. Use an independently established institutional contact or original source. A claimed name, uploaded file or confirmed platform email alone is not verified identity. An unavailable source means confirmation is pending or unavailable, not that a certificate is counterfeit.
Publish a scoped result
The provider chooses whether to display their qualification. Training confirmation is distinct from practical assessment, registration, licensing and identity checks. Fictional institution results must remain illustrative and must not satisfy real verified qualification filters.
Maintain records and source trust
Corrections, expiry, withdrawals and source or institution suspension can invalidate current confirmation. Preserve the reason and history. Material changes awaiting independent approval hold affected confirmation. Affected account holders receive private updates in Notifications and Qualifications, with the existing request review route. These are in app notices, not email or SMS delivery. Losing trust in an institution does not establish misconduct by every graduate and must not erase their accounts, actual work or unrelated qualifications.
Separate fictional demonstration
Use an assigned fictional institution, one institution administrator, a separate authorised reviewer and an ordinary provider account. Begin with the provider’s independent signup and certificate submission, not an invitation link.
- Inspect a fictional completed register record and its source date. Do not enter real graduate information.
- As the ordinary provider, submit certificate details from Qualifications and verification. A record without an independently approved holder contact must remain pending, even when its number and name match. In Register records, an administrator can propose the official holder contact. A second institution administrator approves the exact proposal from Independent approvals.
- As the provider, run Check current institution register. A matching confirmed email, holder name, certificate details and current authority can establish the supported ownership binding. Otherwise use a documented independent ownership review. The provider result must remain Demonstration or Illustrative confirmation.
- Change, withdraw or expire the fictional source record and refresh the provider result. Current trust must not remain after its supporting authority fails.
- Test the API separately with scoped test credentials and the provider’s temporary approval token. Read access is metadata, not permission to enumerate graduates. Revoke test credentials afterwards.
This independent submission walkthrough is a test plan, not a claim that its browser acceptance is complete. The earlier 9F invitation scenario does not validate it. Direct register ownership matching has database coverage, including name changes and no invitation. Actual external institution connectivity and browser acceptance with separate staff and provider accounts remain open.
Optional invitations to join
An institution may invite graduates to open a OgaPass account. Invitation delivery is separate from qualification eligibility. An invitation alone is not proof of qualification or identity and must not replace the ownership check. Current invitation links are shared manually; automatic invitation email, WhatsApp and SMS delivery are not enabled.
Controls before a real pilot
The required process uses an immutable record proposal and a different authorised approver. Sensitive corrections invalidate the approval, and a single staff institution must wait for independent approval. Operations must be able to investigate attributed events, immediately freeze compromised trust, remove a source and independently approve restoration after fresh checks. The server now stages register commits, source changes, holder contacts, confirmations and incoming API batches as immutable proposals. The submitting person cannot approve their own proposal, and changed versions or revoked membership invalidate approval. Pending single staff institutions need a separately authorised approver. Monitoring includes attributed cases, threshold indicators and approval concentration; these signals are not proof of fraud.
The platform cannot independently prove every training event or prevent institution staff collusion. Monitoring, samples, investigation and conditional participation address that remaining source risk. Real partner activation stays off while the essential controls and acceptance tests are incomplete.