Discourse thread at https://yo.atxhs.org/t/revamping-our-internal-systems/300
The vision – all admin interactions with account(s) occur through the LDAP. LDAP is the source of truth for all member info including active billing, B-share, contact info, etc (i.e. admins do not directly interact with subsystems like Freshbooks to update accounts). Accurate info, easily accessible.
The needs described in this project have been largely satisfied by our new member management system Neon. Work is now being redirected to Neon API integrations to achieve the workflows shown below.
Check out the Neon Integrations repo here for the latest developments.
Here's what the basic workflow would look like for the base model created which we can build further upon.
Link to Google drawing here
- Accounting system for membership dues (Stripe used for payment processing)
- API docs
- Uses OAuth for authentication
- Forum for member discussion
- API docs
GETcalls only require API key and API user in headersPOSTcalls require API key, API user, and content-type in the headers- See verified example scripts in
/examplesdirectory
- Scheduling system for booking time at the space
- Checked with CSM about API, they have integrations through Zapier, but no direct access endpoint. May be able to reverse engineer to figure out endpoints and methods
- Email service for updates
- API docs
- Used for access into the space
- We will need to research how to interact with this system
This is an open-source project for ATX Hackerspace. Keep any API tokens or other private information stored in the /private directory which is ignored by git. If you are interested in working on this project with us, please reach out to it@atxhs.org.