IT service terms Remote access acceptable use Lake Charles, Louisiana

Terms of Service

Clear rules keep a remote support setup safe. These terms set the service boundary for Fields & Foster Network and every client using Devolutions RDM, managed support, cloud services, or related IT work.

Read them before you open a ticket or grant access. Use the jump links below to go straight to the parts that affect your team.

Secure office workstation with remote access tools and a policy document on a bright desk in Lake Charles

Security first

Remote access stays inside approved vaults and named accounts.

Plain boundaries

Scope, liability, and termination are written in direct terms.

Fast review

The main points are grouped so your team can check them quickly.

Agreement Overview

This is the working agreement for every service request, support session, and implementation task.

When a client uses Fields & Foster Network services, accepts a proposal, or lets our team work in its environment, these terms apply. They cover IT consulting, network work, software implementation, system integration, data security, cloud services, and technical support tied to Devolutions RDM.

If your team sends credentials, opens remote access, or asks for changes to live systems, you agree to follow these terms. Short version: use approved channels only.

What this covers

  • Support access. Remote sessions, vault use, and named account work.
  • Implementation work. Software setup, integration, and configuration changes.
  • Client acceptance. Use of the service counts as acceptance.

Acceptable Use of Remote Access Tools

These rules keep RDM sessions controlled. They are strict on purpose.

Passwords, vault entries, and session credentials stay in approved Devolutions RDM storage. Send access through secure means only. Never pass logins in email, chat, or plain text notes.

Do not run scans, tests, or penetration work unless it is written into the scope. Keep tools inside the approved task list.

Your internal security rules still apply. If a client policy is stricter than our baseline, the stricter rule controls the session.

The rules are simple.

No shared logins

Each user needs a named identity. Shared accounts make audits harder and are not allowed.

Use approved tools

Only tools agreed in the statement of work may connect to systems or vaults.

Stop when risk changes

If a system looks compromised, halt the session and report it right away.

Keep records clean

Save notes in the agreed location. Do not copy credentials into loose files.

Short answer: keep access controlled, documented, and within scope.

Your Responsibilities

Client-side work matters. If the inputs are wrong, the result will be wrong too.

Give accurate details

Tell us what is in place, what is broken, and which systems are in scope. Use secure channels for credentials only.

Report incidents within 24 hours

If you see a breach, loss, or suspected misuse, tell us within one day so the response can start fast.

Keep software licensed

You are responsible for valid licences on software accessed or managed through RDM and related support work.

If your team cannot meet these duties, pause the work and fix the process first.

Limitations of Liability

This section sets the risk boundary for managed services contract conditions.

Fields & Foster Network is not liable for indirect damage, lost business, or data loss caused by client-side misconfiguration, weak controls, or actions taken outside the approved scope. If a client changes a live system without telling us, that risk stays with the client.

Total liability is capped at the fees paid in the 12 months before the claim. That cap applies unless another written agreement says otherwise.

What this means in practice

Wrong config, wrong result

If a server, firewall, or vault setting is changed on the client side, the outcome can change too.

Fees define the cap

Claims are tied to the amount paid over the prior 12 months. No open-ended exposure.

Scope still matters

Work outside the statement of work needs a fresh approval before anyone starts.

Term and Termination

End the relationship cleanly. That protects systems and keeps the handoff simple.

30 days' notice

Either party may end the agreement with 30 days' written notice.

Immediate breach action

We may end service at once for acceptable use breaches or non-payment.

If service ends, access should be removed, credentials rotated, and outstanding work settled in writing.

Review our full terms

If your team needs a remote access service agreement that fits Devolutions RDM and managed IT support, start here.

Contact Fields & Foster Network

Short. Clear. Written for production work.

Governing Law & Dispute Resolution

These terms are governed by the State of Louisiana, with venue and dispute handling tied to Calcasieu Parish when a written process is needed.

Local contact

225 East Parkway Street
Lake Charles, Louisiana 70607

info@fieldsfosternetwork.com
+13059576591

If a clause needs to change, it has to be written down and signed. Verbal changes do not override this page.