Historically, we have worked to store this information in our CRM (Groundhogg), and I think we should continue that practice.
A couple of related ideas came up from this. First, Nathalie wants to continue to use Asana as a workspace for processing membership-related workflow tasks. As long as we are continuing to encourage the use of Asana for task management in general, I think this makes sense. Also, the folks discussing the operational work around being Membership Coordinator wanted to encourage the use of (Google) spreadsheets for intermediate processing of data, but not as an archive.
How does this all land with my fellow @IT-Circle folks?
I support this standardization. Are there members who don’t have that information on the CRM? A big piece is that we can see you has active membership on woocommerce memberships.
I also wonder about SoPra membership model and how it relates to this.
Staff members who don’t know about our use of our CRM for tracking membership itself? I think it’s possible. I think we still have a fair amount of work to do to ensure that staff members are properly oriented.
My main reason in submitting this backlog item, though, was to clearly establish this policy. I’ll follow up with a formal proposal soon.
I think maybe I need more orientation on how we use woocommerce memberships.
That makes sense. Although I think most SoPra members are SoFAN members but not staff members, so this initial work around staff membership may not be immediately relevant.