Identify the people and systems
Name the customer decision-maker, technical contacts and the people carrying out the work. Record which systems and environments are in scope.
Security & access
Plan access before making changes
A practical checklist to review with your authorised administrator before a remote project begins.
The exact controls depend on your systems and the written project scope. Use the points below to document the arrangements for your engagement; this page does not claim an independently audited security certification or a particular compliance status.
Agree the access method
Use an organisation-approved remote-access or delegation method. Confirm device requirements, authentication, multi-factor authentication where supported and any customer access policies before connecting.
Limit permissions and duration
Specify the minimum permissions and access window needed for the task. Prefer named, temporary access over shared permanent administrator credentials, and agree who can revoke it.
Approve changes and keep records
Agree the change approval, maintenance window, configuration backup, rollback prerequisites and recording of implementation activity. Confirm whether platform audit logs are available and who retains them.
Control information sharing
Agree the approved channel, purpose, storage location and authorised recipients for any project information. Resolve confidentiality and data-processing requirements before sharing sensitive material.
Close access at handover
Identify credentials or permissions to revoke, return the agreed configuration and validation records, and confirm how any project copies will be returned or deleted.
What belongs in the public enquiry form?
A high-level project description, platform names, approximate scope and timing are enough to start. Do not submit passwords, access tokens, customer datasets, network exports or sensitive internal documents. A suitable secure transfer method must be agreed before confidential project material is exchanged.
Website enquiry data
Online enquiries are recorded in a private inbox on our website server, outside the public website files. Public visitors cannot list or retrieve submissions. Submission references help with follow-up; they are not a password or a public access link. Read the Privacy Policy for use, retention and international processing details.
Procurement and security questions
Tell us if your approval process needs a security questionnaire, confidentiality agreement or data-processing terms. Required documents and any gaps are reviewed before an engagement is approved. Report a suspected website security issue to info@amnet.world, with a high-level description and affected URL. Do not send exploit data or confidential records in the public form.
Discuss your organisation’s requirements
Tell us what your procurement and IT teams need to review before granting access.