This page explains two methods of limiting access to your web page. The first method explained will be a blanket shield, this can either block everyone on the outside or inside the district from viewing your page. This is the simplest method and can be accomplished in one steep. Simply download one of the following files and place it in the directory you want secured. This file will block all incoming requests, with a simple modification it will block interior requests.

This is what the file looks like:
AuthType Basic
<Limit GET>
order allow,deny
allow from all
deny from 172.18.1.2
</Limit>
To reverse the operation change like this:
AuthType Basic
<Limit GET>
order deny,allow
deny from all
allow from 172.18.1.2
</Limit>
If you get it to work you page should be replaced with this one.

This process is more in-depth and requires an addition to the password file. Use this page to encrypt and add passwords to the password file. Now simply create a file named "htaccess.cfg" and add the following lines:
AuthType Basic
AuthUserFile /intranet/passwd/School Name
AuthName Your Name
require user User name
Edit The text in green the School Name is an abbreviation.
AH = Amelia High
AM = Amelia Middle
GH = Glen Este High
GM = Glen Este Middle
AE = Amelia Elmentary
BE = Brantner  Elmentary
CE = Clough Pike  Elmentary
HH = Holly Hill  Elmentary
ME = Merwin  Elmentary
SE = Summerside  Elmentary
WV = Willowville  Elmentary
WT = Withamsville  Elmentary
Your Name should be self explanatory and username is the name you added to the Password file. Multiple users can be added just leave spaces between each user. If you use "require valid-user" in place of "require user User name" all users in the password file will have access.

Combo secure
 This Combination the two and you should be able to figure it out if you have played with examples above.
AuthType Basic
AuthUserFile /intranet/passwd/School Name
AuthName Your Name
require user User name
<Limit GET>
order allow,deny
allow from all
deny from 172.18.1.2
</Limit>