Once a yearBoard turnover: accounts, access and keys
Once a year
Board turnover: accounts, access and keys
When an officer or editor changes, accounts and keys must move with the role, not stay with the person.
Before you start
- The person leaving and the site owner, together
- A password manager to hand over the shared PTSA login
Steps
- The person leaving lists every account they hold: Webflow, Brevo, Gandi, the composer, the Chatter Google Forms and any @cherrycrest-ptsa.org mailbox.
- Shared PTSA account: Webflow, Brevo and Gandi should belong to one PTSA role address, not to a person. If the composer is hosted, its Cloudflare and GitHub accounts belong to it too. Change its password and recovery details, and hand them over in person or through a password manager, never in an email. TBD whether the role address is created and what it is.
- Webflow: editors share one login, so nothing is added or removed per person. Instead, change the shared password whenever someone who knew it leaves, and share the new one with the people staying.
- Brevo: change the shared password the same way. Update the sender name or reply-to address if they name a person.
- Composer: update the list of people allowed to sign in. How depends on where it runs: TBD.
- Gandi: point role addresses (president@, editor@ and others) to the new people, and check the domain's renewal date and payment card. The domain is renewed every year; the current term ends Nov 2, 2027.
- Keys: the composer uses a Webflow key and a Brevo key that belong to the PTSA account. Never copy them into email, chat or documents. If someone who had them leaves, ask the technical helper to make new keys and cancel the old ones.
- Update the Leadership page (steps).
Screenshot to add
If the domain lapses, everything stops. The website and every @cherrycrest-ptsa.org mailbox depend on it. Whoever holds the Gandi login must keep the renewal and card up to date.