NFGCONNECT
TRUST / ACCESS CONTROLS

Connected.
With your permission.

Access controls are part of the support workflow, from account enrollment to stopping a session.

Identity before access

The website uses verified NFG account sign-in. An administrator-issued enrollment code links a member to their assigned role. An email record or software download alone does not grant access.

The right role for the job

Each person signs in with their own identity. Customers see only their own computers and support requests. Technicians see only assigned work. Company administrators manage their own company’s members, computers, assignments and administration logs. Other company data remains private. Only the website owner has global oversight. Choosing a role on the setup page never changes account permissions.

Approval on the customer computer

Screen viewing, remote control and file transfer are selected independently. The customer reviews requested permissions locally, and a separate confirmation is required for live testing.

USB has its own checks

A selected USB device needs separate approval and transport setup. Relay connections use TLS terminating at the relay. The relay and its operator are part of the trust boundary; this is not a claim of end-to-end encryption.

Stop and revoke

Use local Windows Stop controls to stop live access. The console can withdraw NFG approvals and revoke sessions. Separate helper programs or Microsoft RDP sessions may also need to be stopped locally.

Preview limitations

Remote features are experimental. Release signing, relay deployment and physical Windows/device qualification must be verified for the specific environment. The website does not certify safe ECU programming.

NFG News — features, updates and community voices