CAP Websites

**Please Note**   Requests for new CAP websites on hold  <-- As discussed with Wing Commanders, PAOs, and ITOs during the Sept. 6-7 briefings on the Wing Website Unification Project, there is currently a hold on establishing any new websites at the wing or unit level.

Wing Website Unification Project
Support Materials

Project guidelines and FAQ are located in the right-hand menu as a download.

• FAQ Updates (See FAQ for details)

  • (Updated 09/04/25) G-1 - Are wings/squadrons required to convert to the new template?

  • (Updated 09/04/25) G-2 - Are squadrons allowed to have websites?

  • A-5 - Where can I put information about the wing staff on the website?

  • L-3 - How do I embed a map to showcase all the squadrons/units in my wing?

  • L-8 - Can I put my squadron’s unit emblem on the wing website?

  • L-9 - Can the wing website include historical details for the wing and squadrons?

  • (Updated 08/17/25) A-6 - How do I set up a Google Workspace for our squadron-specific, wing-specific, and region-specific emails and member-only areas?

  • (Updated 08/27/25) L-10 - How do we add donation buttons to the squadron landing pages?

  • (Updated 09/05/25) IT-8 - May squadrons have vanity domains?

• To begin your wing website conversion to the consolidated template, please email capwebsites@capnhq.gov and copy macstaff@cap.gov to be assigned a MAC SiteViz team member.

• SiteViz Tutorial – Google Calendar Walkthrough. Here

• FAQs:   Information on the new wing donation module on the wing websites can be found here

Email capwebsites@capnhq.gov with macstaff@cap.gov copied with questions.

Google Workspace Requests
 

Procedure For Requesting
The CAP IT Security Manager has directed that squadrons, wings, and regions may have their own independent Google Workspaces, separate from each other. The following procedure outlines the process for requesting new independent Google Workspaces for a squadron, wing, or region. Squadrons with existing Google Workspaces are not required to shut them down if their wing stands up a Workspace. Likewise, wings with existing Workspaces are not required to shut them down if their region stands up a Workspace. Existing Workspaces from all echelons are not required to go through reapproval.

Request Process:

1. Documentation of commander review and approval for the echelon requesting the Google Workspace. For clarity, squadrons require squadron commander approval, wings require wing commander approval, and regions require region commander approval.
    

2. Submit an IT ticket under the category “Google Workspace and Social Media Requests” with a copy of the unit commander’s approval attached to the request.
    

3. Once IT approval has been received, you can proceed with requesting a Google for Nonprofits account through Google.
    

4. As you work through the Google process with Goodstack it will ask for the EIN to be verified. Go back to your IT ticket and update it to indicate that an EIN verification will be processed. (Please note : You’ll need to set your ongoing helpdesk ticket to “In Progress” to prevent it from automatically closing.)
    

5. Once IT approves of the EIN use, continue with the Goodstack setup. When Goodstack asks you to prove you own the domain, update the IT ticket again with the DNS txt records provided by Goodstack.
    

6. Continue the Goodstack setup.

Updated: 10/31/25RV