Acceptable Use Policy Template: Customize It Step by Step

A new hire emails a client file to a personal account on the second day, intending to finish work at home. The manager wants the file removed, IT needs to assess the exposure, and nobody can find a written rule explaining where client information belongs. That's where an acceptable use policy template earns its place, but only if someone turns it into working instructions. A useful policy names the people responsible, explains permitted behavior, records acceptance, and gives staff a fair process when something goes wrong. Core Clauses Every Acceptable Use Policy Needs An acceptable use policy, or AUP, connects everyday decisions to access permissions and accountability. The NIST Policy on Information Technology Resources Access and Use illustrates that structure through written authorization, restrictions on credential sharing, user acknowledgment, and consequences for violations. Start with the copyable clauses below. Each starter sentence establishes the boundary; the continuation makes it actionable. Before publication, replace role titles with named contacts and complete the policy header with the organization's name, owner, version, effective date, reporting contacts, and review date. Core clauses and what each must cover Clause What It Must Cover Starter Sentence Purpose and scope Why systems exist and who is covered This policy applies to anyone using company devices, accounts or networks. Acceptable use Business tasks allowed, plus limited personal use Light personal browsing is allowed if it does not affect work or security. Prohibited activity Specific banned actions, not vague bans Do not install unapproved software or browser extensions on company devices. Credentials and access Account sharing, MFA and password rules Never share passwords, MFA codes or access tokens with anyone. Data handling Data classes and approved storage locations Customer, student or donor records may only be stored in approved systems. AI and third-party tools Approved AI tools and confidential-data limits Do not enter restricted data into public AI tools without written approval. Monitoring What is logged, who reviews it and retention period Systems are logged for security, and logs are reviewed only by named staff. Reporting Who to notify and how quickly Report suspected misuse to the IT contact within one hour. Enforcement and appeal Staged responses and an appeal route Violations are handled in stages, and users may appeal to a named manager. Acknowledgment Signature, version and date I have read this policy, the version and date shown above, and agree to follow it. Copyable policy wording Purpose and scope. This policy applies to anyone using company devices, accounts or networks. Systems support authorized organizational activities; employees, contractors, volunteers, and other authorized users must follow this policy, including when accessing company information from personal devices. The policy owner resolves scope questions before access begins. Acceptable use. Light personal browsing is allowed if it does not affect work or security. Authorized work takes priority, and personal activity must not create costs, expose information, or disrupt shared equipment. Managers may restrict personal use on operational or student devices. Prohibited activity. Do not install unapproved software or browser extensions on company devices. Harassment, unlawful activity, unauthorized security testing, bypassing safeguards, and disruptive resource use are prohibited. IT must approve software and unusual network activity before use. Credentials and access. Never share passwords, MFA codes or access tokens with anyone. Use assigned accounts, enable required multifactor authentication, and follow IT's password requirements. Managers must authorize access for a defined purpose and duration; IT removes access when that authorization ends. Data handling. Customer, student or donor records may only be stored in approved systems. Follow the data-classification annex when storing, sending, or deleting information. The named data owner must approve exceptional transfers before they occur. AI and third-party tools. Do not enter restricted data into public AI tools without written approval. Credentials and other expressly prohibited data remain barred even when another exception is approved. IT and the data owner must approve services, integrations, and permissions before connection; users must verify AI-generated work before relying on it. For practical language to compare against a team's proposed rules, 1chat's AI usage guidelines for teams provide an additional reference. The organization's own approved-tool list must still determine what staff can use. Monitoring. Systems are logged for security, and logs are reviewed only by named staff. The monitoring annex identifies collected records, authorized reviewers, review purposes, retention periods, and the contact for privacy questions. Any disciplinary use must follow the published investigation process. Reporting. Report suspected misuse to the IT contact within one hour. Stop the activity, preserve relevant messages, and use the after-hours contact for urgent incidents. Suspected credential theft or active disclosure must be reported immediately. Enforcement and appeal. Violations are handled in stages, and users may appeal to a named manager. IT may contain an immediate threat; leadership and HR determine further action after reviewing evidence, intent, impact, and prior incidents. The policy owner records decisions and exceptions. Acknowledgment. I have read this policy, the version and date shown above, and agree to follow it. Questions must be raised with the policy owner before acceptance. The acknowledgment record includes the user's name, signature or electronic acceptance, policy version, and acceptance date. Editing tip: Aim to keep the core policy under about six pages. Move technical configurations, tool lists, and audience-specific instructions into annexes. Save these clauses in an editable document for the organization's template download. Keep the published policy and its editable master under the same owner so changes don't produce competing versions. Adapting the Template for Your Sector One core policy with audience-specific annexes works better than a document that treats a student, volunteer, engineer, and systems administrator as interchangeable. The core sets common boundaries. Each annex explains how those boundaries apply to actual devices, information, and responsibilities. The important distinction is often the user's role rather than the organization's industry. A school's finance administrator needs different permissions from a student using a supervised laptop, even though both follow the same core policy. Sector-specific clauses to add Sector Clauses to Add Example Situation Schools Age-based rules, supervised device use, safeguarding reporting,