TAC HRTAC HR
A scene from a Saudi workplace
HR templates

IT Resources Acceptable Use Policy Template

Most data incidents in small companies are not made by a skilled intruder. They come from a password written on a slip of paper, an account shared by three people, or a lost personal phone that held employee files. This policy writes down what is allowed and what is not on the company's devices, accounts and data, who is told when something looks wrong, and what happens to the accounts of someone who leaves. It is guidance to adapt to your company's set-up and is neither legal advice nor a full information security document.

Last reviewed
On this page

01What an acceptable use policy is for, and who it covers

The policy answers an everyday question: may I do this on my work computer? The employee finds the answer written before he acts, and the manager has something to rely on when he objects. It is not a technical policy for network engineers but a paper every employee can follow, suitable for a company of five or of fifty.

The IT function, or whoever does its work, writes it with HR and the authorised body approves it. It applies to everyone who uses the company's devices, accounts, network or data, whether employees, contractors or trainees, and to personal devices whenever they connect to company data. It connects with the code of conduct, the confidentiality and social media policy and the custody policy.

02The acceptable use policy text and the commitment form

[Company name]
IT resources acceptable use policy
Version: [number]      Effective date: [date]

1. Purpose and scope
1. This policy sets the acceptable use of [Company name] devices, accounts, network and data.
2. It applies to anyone who uses these resources or reaches their data from any device.

2. Accounts and passwords
1. Every user has an account in his own name, shares it with no one and does not use anyone else's.
2. A password is secret: it is not left in view or sent in a message, and it meets [minimum length and complexity].
3. A password is changed every [__] days, and at once if exposure is suspected.
4. The user locks his screen whenever he leaves his device.

3. Devices and software
1. Company devices are for work; limited occasional personal use is allowed so long as it does not harm the work or security.
2. The user does not install software without the approval of [authority] and does not disable protection software.
3. A personal device that connects to company data meets the conditions of [passcode lock, encryption and updates], and the company may ask for its data to be deleted from it when service ends.
4. Company data is not moved to external storage media or personal cloud accounts.

4. Email, internet and messaging
1. Company email is used for work and not to register for services unrelated to the work.
2. The user does not open links or attachments from an unknown source and reports suspicious messages.
3. Browsing or downloading anything contrary to law or public decency, or that endangers the network, is forbidden.

5. Data protection
1. Customer or employee data is not entered into external tools or unapproved artificial intelligence applications.
2. The user does not reach data his work does not require, even if the system allows it.
3. Sensitive documents are printed only when needed and destroyed after use.

6. Monitoring
1. The company keeps logs of the use of its systems and accounts for security and audit purposes, and the user is told so when he signs this policy.

7. Reporting incidents
1. The user reports at once the loss of a device, a suspected breach of his account or a data leak, on [channel] within [__] hours.
2. The user does not hide an incident for fear of punishment; early reporting limits the damage and is taken into account.

8. End of service
1. The employee's accounts and permissions are switched off at the end of his last working day, and he returns his devices and files under the custody policy.

9. Breach
1. A breach of this policy is dealt with under the company's approved disciplinary ladder and may lead to permissions being suspended immediately.

Approval
[Approver's name and title]      Signature: ________      Date: [date]

--------------------------------------------------

Commitment to the acceptable use policy

I, the undersigned, acknowledge that I have read the IT resources acceptable use policy of [Company name], version [number], and understood it, and undertake to comply with it, and I know that logs of the use of the company's systems are kept for security and audit purposes.

Name: [employee name]      Employee number: [number]      Signature: ________      Date: [date]

03The policy clause by clause

Clause 2: one account per person

A shared account erases responsibility: when a figure changes or a file is deleted nobody knows who did it. The clause forbids sharing absolutely, even between two colleagues one of whom trusts the other, because trust proves nothing in a log.

Clause 3: a personal device on conditions

Do not ban every personal device, or employees will get round the ban, and do not allow everything, or you lose your data. Require for connection to company data what you can check: a passcode lock, system updates, and the ability to delete the company's data on leaving.

Clause 5: external tools and artificial intelligence

Copying customer data into a free tool on the internet takes it out of the company's custody with no way back. Keep a list of approved tools and write that personal or commercial company data is not entered into any other.

Clause 6: monitoring that is announced

Monitoring the employee does not know about loses trust and weakens any reliance on it. Write that the logs are kept, that the employee's acknowledgement covers knowing so, and go no further than security and audit need.

Clause 8: switching off an account at a fixed hour

A leaver's accounts are a risk that does not appear on handover lists. Tie their suspension to the end of the last working day and not to a date the company decides later, because the gap between leaving and suspension is the longest stretch of danger.

04A worked example: switching off a resigning employee's account and the next password change

An employee resigned on a monthly wage of SAR 7,000.00, giving notice on 2027-05-04. The notice period function puts the employee's notice at 30 days, so his last working day is 2027-06-03 (Thursday), when his account and permissions are switched off at the end of the day and he returns his devices.

ItemValue
Date of notice2027-05-04
Length of notice30 days
Account suspended and permissions withdrawnEnd of 2027-06-03
Last password change2027-01-04
Change cycle in this example90 days
Next password change2027-04-04 (Sunday)

So the password change on 2027-04-04 falls before he leaves and is carried out as usual; any change after it lapses when the account is suspended, and the IT officer checks that the suspension was carried out on time. The dates and the change cycle are illustrative inputs, and the last working day comes from the notice period function on our site.

05When not to apply this policy

Customer systems and anything run by others

A system owned by a customer or a government body is governed first by its owner's conditions, and this policy still applies to whatever does not conflict with them.

Advanced security for large organisations

The security policy of a data centre or of a specially regulated body is wider than this template and is supplemented by separate technical annexes.

Purely technical decisions

Choosing antivirus software and the method of backup is a technical decision for the IT function, and it is not written into this paper that every employee reads.

06Hard cases and common mistakes

A colleague who runs an absent employee's account

This is the most common case and it starts with good intentions. Define the approved substitute: a written delegation with temporary permission instead of sharing a password.

An employee who uses his personal phone for work photographs

Photographs may hold customer data or site details. Ask for them to be moved to the company's storage and deleted from the personal device, and write that into the conditions.

A sudden resignation with no notice

The account is suspended from the moment the decision to end the relationship is taken, not from a nominal last working day, and the direct manager and the IT function set the right time by written decision.

Common mistake: a long policy that nobody reads

A forty-page paper is not respected. Keep it to two pages and refer technical detail to annexes that not every employee is asked to sign.

Common mistake: punishing someone who reports his own incident

If a person who reports the loss of his device is punished, nobody reports afterwards. Write that early reporting is taken into account.

07Steps to adapt the policy to your company

  1. 1

    List the systems, devices and accounts

    Write down what the company owns: devices, email, the HR program, the accounting systems, and who holds permission on each.

  2. 2

    Pick password conditions your staff can live with

    Conditions that are too hard drive people to write them on paper. Choose a reasonable length and a change cycle the company really keeps.

  3. 3

    Approve a list of permitted tools

    Gather what the team actually uses, approve what is suitable, and name who approves a new tool.

  4. 4

    Tie account suspension to the exit procedure

    Put "suspend accounts" in the leaver's handover list, with the name of who does it and the time.

  5. 5

    Collect the acknowledgement and renew it

    The employee signs on joining, and the signature is renewed with every material change to the policy or on the cycle the company sets.

08Acceptable use policy checklist before approval

9 items

09Frequently asked questions

  • Limited occasional use is allowed in the template so long as it does not harm the work or security, and the company narrows or widens the limit according to the nature of its work.

  • The company keeps logs of the use of its systems for security and audit purposes, and the employee is told so plainly when he signs the acknowledgement.

  • You report on the set channel at once so access can be closed and the passcode changed, and then the question of deleting the company's data from the device is considered.

  • No. The approved substitute is a written delegation with temporary permission, and the password stays with you alone.

  • At the end of your last working day, under the policy. The notice rules are on the notice period page.

  • When it connects to company data, the written conditions for such devices apply to it, and nothing else.

Related pages

Inside TAC HR

IT resources in TAC HR

In the attendance service an employee's account in the app is bound to one device; if the account is opened from a new device sign-in is refused and a dialogue sends a change-of-device request to management, and a punch from a rooted phone or an emulator is rejected and management is told of the attempt. Under "Establishment settings" («إعدادات المنشأة») and then "Users" («المستخدمون») you invite a new administrator, resend the invitation and disable an account with the "Disable" («تعطيل») button, and permissions are distributed in "Admin groups" («المجموعات الإدارية») by branch and department scope, so a user sees only what his group allows. The "Establishment activity log" («سجل نشاط المنشأة») records who did what and when across the modules, filtered by module and date. In the document archiving service a "Confidentiality agreement" («اتفاقية سرية») can be kept among the employee's documents, and in the employee requests service a device handed over is recorded as custody and the employee acknowledges receipt from his phone. Other templates are on the templates page.

  • Attendance — An attendance system that records every punch with its time, place and source
  • Employee requests — An employee request system with an approval route per request type and a leave balance checked before approval
  • Document archiving — Employee and company document archiving with expiry dates and a reminder before every renewal