Open NOID for Web

  1. Start from the official https://www.aieng.co.za/ homepage and select Open NOID for Web.
  2. Use a current browser with ordinary site storage enabled. A private-browsing window can discard installation state when closed.
  3. Follow the on-screen PIN and device review. Keep the PIN private and do not send it to support.
  4. Wait for the connection badge to show Online before starting a call or expecting immediate delivery.
  5. Record the eight letters and numbers shown after NOID-. That is the address compatible users enter to reach this installation.

If an installed PWA reopens an older version, use the in-app update check, refresh the browser page once, then fully close and reopen the installed app.

Sign in to the account area

Select Account on the public website. Enter exactly the eight characters after NOID-, then the four-digit PIN. The identity entry is not case-sensitive, but every letter and number must be present.

The account area provides private activity and settings. It is intentionally excluded from search indexing and advertising because it is a utility screen rather than public publisher content. If the account reports an unknown identity, confirm that the client and website show the same address and that you did not open a different browser profile.

Repeated unsuccessful attempts can trigger a temporary rate limit. Wait for the displayed interval instead of repeatedly retrying. If a changed PIN is forgotten, use the supported recovery process rather than sharing device credentials with anyone.

Groups, invitations and shared plans

Open More, then Groups to create a shared space or respond to an invitation. Check the inviting NOID and group description before accepting. A recipient is not a member until the invitation is accepted.

  • Invitation not visible: confirm both clients show Online, verify the invited NOID character by character and allow protected messages time to deliver.
  • Calendar change missing: confirm the person accepted the group and reopen the group Calendar after reconnecting.
  • Notice Board update missing: keep the client online briefly and check that the post belongs to the intended group.
  • Wrong member or role: ask the group administrator to review the member list and group controls.
  • Geofence needs correction: use Clear before accepting an incorrect draft, or Edit to move the boundary points later.

Group membership does not automatically disclose location. A geofence presence check remains permission-based, and a member can decline or be unavailable. See the Groups Guide for the full interaction model.

Hotel, office and guest Wi-Fi

Guest networks often use a captive portal. A device may show a Wi-Fi connection even though normal internet access has not been granted. Open a conventional HTTPS webpage, complete the venue’s terms or room sign-in, and verify that several ordinary sites load before reopening NOID.

If browsing works but calls do not, the network may restrict real-time media, long-lived connections or background traffic. Confirm that text delivery works, disable battery-saving restrictions for the client where appropriate, and try an approved alternative connection such as mobile data. Do not attempt to bypass venue security controls.

Moving to another network does not change the NOID address. The connection is only the route to the relay.

Troubleshoot a call

  • No outgoing audio: check the selected microphone, browser permission indicator, operating-system input device and hardware mute control.
  • No incoming audio: check speaker output, volume, Bluetooth routing and whether another application holds the audio device.
  • Recipient unavailable: verify both clients show Online and compare every character of the recipient address.
  • Call starts then drops: note the time, duration, client versions and whether either connection changed. Test a stable network before reporting a relay fault.
  • Permission denied: reopen site permissions in browser or Android settings, allow the microphone for a deliberate call, then retry.

NOID cannot place an emergency call or guarantee access to public telephone networks. Keep a conventional emergency method available.

Troubleshoot a message

A message can remain pending while the sender or recipient is offline. Keep the sending client open briefly so it can retry, confirm both connection indicators, and avoid repeatedly sending the same content. Check the recipient address before assuming a delivery fault.

Attachments have size and type limits. If a file fails, try a smaller supported file, confirm the browser can read the selected file, and check that security software is not blocking the upload. Do not rename an unsafe executable to disguise its type.

The relay records delivery metadata but the administrator message register does not display encrypted message text or attachment contents. A useful support report therefore includes timestamps and status—not a copy of the private conversation.

Location and map features

Location permission is requested only when a feature needs a position. Open the relevant feature, respond to the protected browser or Android prompt, and wait for the device to obtain a fix. Indoors, GPS can be slow or imprecise.

If a map is blank, check the normal internet connection, content blockers and whether map-tile requests are allowed. If a geofence is inaccurate, move to a clearer location and wait for the reported accuracy to improve before saving the boundary.

A location intentionally shared with a selected recipient can be read by that recipient. Review the destination and stop tracking when it is no longer needed.

Updates, downloads and support reports

Browser clients use a service worker and can temporarily retain an older cached version. Use Check update, refresh once, and reopen an installed PWA. Android users should compare the installed version with the official Downloads page and install only an authentic NOID package.

A good support report contains the approximate date and time, NOID client version, browser or Android version, connection state, feature used, expected result, actual result and short reproducible steps. Screenshots should hide other people’s identifiers and private content.

Never include: a PIN, private key, installation credential, full private message, another person’s location or a confidential attachment. Registered users can submit an account-linked report through Contact AIEng.

Advertising disclosure: this public help article may carry Google AdSense advertising. Private account and support forms do not. Ads are separate from troubleshooting instructions and are not a recommendation to install third-party software.