Greetings all,
Below is a short line item description of some of the web-based admin things I’ve been dealing with over the years. I don’t expect us to go over this thoroughly during the board meeting. The main point is that the Board needs to decide how to handle/transfer these responsibilities in due time. This could be a local website management firm or another volunteer.

Google admin access and setting privileges: admin.google.com
Years ago, we signed up FYA for a Google Business account and applied for the non-profit status, which allows the organization to create emails for users without charge. All of the user access information is controlled through the Google Admin portal. User privileges for accounts, etc. The current accounts listed as super admin are:

• info@fairbanksyouthadvocates.org (named Executive Director)
• patrick@
• marylee@
• brian.taylor@

Keep in mind that since I had retained super admin privileges on the account, I could log in and restrict Alnise email access privileges. Technically, I probably should not have had access since I was no longer on the board. But in the end, I’m glad I did.

General Logins for Admin accounts
We set up info@fairbanksyouthadvocates.rog for long-term logins on various accounts, like banks, subscriptions, hosting, etc. That way, it would supersede the various changing positions. Much of this has been reviewed over the past 6 months as Rodney and Marylee worked through the aftermath of Alnise. I think it would be helpful to have a list of sites that use this email. Like Credit cards, banks, subscription services, etc.

Stripe account (login and access)
Stripe is the merchant account service used on the FYA website to receive credit cards. Access to this account has been shared with patrick@alaskaphotographics.com, and I can log in and see all transactions. (I’m not positive of the other access account. It should be info@fairbanksyouthadvocates.org (Marylee, can you advise on this?) It is currently set up to charge daily but send weekly deposits directly into the FYA bank account.

FYA related Websites
I have been managing the backend of these websites while absent from the board, although much of the content has not been refreshed since Alnise took over. I made several requests to sit down with her and go through the site to ensure everything was current. This never took place for several reasons. Backend admin issues include updates to the new version of WordPress and plugin updates. Each site utilizes various plugins for different functionality, and these need to be updated, so everything operates smoothly.

• Public site
  • Needs an overhaul, but I’ve done several fixes over the past few months. Donor information is stored in the admin portion of the website and reports can be run directly from there if needed. Subscriptions to recurring donations are also managed through the backend.
• Private Board site
  • I recently changed the Word Press theme which resolved the problem with comments not showing. I also updated a few of the outdated pages, although this site also needs a review for functionality. The board needs to decide how they want to use it. I’ve noticed that email has become a common means of communication. This is fine, however decisions need to be made in either in meetings or on the board website.
  • Adding and changing user privileges for new and outgoing board members.
• Clearwater site
  • Needs to be rebuilt with new branding when ready.

Mail chimp interface for digital newsletters (login info uses info@fairbanksyouthadvocates.org
Mailchimp is used to store the mailing list and send out digital versions of the newsletter. Building the newsletter in Mailchimp is not difficult. I’ve been doing it, but someone else should take this over in the future. I’m willing to provide tutorials on this.

Website hosting options (currently Bluehost, but an alternative may be better due to speed issues)
We use Bluehost to host FYA (that is, pay a monthly parking fee). Bluehost is cheap, and so is the performance of their hosting service. However, it may be sufficient for us. The admin gets real clunking on Bluehost. If it becomes intolerable, the site can be moved to another hosting company.