In this example, Ken is the person who will be creating, maintaining, and sharing the list; Marion will be able to send messages to the list, but she will not be able to see who the members of the list are.

1. Ken creates a new Contact Database on his Desktop and gives it a meaningful name, in this case, "Ken's Shared Contacts":
   
   

2. He opens the newly-created contact database and makes a New Mail List within it:
   

3. He names the list and adds members to it (note as per Cam: "Whoever is making the list for the school, it would probably be a good idea to preface each list with "Ray" or "HHS" etc. Then, when you go to compose a message, you can see all the shared lists specific to your school. E.g. I might make "Ray 3rd" "Ray Sp. Ed" etc...then when I go to send a message, I can just start to type "Ray" and then choose from all the shared lists, without knowing the exact name first.")
   

4. He closes and saves. Now, back on his Desktop, he clicks once on Ken's Shared Contacts to select it, then goes to the Collaborate menu and selects Permissions:
   

5. Recall that, for this example, he wants Marion to be able to "use" his contacts, but not to see who the individual list members are. So, in the permissions dialog, he enters her name, and from the Access popup menu, he selects View List.
   

   Note that if he wanted to allow Marion to use his shared contact entries AND to see the actual recipients that his contact entries correspond to, he would select Open Items. If he wanted Marion to be able to do both of those things AND be able to make edits as well, he would select Creator. In that last case, any changes Marion makes to any of his entries would also be reflected in his copy, and in anyone else's that he gave access to. In other words, they would stay in sync.

6. Now, Ken has created the database, created a list within it called 9th Grade Parents, and set the permissions for the people he wants to share it with. There is still one more step -- at this point, Marion cannot yet "see" the database. So, in that Permissions dialog box, Ken clicks the Subscribers button, which brings up a subscribers list with his name in it. Right now he is the only subscriber, i.e. the only person with the icon visible on his Desktop. He now needs to add Marion as a subscriber, so he clicks the Add Subscriber button and finds her name in the directory, OR, as Cam points out, he can drag them from the Permissions window into the Subscribers window -- much easier if you have a long list of people.
   

   Once she is added, her Desktop will acquire a new, randomly-placed icon of his shared contacts database. She has to do one thing before she can use it (details below).

7. The last step is important. Ken must drag the shared contacts database into his main Contacts before he will be able to send messages to any of the recipients within it.

   Marion must likewise drag HER copy of his shared contacts database into HER main Contacts before she can use them.

   

8. Now, either Ken or Marion can create a new mail message addressed to "9th Grade Parents." No one else on the server can see that list or use it, and only Ken can see and control who is actually on the list.