https://wiki.asmbly.org/api.php?action=feedcontributions&feedformat=atom&user=JonAsmbly Wiki - User contributions [en]2026-04-29T02:14:50ZUser contributionsMediaWiki 1.35.8https://wiki.asmbly.org/index.php?title=Meetings&diff=4117Meetings2026-01-12T06:37:00Z<p>Jon: /* Stewards Meeting */</p>
<hr />
<div>There are a number of standing meetings at Asmbly. <br />
<br />
==Community Social Hour==<br />
The Asmbly community social is open to all and usually occurs on the first Wednesday of every month. There's no business agenda.<br />
==Leadership Meetings==<br />
The Executive Director (or delegate) holds monthly meetings of operational leadership (Directors, Shop Area Leads, managers) to discuss issues relevant to the day-to-day operation of Asmbly.<br />
<br />
==Board Meetings==<br />
The Asmbly board meets on the second and fourth Wednesdays of every month. These can be virtual or in-person. Email board@asmbly.org for details if you'd like to attend. Minutes can be found in [https://drive.google.com/drive/u/1/folders/1izGozNaR1nJrbMZfT-XMzEZSffJKgcq5 Google Drive]<br />
<br />
[[Category:Operations]]</div>Jonhttps://wiki.asmbly.org/index.php?title=Trinco_300_Abrasive_Blaster&diff=3699Trinco 300 Abrasive Blaster2025-07-25T01:56:53Z<p>Jon: </p>
<hr />
<div>{{boneyard}}<br />
The Trinco 300 abrasive blast cabinet with media recirculator is found in the fabrication area.<br />
<br />
<br />
Please don't add or change the abrasive without talking to a steward first.<br />
<br />
{{ToolPhoto|BlastCabinet.jpg}}<br />
<br />
{{Hosted|Joe Ngo}}</div>Jonhttps://wiki.asmbly.org/index.php?title=Internal_Network&diff=3680Internal Network2025-07-18T19:31:11Z<p>Jon: </p>
<hr />
<div>In the past year we've embarked on a project of simplifying the network infrastructure of the space. As of now (January 2022) we've reduced about as much as we're going to and replaced anything left that exceeded our jankiness tolerance, so we're mainly in maintenance mode.<br />
<br />
==== The Mini-Rack ====<br />
The 9U wall-mount rack in the multipurpose room (nee Lounge) is the new core of the Asmbly network. It contains an UPS, a 48-port patch panel, our Spectrum Business cable modem/router contraption, the Unifi Dream Machine Pro that manages our network, a Unifi 48-port core switch, and a Unifi 24-port POE switch to power APs, cameras, and miscellany. <br />
<br />
==== WiFi ====<br />
Asmbly WiFi is provided by six Unifi UAP-AC-Lites.<br />
* One's in the multi-purpose room over the textiles door<br />
* Two are mounted on ceiling beams roughly centered over the eastern and western halves of the woodshop area<br />
* One's mounted on a ceiling beam roughly centered in the metal shop<br />
* One's mounted on a ceiling beam roughly centered in ceramics<br />
* One's perched in the wall rack in the new lobby. It should be mounted on the ceiling one of these days.<br />
<br />
==== Sub-switches ====<br />
* The "Expansion" Switch<br />
** The new lobby has a wall rack containing a US-24-POE-250W supporting equipment in the 302 expansion area.<br />
* The Shop Switch<br />
** The storage loft has a USW-24-POE and UPS mounted on the wall, mainly to support cameras.<br />
* The 3D Printer Switch<br />
** The 3D printer area has a USW-Lite-16-POE supplying equipment in that area<br />
<br />
==== OpenPath ====<br />
The [[Openpath]] (now Alta Open) cabinet controlling the 304 doors is mounted under the mini-rack. There's another near the wall rack in the new lobby controlling the 302 doors.<br />
<br />
[[Category:Operations]]</div>Jonhttps://wiki.asmbly.org/index.php?title=Category:Policies&diff=3678Category:Policies2025-07-18T17:41:26Z<p>Jon: added link to bylaws etc</p>
<hr />
<div>This category contains Asmbly's operational policies. Many of them are also included in the [[Member Handbook]].<br />
<br />
Asmbly's governing bylaws and policies adopted by the board maybe be found in our public [https://drive.google.com/drive/u/1/folders/1d6pFaw7LAfkfgCCxQQfldOosOEJSG0v9 Google Drive].</div>Jonhttps://wiki.asmbly.org/index.php?title=Category:Policies&diff=3677Category:Policies2025-07-18T17:36:39Z<p>Jon: removed "board adopted"</p>
<hr />
<div>This category contains policies that have been adopted by Asmbly. Many of them are also included in the [[Member Handbook]].</div>Jonhttps://wiki.asmbly.org/index.php?title=MediaWiki:Sidebar&diff=3675MediaWiki:Sidebar2025-07-18T17:35:51Z<p>Jon: Added link to policies</p>
<hr />
<div><br />
* navigation<br />
** https://asmbly.org | ASMBLY Homepage<br />
** https://yo.asmbly.org | ASMBLY Discourse<br />
**Category:Policies | ASMBLY Policies<br />
**Member_Handbook|Member Handbook<br />
**https://asmbly.org/classes/ | Upcoming Classes<br />
**Special_Interest_Groups | Special Interest Groups<br />
**Tools|Tools in the Space<br />
**Category:Operations|ASMBLY Operations<br />
<br />
* Wiki<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
<br />
* SEARCH</div>Jonhttps://wiki.asmbly.org/index.php?title=Privilege_Management&diff=3382Privilege Management2025-02-26T18:23:56Z<p>Jon: </p>
<hr />
<div>Asmbly has a evolved a simplified set of privilege groups that describe an individual's characteristics with respect to the organization. These are all managed via Neon, but membership in some groups is inferred from other account attributes.<br />
<br />
Note that a Neon account may have more than one type, and a Discourse user may be in multiple groups.<br />
<br />
=== Subscribers ===<br />
Any Neon account with an associated Membership record with a start date <= today, an end date >= today, and a successful payment is an Asmbly subscriber. When that payment is greater than $0 the subscriber is paid, otherwise the subscriber is comped. Paid and Comped subscribers have identical behavior in all Asmbly systems except for our daily ledger counts. Note that paid memberships might have been paid by gift certificate.<br />
<br />
* Subscribers are added to the "Asmbly Makers" group on Discourse.<br />
* Subscribers who have completed orientation and signed the waiver are granted access to the general areas of the Asmbly facility during normal operating hours. See the [[Openpath]] page for more information.<br />
<br />
''Note for Neon backend users: The results of a Neon default filter for subscribers will return accounts whose membership records have failed payments, e.g. auto-renewals on expired credit cards. Asmbly does not provide a grace period to subscribers with failed payments.''<br />
<br />
=== Ceramics Subscribers ===<br />
Folks who've paid for a Ceramics-tier membership and completed Ceramics Studio Introduction have access to the Ceramics area in addition to the rest of the shop.<br />
<br />
* Ceramics Subscribers are added to the "Asmbly Makers" group on Discourse.<br />
* Ceramics Subscribers who've signed the waiver and completed orientation and CSI have access to the main shop areas and the Ceramics studio during normal operating hours.<br />
<br />
=== Secured Tool Access ===<br />
Some tools at Asmbly are access-controlled. Subscribers who have completed the access prerequisites for these tools will be granted access. This is typically indicated in Neon by a "class completion date" field for that tool, with OpenPath access to the tool being granted when the class date is filled in.<br />
<br />
=== CoWorking Tenants ===<br />
CoWorking Tenants are Subscribers who rent a cube in the [[CoWorking]] area.<br />
<br />
* CoWorking Tenants have access to the CoWorking area.<br />
* CoWorking Tenants have a short grace period on failed subscription renewal payments. <br />
<br />
=== Stewards ===<br />
A Subscriber with the "Steward" account type is a Steward. You can read more about being a Steward in the [[Stewards Guide]].<br />
<br />
* Stewards are added to the "Stewards" group on Discourse.<br />
* Stewards have access to Stewards' storage areas at Asmbly.<br />
* Stewards are allocated additional booking hours in Skedda.<br />
<br />
=== Instructors ===<br />
A Neon account with the "Instructor" type is an Instructor. Note that Instructors need not be Asmbly subscribers, but as of now there's no official process on granting non-subscriber instructors access to the facility for their classes.<br />
<br />
* Instructors have access to Instructors' storage areas in Asmbly.<br />
<br />
=== Super Stewards ===<br />
"Super Stewards" or "Supers" are Stewards with Director-level facility access permissions. This access level is to some extent subjective, but generally include longtime area leads and former Directors who are still stewards. These are folks we trust to be able to handle an after-hours emergency. These individuals are identified in Neon by the "Super Steward" account type.<br />
<br />
* Super Stewards are added to the "Stewards" group on Discourse<br />
* Super Stewards have 24/7 access to all areas of the facility<br />
* Super Stewards don't immediately lose their facility access if a renewal payment fails.<br />
<br />
=== Leaders ===<br />
Leaders are designated Asmbly management. They usually have "Director" in their title, and they may be volunteer Subscribers or paid staff. Current leaders are listed on the [[Leadership]] page. These individuals are identified in Neon by the "Leader" account type.<br />
<br />
* Leaders are added to the "Leadership" group on Discourse.<br />
* Leaders have 24/7 access to all areas of the facility.<br />
* Leaders don't immediately lose their facility access if a renewal fails.<br />
<br />
''Note that board members are not granted any special Asmbly privileges unless they also hold an operational leadership position.''<br />
<br />
=== Staff ===<br />
Staff are individuals who are paid for their general work at Asmbly. They may have facility access equivalent to a Steward or Director depending on the role. They're identified in Neon by the account type "Staff". Staff are typically also Stewards or Leaders.</div>Jonhttps://wiki.asmbly.org/index.php?title=Offsite_Services&diff=3222Offsite Services2025-01-10T16:52:39Z<p>Jon: /* Current Systems */</p>
<hr />
<div>This page is a summary of all the off-site/third-party/cloud services utilized by Asmbly and how we use them.<br />
<br />
= Current Systems = <br />
== Neon == <br />
Neon is our member management system. We intend for it to be the sole interface for administrative tasks and the source of truth for member authentication and authorization. We've been pretty successful at the latter, less so with the former -- staff and volunteer leads still juggle multiple dashboards to some extent.<br />
<br />
Neon account creation starts with the [https://asmbly.org/join/ Join Form] on the website.<br />
Existing users may log into Neon at https://asmbly.z2systems.com/login.jsp<br />
<br />
Neon is a cloud service and has an [https://developer.neoncrm.com/api-v2/ API]<br />
<br />
== Alta Open (formerly Openpath) ==<br />
Alta Open is our access control system. It has its own user database, but that database is automatically synced with Neon account information. Some leaders have permission to access the Alta Open dashboard to modify user permissions, view access logs, and suchlike.<br />
<br />
Alta Open is a cloud service and has an [https://openpath.readme.io/reference API]<br />
<br />
== Skedda ==<br />
Skedda is the group calendaring tool we're using to schedule access to the space.<br />
<br />
Skedda has its own credential database that requires manual management of user permissions. It also unfortunately lacks any kind of published API. We have a medium-term goal of implementing some mechanism to update Skedda automatically based on member status changes in Neon, but no work is being done on that project at this time.<br />
<br />
For permission to book Asmbly spaces on Skedda, you must first sign up using the private invitation link you can find in your subscription acknowledgement email or the members-only message area of Discourse. https://yo.asmbly.org/t/skedda-invite-link/203. You might be signed into Discourse and you must be a member of the "makers" (paying members) group to view the link.<br />
<br />
Once you have created your Skedda account, you can log into Skedda directly at https://asmbly.skedda.com.<br />
<br />
== Discourse ==<br />
Discourse is the software that powers the Asmbly discussion site https://yo.asmbly.org/<br />
<br />
Discourse maintains its own credential database that requires manual management of user permissions. We have some periodic maintenance scripts that update Discourse users automatically in response to member status changes. As of now we don't plan to change Discourse to authenticate directly against Neon, because we can have Discourse users who are not and have never been Asmbly members and we don't want to put a bunch of non-members in Neon.<br />
<br />
Asmbly's Discourse instance is managed by [https://www.communiteq.com Communiteq] and has an [https://docs.discourse.org API]<br />
<br />
== Mediawiki ==<br />
This Asmbly wiki runs on Mediawiki. The ATXHS wiki did as well, but it became a maintenance sink so we're no longer keeping that online. <br />
<br />
This wiki authenticates users via Discourse -- if you have an Asmbly Discourse account, you also have a wiki account. Current and former members have edit permission.<br />
<br />
This wiki is self-hosted off site on AWS.<br />
<br />
== SignNow ==<br />
Some time back we switched all our e-sign forms from Smartwaiver to SignNow. New-and-improved features include emailing signers copies of their documents and automatically uploading them to Asmbly's files in GDrive. SignNow *kind of* has an API -- it can trigger [https://zapier.com/apps/signnow/integrations Zapier], which is good enough for us.<br />
<br />
== Wordpress ==<br />
The [http://www.asmbly.org public-facing website] runs on Wordpress. <br />
<br />
Wordpress is hosted off site and has an [https://developer.wordpress.org/rest-api/ API]<br />
<br />
== Zapier ==<br />
Zapier is a sorta no-code cloud workflow automation service. It supports limited webhook-style automations, but fortunately one of the actions is "execute arbitrary Python code" so we can do whatever we want in response to a SignNow document or Google Forms submission.<br />
<br />
== PayPal ==<br />
We use PayPal for generating miscellaneous invoices, including Co-Working and storage rentals. This is mainly a workaround for the fact that Neon doesn't support multiple concurrent subscriptions for a user (ie a member can't have both a membership subscription and a storage rental subscription that both automatically renew month-to-month).<br />
<br />
== Square ==<br />
We use Square for easier donations and purchase of supplies onsite at Asmbly.<br />
<br />
== Google Workspace ==<br />
Space leadership uses Google Workspace for mail, document sharing, the usual office stuff. As a non-profit organization we can use it free of charge. Many volunteers also use Asmbly's Google Workspace and we have a Shared Drive that is open for all in the Asmbly domain.<br />
<br />
== QuickBooks ==<br />
We use QuickBooks for our banking and accounts payable. Instructors are paid via QuickBooks, and QuickBooks Workforce is used for managing employee hours/pay/benefits.<br />
<br />
== Slack ==<br />
Space leadership, staff, and core volunteers use Slack for day-to-day operational communications.<br />
<br />
== Basecamp == <br />
Basecamp is a simple, web-based project management platform. We use it for coordinating and planning tasks for special events and general top-down project task tracking.<br />
<br />
== 1Password == <br />
1Password is a password manager which Asmbly uses to store all passwords for Asmbly accounts and securely share them with relevant parties. Asmbly has a Teams account with a limited number of seats.<br />
<br />
== TechSoup == <br />
TechSoup is a nonprofit organization that provides other nonprofits with access to software and technology at discounted prices. We use this resource for discounts on AWS and other subscription services we use. Each time we consider adding new services, we check TechSoup to ensure we're getting the best option for the best price.<br />
== Canva == <br />
Canva is a web-based content creation app that allows for creating a wide range of types of content and directly ordering prints. We use Canva for branded content creation including flyers, social media posts, animations, slide decks, signage, and more. As a non-profit organization we have a Pro account free of charge. Our Canva is loaded with all of our branded content including brand colors, fonts, logo variations, photos, graphic elements, templates, and more. Canva also has a large library of content that can be used in creations.<br />
<br />
== SignUpGenius == <br />
SignUpGenius is used for organizing volunteers for special events. It allows us to create a page for the volunteer event and list options for tasks volunteers can easily sign up for without having to create an account.<br />
== Mailjet ==<br />
Mailjet is used for our email announcements and monthly(ish) update / newsletter mailings. We are also transitioning class registrations to this system. <br />
<br />
Users may unsubscribe from the list using personalized links in the footer of each Mailjet email.<br />
<br />
All Neon accounts are automatically added to this email list at the time of account creation. <br />
<br />
Mailjet is a cloud service and has an [https://dev.mailjet.com/email/reference/overview/ API]<br />
=Deprecated Services=<br />
These are services we used to use, but don’t anymore for various reasons. <br />
<br />
== Hootsuite == <br />
Hootsuite is a social media management platform that we used to schedule posts across multiple social media platforms.<br />
<br />
== Mailchimp ==<br />
Mailchimp was used for our email announcements and monthly(ish) update / newsletter mailings. It was replaced with Flodesk. <br />
<br />
Users may sign up for the list here<br />
Users may unsubscribe from the list using personalized links in the footer of each Mailchimp email.<br />
<br />
( Administrative question: Are users automatically added to the mail chimp list at some point in the signup process? Answer: No, not currently. We periodically export all Neon users as CSV to update our mailing list.) <br />
<br />
Mailchimp is a cloud service and has an [https://mailchimp.com/developer/ API]<br />
<br />
== Flodesk ==<br />
Flodesk was used for our email announcements and monthly(ish) update / newsletter mailings. It was replaced with Mailjet. <br />
<br />
Users may sign up for the list here<br />
Users may unsubscribe from the list using personalized links in the footer of each Flodesk email. <br />
<br />
Flodesk is a cloud service and has an [https://developers.flodesk.com/ API]<br />
== Smartwaiver ==<br />
We used to use Smartwaiver for tracking liability waivers from members and visitors. All active e-sign documents have been moved to SignNow, but we maintain our SmartWaiver account so we can access the document archive.<br />
<br />
== Clockify == <br />
Clockify is a free time tracking software. We used it for our hourly staff to track time for wages. It’s been replaced with Quickbooks’ integrated solution (Quickbooks Workforce).<br />
<br />
== Freshbooks ==<br />
ATXHS used to use Freshbooks for member invoicing before they switched to Neon. For a while we had some old-school members who never bothered to make Neon accounts, so we kept Freshbooks around as long as they keep renewing their memberships.<br />
<br />
Since a Neon account was required for facility access via OpenPath, the last remaining Freshbooks members were basically inactive supporters. We appreciated them!<br />
<br />
[[Category:Operations]]</div>Jonhttps://wiki.asmbly.org/index.php?title=Offsite_Services&diff=3221Offsite Services2025-01-10T16:51:30Z<p>Jon: /* Deprecated Services */</p>
<hr />
<div>This page is a summary of all the off-site/third-party/cloud services utilized by Asmbly and how we use them.<br />
<br />
= Current Systems = <br />
== Neon == <br />
Neon is our member management system. We intend for it to be the sole interface for administrative tasks and the source of truth for member authentication and authorization. We've been pretty successful at the latter, less so with the former -- board members and some volunteer leads still juggle multiple dashboards to some extent.<br />
<br />
Neon account creation starts with the [https://asmbly.org/join/ Join Form] on the website.<br />
Existing users may log into Neon at https://asmbly.z2systems.com/login.jsp<br />
<br />
Neon is a cloud service and has an [https://developer.neoncrm.com/api-v2/ API]<br />
<br />
== Alta Open (formerly Openpath) ==<br />
Alta Open is our access control system. It has its own user database, but that database is automatically synced with Neon account information. Directors and some leaders have permission to access the Alta Open dashboard to modify user permissions, view access logs, and suchlike.<br />
<br />
Alta Open is a cloud service and has an [https://openpath.readme.io/reference API]<br />
<br />
== Skedda ==<br />
Skedda is the group calendaring tool we're using to schedule access to the space.<br />
<br />
Skedda has its own credential database that requires manual management of user permissions. It also unfortunately lacks any kind of published API. We have a medium-term goal of implementing some mechanism to update Skedda automatically based on member status changes in Neon, but no work is being done on that project at this time.<br />
<br />
For permission to book Asmbly spaces on Skedda, you must first sign up using the private invitation link you can find in your subscription acknowledgement email or the members-only message area of Discourse. https://yo.asmbly.org/t/skedda-invite-link/203. You might be signed into Discourse and you must be a member of the "makers" (paying members) group to view the link.<br />
<br />
Once you have created your Skedda account, you can log into Skedda directly at https://asmbly.skedda.com.<br />
<br />
== Discourse ==<br />
Discourse is the software that powers the Asmbly discussion site https://yo.asmbly.org/<br />
<br />
Discourse maintains its own credential database that requires manual management of user permissions. We have some periodic maintenance scripts that update Discourse users automatically in response to member status changes. As of now we don't plan to change Discourse to authenticate directly against Neon, because we can have Discourse users who are not and have never been Asmbly members and we don't want to put a bunch of non-members in Neon.<br />
<br />
Asmbly's Discourse instance is managed by [https://www.communiteq.com Communiteq] and has an [https://docs.discourse.org API]<br />
<br />
== Mediawiki ==<br />
This Asmbly wiki runs on Mediawiki. The ATXHS wiki did as well, but it became a maintenance sink so we're no longer keeping that online. <br />
<br />
This wiki authenticates users via Discourse -- if you have an Asmbly Discourse account, you also have a wiki account. Current and former members have edit permission.<br />
<br />
This wiki is self-hosted off site on AWS.<br />
<br />
== SignNow ==<br />
Some time back we switched all our e-sign forms from Smartwaiver to SignNow. New-and-improved features include emailing signers copies of their documents and automatically uploading them to Asmbly's files in GDrive. SignNow *kind of* has an API -- it can trigger [https://zapier.com/apps/signnow/integrations Zapier], which is good enough for us.<br />
<br />
== Wordpress ==<br />
The [http://www.asmbly.org public-facing website] runs on Wordpress. <br />
<br />
Wordpress is hosted off site and has an [https://developer.wordpress.org/rest-api/ API]<br />
<br />
== Zapier ==<br />
Zapier is a sorta no-code cloud workflow automation service. It supports limited webhook-style automations, but fortunately one of the actions is "execute arbitrary Python code" so we can do whatever we want in response to a SignNow document or Google Forms submission.<br />
<br />
== PayPal ==<br />
We use PayPal for generating miscellaneous invoices, including Co-Working and storage rentals. This is mainly a workaround for the fact that Neon doesn't support multiple concurrent subscriptions for a user (ie a member can't have both a membership subscription and a storage rental subscription that both automatically renew month-to-month).<br />
<br />
== Square ==<br />
We use Square for easier donations and purchase of supplies onsite at Asmbly.<br />
<br />
== Google Workspace ==<br />
Space leadership uses Google Workspace for mail, document sharing, the usual office stuff. As a non-profit organization we can use it free of charge. Many volunteers also use Asmbly's Google Workspace and we have a Shared Drive that is open for all in the Asmbly domain.<br />
<br />
== QuickBooks ==<br />
We use QuickBooks for our banking and accounts payable. Instructors are paid via QuickBooks, and QuickBooks Workforce is used for managing employee hours/pay/benefits.<br />
<br />
== Slack ==<br />
Space leadership, staff, and core volunteers use Slack for day-to-day operational communications.<br />
<br />
== Basecamp == <br />
Basecamp is a simple, web-based project management platform. We use it for coordinating and planning tasks for special events and general top-down project task tracking.<br />
<br />
== 1Password == <br />
1Password is a password manager which Asmbly uses to store all passwords for Asmbly accounts and securely share them with relevant parties. Asmbly has a Teams account with a limited number of seats.<br />
<br />
== TechSoup == <br />
TechSoup is a nonprofit organization that provides other nonprofits with access to software and technology at discounted prices. We use this resource for discounts on AWS and other subscription services we use. Each time we consider adding new services, we check TechSoup to ensure we're getting the best option for the best price.<br />
== Canva == <br />
Canva is a web-based content creation app that allows for creating a wide range of types of content and directly ordering prints. We use Canva for branded content creation including flyers, social media posts, animations, slide decks, signage, and more. As a non-profit organization we have a Pro account free of charge. Our Canva is loaded with all of our branded content including brand colors, fonts, logo variations, photos, graphic elements, templates, and more. Canva also has a large library of content that can be used in creations.<br />
<br />
== SignUpGenius == <br />
SignUpGenius is used for organizing volunteers for special events. It allows us to create a page for the volunteer event and list options for tasks volunteers can easily sign up for without having to create an account.<br />
== Mailjet ==<br />
Mailjet is used for our email announcements and monthly(ish) update / newsletter mailings. We are also transitioning class registrations to this system. <br />
<br />
Users may unsubscribe from the list using personalized links in the footer of each Mailjet email.<br />
<br />
All Neon accounts are automatically added to this email list at the time of account creation. <br />
<br />
Mailjet is a cloud service and has an [https://dev.mailjet.com/email/reference/overview/ API]<br />
=Deprecated Services=<br />
These are services we used to use, but don’t anymore for various reasons. <br />
<br />
== Hootsuite == <br />
Hootsuite is a social media management platform that we used to schedule posts across multiple social media platforms.<br />
<br />
== Mailchimp ==<br />
Mailchimp was used for our email announcements and monthly(ish) update / newsletter mailings. It was replaced with Flodesk. <br />
<br />
Users may sign up for the list here<br />
Users may unsubscribe from the list using personalized links in the footer of each Mailchimp email.<br />
<br />
( Administrative question: Are users automatically added to the mail chimp list at some point in the signup process? Answer: No, not currently. We periodically export all Neon users as CSV to update our mailing list.) <br />
<br />
Mailchimp is a cloud service and has an [https://mailchimp.com/developer/ API]<br />
<br />
== Flodesk ==<br />
Flodesk was used for our email announcements and monthly(ish) update / newsletter mailings. It was replaced with Mailjet. <br />
<br />
Users may sign up for the list here<br />
Users may unsubscribe from the list using personalized links in the footer of each Flodesk email. <br />
<br />
Flodesk is a cloud service and has an [https://developers.flodesk.com/ API]<br />
== Smartwaiver ==<br />
We used to use Smartwaiver for tracking liability waivers from members and visitors. All active e-sign documents have been moved to SignNow, but we maintain our SmartWaiver account so we can access the document archive.<br />
<br />
== Clockify == <br />
Clockify is a free time tracking software. We used it for our hourly staff to track time for wages. It’s been replaced with Quickbooks’ integrated solution (Quickbooks Workforce).<br />
<br />
== Freshbooks ==<br />
ATXHS used to use Freshbooks for member invoicing before they switched to Neon. For a while we had some old-school members who never bothered to make Neon accounts, so we kept Freshbooks around as long as they keep renewing their memberships.<br />
<br />
Since a Neon account was required for facility access via OpenPath, the last remaining Freshbooks members were basically inactive supporters. We appreciated them!<br />
<br />
[[Category:Operations]]</div>Jonhttps://wiki.asmbly.org/index.php?title=Offsite_Services&diff=3220Offsite Services2025-01-10T16:13:58Z<p>Jon: /* Clockify */</p>
<hr />
<div>This page is a summary of all the off-site/third-party/cloud services utilized by Asmbly and how we use them.<br />
<br />
= Current Systems = <br />
== Neon == <br />
Neon is our member management system. We intend for it to be the sole interface for administrative tasks and the source of truth for member authentication and authorization. We've been pretty successful at the latter, less so with the former -- board members and some volunteer leads still juggle multiple dashboards to some extent.<br />
<br />
Neon account creation starts with the [https://asmbly.org/join/ Join Form] on the website.<br />
Existing users may log into Neon at https://asmbly.z2systems.com/login.jsp<br />
<br />
Neon is a cloud service and has an [https://developer.neoncrm.com/api-v2/ API]<br />
<br />
== Alta Open (formerly Openpath) ==<br />
Alta Open is our access control system. It has its own user database, but that database is automatically synced with Neon account information. Directors and some leaders have permission to access the Alta Open dashboard to modify user permissions, view access logs, and suchlike.<br />
<br />
Alta Open is a cloud service and has an [https://openpath.readme.io/reference API]<br />
<br />
== Skedda ==<br />
Skedda is the group calendaring tool we're using to schedule access to the space.<br />
<br />
Skedda has its own credential database that requires manual management of user permissions. It also unfortunately lacks any kind of published API. We have a medium-term goal of implementing some mechanism to update Skedda automatically based on member status changes in Neon, but no work is being done on that project at this time.<br />
<br />
For permission to book Asmbly spaces on Skedda, you must first sign up using the private invitation link you can find in your subscription acknowledgement email or the members-only message area of Discourse. https://yo.asmbly.org/t/skedda-invite-link/203. You might be signed into Discourse and you must be a member of the "makers" (paying members) group to view the link.<br />
<br />
Once you have created your Skedda account, you can log into Skedda directly at https://asmbly.skedda.com.<br />
<br />
== Discourse ==<br />
Discourse is the software that powers the Asmbly discussion site https://yo.asmbly.org/<br />
<br />
Discourse maintains its own credential database that requires manual management of user permissions. We have some periodic maintenance scripts that update Discourse users automatically in response to member status changes. As of now we don't plan to change Discourse to authenticate directly against Neon, because we can have Discourse users who are not and have never been Asmbly members and we don't want to put a bunch of non-members in Neon.<br />
<br />
Asmbly's Discourse instance is managed by [https://www.communiteq.com Communiteq] and has an [https://docs.discourse.org API]<br />
<br />
== Mediawiki ==<br />
This Asmbly wiki runs on Mediawiki. The ATXHS wiki did as well, but it became a maintenance sink so we're no longer keeping that online. <br />
<br />
This wiki authenticates users via Discourse -- if you have an Asmbly Discourse account, you also have a wiki account. Current and former members have edit permission.<br />
<br />
This wiki is self-hosted off site on AWS.<br />
<br />
== SignNow ==<br />
Some time back we switched all our e-sign forms from Smartwaiver to SignNow. New-and-improved features include emailing signers copies of their documents and automatically uploading them to Asmbly's files in GDrive. SignNow *kind of* has an API -- it can trigger [https://zapier.com/apps/signnow/integrations Zapier], which is good enough for us.<br />
<br />
== Wordpress ==<br />
The [http://www.asmbly.org public-facing website] runs on Wordpress. <br />
<br />
Wordpress is hosted off site and has an [https://developer.wordpress.org/rest-api/ API]<br />
<br />
== Zapier ==<br />
Zapier is a sorta no-code cloud workflow automation service. It supports limited webhook-style automations, but fortunately one of the actions is "execute arbitrary Python code" so we can do whatever we want in response to a SignNow document or Google Forms submission.<br />
<br />
== PayPal ==<br />
We use PayPal for generating miscellaneous invoices, including Co-Working and storage rentals. This is mainly a workaround for the fact that Neon doesn't support multiple concurrent subscriptions for a user (ie a member can't have both a membership subscription and a storage rental subscription that both automatically renew month-to-month).<br />
<br />
== Square ==<br />
We use Square for easier donations and purchase of supplies onsite at Asmbly.<br />
<br />
== Google Workspace ==<br />
Space leadership uses Google Workspace for mail, document sharing, the usual office stuff. As a non-profit organization we can use it free of charge. Many volunteers also use Asmbly's Google Workspace and we have a Shared Drive that is open for all in the Asmbly domain.<br />
<br />
== QuickBooks ==<br />
We use QuickBooks for our banking and accounts payable. Instructors are paid via QuickBooks, and QuickBooks Workforce is used for managing employee hours/pay/benefits.<br />
<br />
== Slack ==<br />
Space leadership, staff, and core volunteers use Slack for day-to-day operational communications.<br />
<br />
== Basecamp == <br />
Basecamp is a simple, web-based project management platform. We use it for coordinating and planning tasks for special events and general top-down project task tracking.<br />
<br />
== 1Password == <br />
1Password is a password manager which Asmbly uses to store all passwords for Asmbly accounts and securely share them with relevant parties. Asmbly has a Teams account with a limited number of seats.<br />
<br />
== TechSoup == <br />
TechSoup is a nonprofit organization that provides other nonprofits with access to software and technology at discounted prices. We use this resource for discounts on AWS and other subscription services we use. Each time we consider adding new services, we check TechSoup to ensure we're getting the best option for the best price.<br />
== Canva == <br />
Canva is a web-based content creation app that allows for creating a wide range of types of content and directly ordering prints. We use Canva for branded content creation including flyers, social media posts, animations, slide decks, signage, and more. As a non-profit organization we have a Pro account free of charge. Our Canva is loaded with all of our branded content including brand colors, fonts, logo variations, photos, graphic elements, templates, and more. Canva also has a large library of content that can be used in creations.<br />
<br />
== SignUpGenius == <br />
SignUpGenius is used for organizing volunteers for special events. It allows us to create a page for the volunteer event and list options for tasks volunteers can easily sign up for without having to create an account.<br />
== Mailjet ==<br />
Mailjet is used for our email announcements and monthly(ish) update / newsletter mailings. We are also transitioning class registrations to this system. <br />
<br />
Users may unsubscribe from the list using personalized links in the footer of each Mailjet email.<br />
<br />
All Neon accounts are automatically added to this email list at the time of account creation. <br />
<br />
Mailjet is a cloud service and has an [https://dev.mailjet.com/email/reference/overview/ API]<br />
=Deprecated Services=<br />
== Hootsuite == <br />
Hootsuite is a social media management platform that we used to schedule posts across multiple social media platforms.<br />
<br />
== Mailchimp ==<br />
Mailchimp was used for our email announcements and monthly(ish) update / newsletter mailings. It was replaced with Flodesk. <br />
<br />
Users may sign up for the list here<br />
Users may unsubscribe from the list using personalized links in the footer of each Mailchimp email.<br />
<br />
( Administrative question: Are users automatically added to the mail chimp list at some point in the signup process? Answer: No, not currently. We periodically export all Neon users as CSV to update our mailing list.) <br />
<br />
Mailchimp is a cloud service and has an [https://mailchimp.com/developer/ API]<br />
<br />
== Flodesk ==<br />
Flodesk was used for our email announcements and monthly(ish) update / newsletter mailings. It was replaced with Mailjet. <br />
<br />
Users may sign up for the list here<br />
Users may unsubscribe from the list using personalized links in the footer of each Flodesk email. <br />
<br />
Flodesk is a cloud service and has an [https://developers.flodesk.com/ API]<br />
== Smartwaiver ==<br />
We used to use Smartwaiver for tracking liability waivers from members and visitors. All active e-sign documents have been moved to SignNow, but we maintain our SmartWaiver account so we can access the document archive.<br />
<br />
== Clockify == <br />
Clockify is a free time tracking software. We used it for our hourly staff to track time for wages. It’s been replaced with Quickbooks’ integrated solution (Quickbooks Workforce).<br />
<br />
== Freshbooks ==<br />
ATXHS used to use Freshbooks for member invoicing before they switched to Neon. For a while we had some old-school members who never bothered to make Neon accounts, so we kept Freshbooks around as long as they keep renewing their memberships.<br />
<br />
Since a Neon account was required for facility access via OpenPath, the last remaining Freshbooks members were basically inactive supporters. We appreciated them!<br />
<br />
[[Category:Operations]]</div>Jonhttps://wiki.asmbly.org/index.php?title=Offsite_Services&diff=3219Offsite Services2025-01-10T16:13:28Z<p>Jon: </p>
<hr />
<div>This page is a summary of all the off-site/third-party/cloud services utilized by Asmbly and how we use them.<br />
<br />
= Current Systems = <br />
== Neon == <br />
Neon is our member management system. We intend for it to be the sole interface for administrative tasks and the source of truth for member authentication and authorization. We've been pretty successful at the latter, less so with the former -- board members and some volunteer leads still juggle multiple dashboards to some extent.<br />
<br />
Neon account creation starts with the [https://asmbly.org/join/ Join Form] on the website.<br />
Existing users may log into Neon at https://asmbly.z2systems.com/login.jsp<br />
<br />
Neon is a cloud service and has an [https://developer.neoncrm.com/api-v2/ API]<br />
<br />
== Alta Open (formerly Openpath) ==<br />
Alta Open is our access control system. It has its own user database, but that database is automatically synced with Neon account information. Directors and some leaders have permission to access the Alta Open dashboard to modify user permissions, view access logs, and suchlike.<br />
<br />
Alta Open is a cloud service and has an [https://openpath.readme.io/reference API]<br />
<br />
== Skedda ==<br />
Skedda is the group calendaring tool we're using to schedule access to the space.<br />
<br />
Skedda has its own credential database that requires manual management of user permissions. It also unfortunately lacks any kind of published API. We have a medium-term goal of implementing some mechanism to update Skedda automatically based on member status changes in Neon, but no work is being done on that project at this time.<br />
<br />
For permission to book Asmbly spaces on Skedda, you must first sign up using the private invitation link you can find in your subscription acknowledgement email or the members-only message area of Discourse. https://yo.asmbly.org/t/skedda-invite-link/203. You might be signed into Discourse and you must be a member of the "makers" (paying members) group to view the link.<br />
<br />
Once you have created your Skedda account, you can log into Skedda directly at https://asmbly.skedda.com.<br />
<br />
== Discourse ==<br />
Discourse is the software that powers the Asmbly discussion site https://yo.asmbly.org/<br />
<br />
Discourse maintains its own credential database that requires manual management of user permissions. We have some periodic maintenance scripts that update Discourse users automatically in response to member status changes. As of now we don't plan to change Discourse to authenticate directly against Neon, because we can have Discourse users who are not and have never been Asmbly members and we don't want to put a bunch of non-members in Neon.<br />
<br />
Asmbly's Discourse instance is managed by [https://www.communiteq.com Communiteq] and has an [https://docs.discourse.org API]<br />
<br />
== Mediawiki ==<br />
This Asmbly wiki runs on Mediawiki. The ATXHS wiki did as well, but it became a maintenance sink so we're no longer keeping that online. <br />
<br />
This wiki authenticates users via Discourse -- if you have an Asmbly Discourse account, you also have a wiki account. Current and former members have edit permission.<br />
<br />
This wiki is self-hosted off site on AWS.<br />
<br />
== SignNow ==<br />
Some time back we switched all our e-sign forms from Smartwaiver to SignNow. New-and-improved features include emailing signers copies of their documents and automatically uploading them to Asmbly's files in GDrive. SignNow *kind of* has an API -- it can trigger [https://zapier.com/apps/signnow/integrations Zapier], which is good enough for us.<br />
<br />
== Wordpress ==<br />
The [http://www.asmbly.org public-facing website] runs on Wordpress. <br />
<br />
Wordpress is hosted off site and has an [https://developer.wordpress.org/rest-api/ API]<br />
<br />
== Zapier ==<br />
Zapier is a sorta no-code cloud workflow automation service. It supports limited webhook-style automations, but fortunately one of the actions is "execute arbitrary Python code" so we can do whatever we want in response to a SignNow document or Google Forms submission.<br />
<br />
== PayPal ==<br />
We use PayPal for generating miscellaneous invoices, including Co-Working and storage rentals. This is mainly a workaround for the fact that Neon doesn't support multiple concurrent subscriptions for a user (ie a member can't have both a membership subscription and a storage rental subscription that both automatically renew month-to-month).<br />
<br />
== Square ==<br />
We use Square for easier donations and purchase of supplies onsite at Asmbly.<br />
<br />
== Google Workspace ==<br />
Space leadership uses Google Workspace for mail, document sharing, the usual office stuff. As a non-profit organization we can use it free of charge. Many volunteers also use Asmbly's Google Workspace and we have a Shared Drive that is open for all in the Asmbly domain.<br />
<br />
== QuickBooks ==<br />
We use QuickBooks for our banking and accounts payable. Instructors are paid via QuickBooks, and QuickBooks Workforce is used for managing employee hours/pay/benefits.<br />
<br />
== Slack ==<br />
Space leadership, staff, and core volunteers use Slack for day-to-day operational communications.<br />
<br />
== Basecamp == <br />
Basecamp is a simple, web-based project management platform. We use it for coordinating and planning tasks for special events and general top-down project task tracking.<br />
<br />
== 1Password == <br />
1Password is a password manager which Asmbly uses to store all passwords for Asmbly accounts and securely share them with relevant parties. Asmbly has a Teams account with a limited number of seats.<br />
<br />
== TechSoup == <br />
TechSoup is a nonprofit organization that provides other nonprofits with access to software and technology at discounted prices. We use this resource for discounts on AWS and other subscription services we use. Each time we consider adding new services, we check TechSoup to ensure we're getting the best option for the best price.<br />
== Canva == <br />
Canva is a web-based content creation app that allows for creating a wide range of types of content and directly ordering prints. We use Canva for branded content creation including flyers, social media posts, animations, slide decks, signage, and more. As a non-profit organization we have a Pro account free of charge. Our Canva is loaded with all of our branded content including brand colors, fonts, logo variations, photos, graphic elements, templates, and more. Canva also has a large library of content that can be used in creations.<br />
<br />
== SignUpGenius == <br />
SignUpGenius is used for organizing volunteers for special events. It allows us to create a page for the volunteer event and list options for tasks volunteers can easily sign up for without having to create an account.<br />
== Mailjet ==<br />
Mailjet is used for our email announcements and monthly(ish) update / newsletter mailings. We are also transitioning class registrations to this system. <br />
<br />
Users may unsubscribe from the list using personalized links in the footer of each Mailjet email.<br />
<br />
All Neon accounts are automatically added to this email list at the time of account creation. <br />
<br />
Mailjet is a cloud service and has an [https://dev.mailjet.com/email/reference/overview/ API]<br />
=Deprecated Services=<br />
== Hootsuite == <br />
Hootsuite is a social media management platform that we used to schedule posts across multiple social media platforms.<br />
<br />
== Mailchimp ==<br />
Mailchimp was used for our email announcements and monthly(ish) update / newsletter mailings. It was replaced with Flodesk. <br />
<br />
Users may sign up for the list here<br />
Users may unsubscribe from the list using personalized links in the footer of each Mailchimp email.<br />
<br />
( Administrative question: Are users automatically added to the mail chimp list at some point in the signup process? Answer: No, not currently. We periodically export all Neon users as CSV to update our mailing list.) <br />
<br />
Mailchimp is a cloud service and has an [https://mailchimp.com/developer/ API]<br />
<br />
== Flodesk ==<br />
Flodesk was used for our email announcements and monthly(ish) update / newsletter mailings. It was replaced with Mailjet. <br />
<br />
Users may sign up for the list here<br />
Users may unsubscribe from the list using personalized links in the footer of each Flodesk email. <br />
<br />
Flodesk is a cloud service and has an [https://developers.flodesk.com/ API]<br />
== Smartwaiver ==<br />
We used to use Smartwaiver for tracking liability waivers from members and visitors. All active e-sign documents have been moved to SignNow, but we maintain our SmartWaiver account so we can access the document archive.<br />
<br />
== Clockify == <br />
Clockify is a free time tracking software. We used it for our hourly staff to track time for wages. It’s been replaced with Quickbook’s integrated solution (Quickbooks Workforce).<br />
<br />
== Freshbooks ==<br />
ATXHS used to use Freshbooks for member invoicing before they switched to Neon. For a while we had some old-school members who never bothered to make Neon accounts, so we kept Freshbooks around as long as they keep renewing their memberships.<br />
<br />
Since a Neon account was required for facility access via OpenPath, the last remaining Freshbooks members were basically inactive supporters. We appreciated them!<br />
<br />
[[Category:Operations]]</div>Jonhttps://wiki.asmbly.org/index.php?title=Offsite_Services&diff=3218Offsite Services2025-01-10T16:08:38Z<p>Jon: </p>
<hr />
<div>This page is a summary of all the off-site/third-party/cloud services utilized by Asmbly and how we use them.<br />
<br />
= Current Systems = <br />
== Neon == <br />
Neon is our member management system. We intend for it to be the sole interface for administrative tasks and the source of truth for member authentication and authorization. We've been pretty successful at the latter, less so with the former -- board members and some volunteer leads still juggle multiple dashboards to some extent.<br />
<br />
Neon account creation starts with the [https://asmbly.org/join/ Join Form] on the website.<br />
Existing users may log into Neon at https://asmbly.z2systems.com/login.jsp<br />
<br />
Neon is a cloud service and has an [https://developer.neoncrm.com/api-v2/ API]<br />
<br />
== Alta Open (formerly Openpath) ==<br />
Alta Open is our access control system. It has its own user database, but that database is automatically synced with Neon account information. Directors and some leaders have permission to access the Alta Open dashboard to modify user permissions, view access logs, and suchlike.<br />
<br />
Alta Open is a cloud service and has an [https://openpath.readme.io/reference API]<br />
<br />
== Skedda ==<br />
Skedda is the group calendaring tool we're using to schedule access to the space.<br />
<br />
Skedda has its own credential database that requires manual management of user permissions. It also unfortunately lacks any kind of published API. We have a medium-term goal of implementing some mechanism to update Skedda automatically based on member status changes in Neon, but no work is being done on that project at this time.<br />
<br />
For permission to book Asmbly spaces on Skedda, you must first sign up using the private invitation link you can find in your subscription acknowledgement email or the members-only message area of Discourse. https://yo.asmbly.org/t/skedda-invite-link/203. You might be signed into Discourse and you must be a member of the "makers" (paying members) group to view the link.<br />
<br />
Once you have created your Skedda account, you can log into Skedda directly at https://asmbly.skedda.com.<br />
<br />
== Discourse ==<br />
Discourse is the software that powers the Asmbly discussion site https://yo.asmbly.org/<br />
<br />
Discourse maintains its own credential database that requires manual management of user permissions. We have some periodic maintenance scripts that update Discourse users automatically in response to member status changes. As of now we don't plan to change Discourse to authenticate directly against Neon, because we can have Discourse users who are not and have never been Asmbly members and we don't want to put a bunch of non-members in Neon.<br />
<br />
Asmbly's Discourse instance is managed by [https://www.communiteq.com Communiteq] and has an [https://docs.discourse.org API]<br />
<br />
== SignNow ==<br />
Some time back we switched our e-sign stuff from Smartwaiver to SignNow. New-and-improve features include emailing signers copies of their documents, and uploading them to Asmbly's Gdrive. SignNow *kind of* has an API -- it can trigger [https://zapier.com/apps/signnow/integrations Zapier], which is good enough for us.<br />
<br />
== Zapier ==<br />
Zapier is a sorta no-code cloud workflow automation service. It supports limited webhook-style automations, but fortunately one of the actions is "execute arbitrary Python code" so we can do whatever we want in response to a SignNow document or Google Forms submission.<br />
<br />
== Mediawiki ==<br />
The Asmbly wiki runs on Mediawiki. The ATXHS wiki did as well, but it became a maintenance sink so we're no longer keeping that online. <br />
<br />
The Asmbly wiki authenticates users via Discourse -- if you have an Asmbly Discourse account, you also have a wiki account. Members and former members have edit permission.<br />
<br />
The wiki is self-hosted off site on AWS.<br />
<br />
== Wordpress ==<br />
The [http://www.asmbly.org public-facing website] runs on Wordpress. <br />
<br />
Wordpress is hosted off site and has an [https://developer.wordpress.org/rest-api/ API]<br />
<br />
== QuickBooks ==<br />
We use QuickBooks for our banking and accounts payable. Instructors are paid via QuickBooks, and QuickBooks Workforce is used for managing employee hours/pay/benefits.<br />
<br />
== PayPal ==<br />
We use PayPal for generating miscellaneous invoices, including Co-Working and storage rentals. This is mainly a workaround for the fact that Neon doesn't support multiple concurrent subscriptions for a user (ie a member can't have both a membership subscription and a storage rental subscription that both automatically renew month-to-month).<br />
<br />
== Square ==<br />
We use Square for easier donations and purchase of supplies onsite at Asmbly.<br />
<br />
== Google Workspace ==<br />
Space leadership uses Google Workspace for mail, document sharing, the usual office stuff. As a non-profit organization we can use it free of charge. Many volunteers also use Asmbly's Google Workspace and we have a Shared Drive that is open for all in the Asmbly domain.<br />
<br />
== Slack == <br />
Space leadership, staff, and core volunteers use Slack for day-to-day operational communications.<br />
<br />
== 1Password == <br />
1Password is a password manager which Asmbly uses to store all passwords for Asmbly accounts and securely share them with relevant parties. Asmbly has a Teams account with a limited number of seats.<br />
<br />
== TechSoup == <br />
TechSoup is a nonprofit organization that provides other nonprofits with access to software and technology at discounted prices. We use this resource for discounts on AWS and other subscription services we use. Each time we consider adding new services, we check TechSoup to ensure we're getting the best option for the best price.<br />
== Canva == <br />
Canva is a web-based content creation app that allows for creating a wide range of types of content and directly ordering prints. We use Canva for branded content creation including flyers, social media posts, animations, slide decks, signage, and more. As a non-profit organization we have a Pro account free of charge. Our Canva is loaded with all of our branded content including brand colors, fonts, logo variations, photos, graphic elements, templates, and more. Canva also has a large library of content that can be used in creations.<br />
<br />
== Basecamp == <br />
Basecamp is a simple, web-based project management platform. We use it for coordinating and planning tasks for special events and general top-down project task tracking.<br />
<br />
== SignUpGenius == <br />
SignUpGenius is used for organizing volunteers for special events. It allows us to create a page for the volunteer event and list options for tasks volunteers can easily sign up for without having to create an account.<br />
== Mailjet ==<br />
Mailjet is used for our email announcements and monthly(ish) update / newsletter mailings. We are also transitioning class registrations to this system. <br />
<br />
Users may unsubscribe from the list using personalized links in the footer of each Mailjet email.<br />
<br />
All Neon accounts are automatically added to this email list at the time of account creation. <br />
<br />
Mailjet is a cloud service and has an [https://dev.mailjet.com/email/reference/overview/ API]<br />
<br />
<br />
=Deprecated Services=<br />
== Hootsuite == <br />
Hootsuite is a social media management platform that we used to schedule posts across multiple social media platforms.<br />
<br />
== Mailchimp ==<br />
Mailchimp was used for our email announcements and monthly(ish) update / newsletter mailings. It was replaced with Flodesk. <br />
<br />
Users may sign up for the list here<br />
Users may unsubscribe from the list using personalized links in the footer of each Mailchimp email.<br />
<br />
( Administrative question: Are users automatically added to the mail chimp list at some point in the signup process? Answer: No, not currently. We periodically export all Neon users as CSV to update our mailing list.) <br />
<br />
Mailchimp is a cloud service and has an [https://mailchimp.com/developer/ API]<br />
<br />
== Flodesk ==<br />
Flodesk was used for our email announcements and monthly(ish) update / newsletter mailings. It was replaced with Mailjet. <br />
<br />
Users may sign up for the list here<br />
Users may unsubscribe from the list using personalized links in the footer of each Flodesk email. <br />
<br />
Flodesk is a cloud service and has an [https://developers.flodesk.com/ API]<br />
== Smartwaiver ==<br />
We used to use Smartwaiver for tracking liability waivers from members and visitors. All active e-sign documents have been moved to SignNow, but we maintain our SmartWaiver account so we can access the document archive.<br />
<br />
== Clockify == <br />
Clockify is a free time tracking software. We used it for our hourly staff to track time for wages. It’s been replaced with Quickbook’s integrated solution (Quickbooks Workforce).<br />
<br />
== Freshbooks ==<br />
ATXHS used to use Freshbooks for member invoicing before they switched to Neon. For a while we had some old-school members who never bothered to make Neon accounts, so we kept Freshbooks around as long as they keep renewing their memberships.<br />
<br />
Since a Neon account was required for facility access via OpenPath, the last remaining Freshbooks members were basically inactive supporters. We appreciated them!<br />
<br />
[[Category:Operations]]</div>Jonhttps://wiki.asmbly.org/index.php?title=Offsite_Services&diff=3217Offsite Services2025-01-10T15:17:12Z<p>Jon: </p>
<hr />
<div>This page is a summary of all the off-site/third-party/cloud services utilized by Asmbly and how we use them.<br />
<br />
= Current Systems = <br />
== Neon == <br />
Neon is our member management system. We intend for it to be the sole interface for administrative tasks and the source of truth for member authentication and authorization. We've been pretty successful at the latter, less so with the former -- board members and some volunteer leads still juggle multiple dashboards to some extent.<br />
<br />
Neon account creation starts with the [https://asmbly.org/join/ Join Form] on the website.<br />
Existing users may log into Neon at https://asmbly.z2systems.com/login.jsp<br />
<br />
Neon is a cloud service and has an [https://developer.neoncrm.com/api-v2/ API]<br />
<br />
== Alta Open (formerly Openpath) ==<br />
Alta Open is our access control system. It has its own user database, but that database is automatically synced with Neon account information. Directors and some leaders have permission to access the Alta Open dashboard to modify user permissions, view access logs, and suchlike.<br />
<br />
Alta Open is a cloud service and has an [https://openpath.readme.io/reference API]<br />
<br />
== Skedda ==<br />
Skedda is the group calendaring tool we're using to schedule access to the space.<br />
<br />
Skedda has its own credential database that requires manual management of user permissions. It also unfortunately lacks any kind of published API. We have a medium-term goal of implementing some mechanism to update Skedda automatically based on member status changes in Neon, but no work is being done on that project at this time.<br />
<br />
For permission to book Asmbly spaces on Skedda, you must first sign up using the private invitation link you can find in your subscription acknowledgement email or the members-only message area of Discourse. https://yo.asmbly.org/t/skedda-invite-link/203. You might be signed into Discourse and you must be a member of the "makers" (paying members) group to view the link.<br />
<br />
Once you have created your Skedda account, you can log into Skedda directly at https://asmbly.skedda.com.<br />
<br />
== Discourse ==<br />
Discourse is the software that powers the Asmbly discussion site https://yo.asmbly.org/<br />
<br />
Discourse maintains its own credential database that requires manual management of user permissions. We have some periodic maintenance scripts that update Discourse users automatically in response to member status changes. As of now we don't plan to change Discourse to authenticate directly against Neon, because we can have Discourse users who are not and have never been Asmbly members and we don't want to put a bunch of non-members in Neon.<br />
<br />
Asmbly's Discourse instance is managed by [https://www.communiteq.com Communiteq] and has an [https://docs.discourse.org API]<br />
<br />
== SignNow ==<br />
Some time back we switched our e-sign stuff from Smartwaiver to SignNow. New-and-improve features include emailing signers copies of their documents, and uploading them to Asmbly's Gdrive. SignNow *kind of* has an API -- it can trigger [https://zapier.com/apps/signnow/integrations Zapier], which is good enough for us.<br />
<br />
== Zapier ==<br />
Zapier is a sorta no-code cloud workflow automation service. It supports limited webhook-style automations, but fortunately one of the actions is "execute arbitrary Python code" so we can do whatever we want in response to a SignNow document or Google Forms submission.<br />
<br />
== Mediawiki ==<br />
The Asmbly wiki runs on Mediawiki. The ATXHS wiki did as well, but it became a maintenance sink so we're no longer keeping that online. <br />
<br />
The Asmbly wiki authenticates users via Discourse -- if you have an Asmbly Discourse account, you also have a wiki account. Members and former members have edit permission.<br />
<br />
The wiki is self-hosted off site on AWS.<br />
<br />
== Wordpress ==<br />
The [http://www.asmbly.org public-facing website] runs on Wordpress. <br />
<br />
Wordpress is hosted off site and has an [https://developer.wordpress.org/rest-api/ API]<br />
<br />
== QuickBooks ==<br />
We use QuickBooks for our banking and accounts payable. Instructors are paid via QuickBooks.<br />
<br />
== PayPal ==<br />
We use PayPal for generating miscellaneous invoices, including Co-Working and storage rentals. This is mainly a workaround for the fact that Neon doesn't support multiple concurrent subscriptions for a user (ie a member can't have both a membership subscription and a storage rental subscription that both automatically renew month-to-month).<br />
<br />
== Square ==<br />
We use Square for easier donations and purchase of supplies onsite at Asmbly.<br />
<br />
== Google Workspace ==<br />
Space leadership uses Google Workspace for mail, document sharing, the usual office stuff. As a non-profit organization we can use it free of charge. Many volunteers also use Asmbly's Google Workspace and we have a Shared Drive that is open for all in the Asmbly domain.<br />
<br />
== Slack == <br />
Space leadership, staff, and core volunteers use Slack for day-to-day operational communications.<br />
<br />
== 1Password == <br />
1Password is a password manager which Asmbly uses to store all passwords for Asmbly accounts and securely share them with relevant parties. Asmbly has a Teams account with a limited number of seats.<br />
<br />
== Clockify == <br />
Clockify is a free time tracking software. We use it for our hourly staff to track time for wages.<br />
<br />
== TechSoup == <br />
TechSoup is a nonprofit organization that provides other nonprofits with access to software and technology at discounted prices. We use this resource for discounts on AWS and other subscription services we use. Each time we consider adding new services, we check TechSoup to ensure we're getting the best option for the best price.<br />
== Canva == <br />
Canva is a web-based content creation app that allows for creating a wide range of types of content and directly ordering prints. We use Canva for branded content creation including flyers, social media posts, animations, slide decks, signage, and more. As a non-profit organization we have a Pro account free of charge. Our Canva is loaded with all of our branded content including brand colors, fonts, logo variations, photos, graphic elements, templates, and more. Canva also has a large library of content that can be used in creations.<br />
<br />
== Basecamp == <br />
Basecamp is a simple, web-based project management platform. We use it for coordinating and planning tasks for special events and general top-down project task tracking.<br />
<br />
== SignUpGenius == <br />
SignUpGenius is used for organizing volunteers for special events. It allows us to create a page for the volunteer event and list options for tasks volunteers can easily sign up for without having to create an account.<br />
== Mailjet ==<br />
Mailjet is used for our email announcements and monthly(ish) update / newsletter mailings. We are also transitioning class registrations to this system. <br />
<br />
Users may unsubscribe from the list using personalized links in the footer of each Mailjet email.<br />
<br />
All Neon accounts are automatically added to this email list at the time of account creation. <br />
<br />
Mailjet is a cloud service and has an [https://dev.mailjet.com/email/reference/overview/ API]<br />
<br />
<br />
=Deprecated Services=<br />
== Hootsuite == <br />
Hootsuite is a social media management platform that we used to schedule posts across multiple social media platforms.<br />
<br />
== Mailchimp ==<br />
Mailchimp was used for our email announcements and monthly(ish) update / newsletter mailings. It was replaced with Flodesk. <br />
<br />
Users may sign up for the list here<br />
Users may unsubscribe from the list using personalized links in the footer of each Mailchimp email.<br />
<br />
( Administrative question: Are users automatically added to the mail chimp list at some point in the signup process? Answer: No, not currently. We periodically export all Neon users as CSV to update our mailing list.) <br />
<br />
Mailchimp is a cloud service and has an [https://mailchimp.com/developer/ API]<br />
<br />
== Flodesk ==<br />
Flodesk was used for our email announcements and monthly(ish) update / newsletter mailings. It was replaced with Mailjet. <br />
<br />
Users may sign up for the list here<br />
Users may unsubscribe from the list using personalized links in the footer of each Flodesk email. <br />
<br />
Flodesk is a cloud service and has an [https://developers.flodesk.com/ API]<br />
== Smartwaiver ==<br />
We used to use Smartwaiver for tracking liability waivers from members and visitors. All active e-sign documents have been moved to SignNow, but we maintain our SmartWaiver account so we can access the document archive.<br />
<br />
== Freshbooks ==<br />
ATXHS used to use Freshbooks for member invoicing before they switched to Neon. For a while we had some old-school members who never bothered to make Neon accounts, so we kept Freshbooks around as long as they keep renewing their memberships.<br />
<br />
Since a Neon account was required for facility access via OpenPath, the last remaining Freshbooks members were basically inactive supporters. We appreciated them!<br />
<br />
[[Category:Operations]]</div>Jonhttps://wiki.asmbly.org/index.php?title=Openpath&diff=3213Openpath2025-01-07T02:38:05Z<p>Jon: /* About the Hardware */</p>
<hr />
<div>Asmbly uses [https://www.openpath.com Openpath] smart readers for building access control (door locks). This system uses a smartphone app as a primary authentication mechanism, so you don't need to use a key fob or badge anymore.<br />
<br />
To set up an Openpath credential on your smartphone, click on the link in the Openpath invitation email. If you haven't received an invitation, you can install the app but can't set up access to Asmbly.<br />
<br />
== For Users ==<br />
Access to the facility is granted on successful completion of all pre-requisites for membership:<br />
<br />
* Purchased a subscription in Neon<br />
* Signed the [https://asmbly.org/waiver subscription agreement and liability waiver]<br />
* Completed [https://asmbly.org/classes/?category=Orientation in-person orientation] if joined later than July 1 2021 or membership has lapsed for more than 12 months<br />
<br />
The Openpath invitation email is sent by setup@openpath.com and has the subject line "Time to set up Openpath for Asmbly Makerspace!". If you expected an invitation and did not receive one, check your spam folder.<br />
<br />
As of now (Dec 2022) Openpath invites are sent periodically throughout the day. If you've completed all your pre-requisites and need urgent activation, email [mailto:membership@asmbly.org membership@asmbly.org] for assistance.<br />
<br />
<!---<br />
If your subscription lapses in Neon, your Openpath access will be suspended. It will be re-enabled when you renew. Email notifications for access suspension and resumption are sent by notification@asmbly.org with subject lines "Your Asmbly Facility Access is Disabled" and "Your Asmbly Facility Access is Enabled", respectively.<br />
---><br />
<br />
== For Administrators ==<br />
Board members and some stewards have access to Asmbly's management interface at https://control.openpath.com. <br />
<br />
=== Keyfobs ===<br />
Keyfob orders are fulfilled from the scanned keyfobs assigned to the Openpath user "Unregistered Keyfob". Find the Weigand credential that matches the fob you're sending. Copy the card number to clipboard/notepad and delete the UK's corresponding credential. Find the purchaser in Openpath and create a new Weigand credential for that user. Paste the card number into the new credential. Confirm the parsed "Card ID" matches the label on the keyfob. Save the credential.<br />
<br />
When you mail or hand-off the keyfob to the purchaser, mark the Neon order fulfilled.<br />
<br />
If "Unregistered Keyfob" is all out of credentials, grab another handful from stock and scan them in turn at any OP reader. You can find the card numbers in the access log.<br />
<br />
== About the Hardware ==<br />
Our panel has a dual-voltage accessory power supply, which takes up a fair amount of space and we don't actually need since all our lock hardware is 24V. We could fit bigger backup batteries if we removed the 12V supply parts. On the other hand, the dual-voltage power supply includes individual fuses for each door lock, which may be prudent to retain.<br />
<br />
Smart readers are connected to the panel via shielded CAT6. The install manual didn't specify a color code, so here's what we used:<br />
{| class="wikitable" style="text-align: center;<br />
|+<br />
!Color<br />
!Signal (old)<br />
!Signal (new)<br />
|-<br />
|Brown / Brown-White<br />
| colspan="2" |Ground<br />
|-<br />
|Orange / Orange-white<br />
| colspan="2" | +V<br />
|-<br />
|Blue<br />
| colspan="2" |Data+<br />
|-<br />
|Blue-white<br />
| colspan="2" |Data-<br />
|-<br />
|Green<br />
| rowspan="2" |Door position contact (NC)<br />
|Rex (NO to Ground)<br />
|-<br />
|Green-White<br />
|Contact (NC to Ground)<br />
|}<br />
Two conductors are used for power and ground to reduce voltage drop. Our runs may be short enough that this isn't strictly necessary, but I have not confirmed. The door lock hardware itself is actuated by a separate single-pair security cable.<br />
<br />
We have not yet set up end-of-line supervision for door contacts for open/short detection. It would perhaps be prudent to do so.<br />
<br />
All the hardware manuals have been scanned and saved in Google Drive.<br />
<br />
[[Category:operations]]</div>Jonhttps://wiki.asmbly.org/index.php?title=Openpath&diff=3212Openpath2025-01-07T02:37:47Z<p>Jon: Added new door pinout with Rex</p>
<hr />
<div>Asmbly uses [https://www.openpath.com Openpath] smart readers for building access control (door locks). This system uses a smartphone app as a primary authentication mechanism, so you don't need to use a key fob or badge anymore.<br />
<br />
To set up an Openpath credential on your smartphone, click on the link in the Openpath invitation email. If you haven't received an invitation, you can install the app but can't set up access to Asmbly.<br />
<br />
== For Users ==<br />
Access to the facility is granted on successful completion of all pre-requisites for membership:<br />
<br />
* Purchased a subscription in Neon<br />
* Signed the [https://asmbly.org/waiver subscription agreement and liability waiver]<br />
* Completed [https://asmbly.org/classes/?category=Orientation in-person orientation] if joined later than July 1 2021 or membership has lapsed for more than 12 months<br />
<br />
The Openpath invitation email is sent by setup@openpath.com and has the subject line "Time to set up Openpath for Asmbly Makerspace!". If you expected an invitation and did not receive one, check your spam folder.<br />
<br />
As of now (Dec 2022) Openpath invites are sent periodically throughout the day. If you've completed all your pre-requisites and need urgent activation, email [mailto:membership@asmbly.org membership@asmbly.org] for assistance.<br />
<br />
<!---<br />
If your subscription lapses in Neon, your Openpath access will be suspended. It will be re-enabled when you renew. Email notifications for access suspension and resumption are sent by notification@asmbly.org with subject lines "Your Asmbly Facility Access is Disabled" and "Your Asmbly Facility Access is Enabled", respectively.<br />
---><br />
<br />
== For Administrators ==<br />
Board members and some stewards have access to Asmbly's management interface at https://control.openpath.com. <br />
<br />
=== Keyfobs ===<br />
Keyfob orders are fulfilled from the scanned keyfobs assigned to the Openpath user "Unregistered Keyfob". Find the Weigand credential that matches the fob you're sending. Copy the card number to clipboard/notepad and delete the UK's corresponding credential. Find the purchaser in Openpath and create a new Weigand credential for that user. Paste the card number into the new credential. Confirm the parsed "Card ID" matches the label on the keyfob. Save the credential.<br />
<br />
When you mail or hand-off the keyfob to the purchaser, mark the Neon order fulfilled.<br />
<br />
If "Unregistered Keyfob" is all out of credentials, grab another handful from stock and scan them in turn at any OP reader. You can find the card numbers in the access log.<br />
<br />
== About the Hardware ==<br />
Our panel has a dual-voltage accessory power supply, which takes up a fair amount of space and we don't actually need since all our lock hardware is 24V. We could fit bigger backup batteries if we removed the 12V supply parts. On the other hand, the dual-voltage power supply includes individual fuses for each door lock, which may be prudent to retain.<br />
<br />
Smart readers are connected to the panel via shielded CAT6. The install manual didn't specify a color code, so here's what we used:<br />
{| class="wikitable"<br />
|+<br />
!Color<br />
!Signal (old)<br />
!Signal (new)<br />
|-<br />
|Brown / Brown-White<br />
| colspan="2" |Ground<br />
|-<br />
|Orange / Orange-white<br />
| colspan="2" | +V<br />
|-<br />
|Blue<br />
| colspan="2" |Data+<br />
|-<br />
|Blue-white<br />
| colspan="2" |Data-<br />
|-<br />
|Green<br />
| rowspan="2" |Door position contact (NC)<br />
|Rex (NO to Ground)<br />
|-<br />
|Green-White<br />
|Contact (NC to Ground)<br />
|}<br />
Two conductors are used for power and ground to reduce voltage drop. Our runs may be short enough that this isn't strictly necessary, but I have not confirmed. The door lock hardware itself is actuated by a separate single-pair security cable.<br />
<br />
We have not yet set up end-of-line supervision for door contacts for open/short detection. It would perhaps be prudent to do so.<br />
<br />
All the hardware manuals have been scanned and saved in Google Drive.<br />
<br />
[[Category:operations]]</div>Jonhttps://wiki.asmbly.org/index.php?title=Wen_6502T_Combination_Sander&diff=3211Wen 6502T Combination Sander2025-01-07T01:26:11Z<p>Jon: </p>
<hr />
<div>{{Boneyard}}<br />
<br />
The Wen 6502T combination sander features a 4x36" belt and 6" disk with tilting table.<br />
<br />
{{ToolPhoto|Wen6502T.jpg}}<br />
<br />
== Resources ==<br />
* [[Media:Wen 6520 Manual.pdf|Instruction Manual]]</div>Jonhttps://wiki.asmbly.org/index.php?title=Template:Hosted&diff=3210Template:Hosted2025-01-06T16:53:21Z<p>Jon: </p>
<hr />
<div><includeonly><br />
==Maintenance==<br />
This tool is owned by {{{1}}} and hosted at Asmbly for members to use. Please [https://asmbly.org/problem submit a problem report] if maintenance is required.<br />
[[category:Hosted]]<br />
[[category:{{{1}}} Owned]]<br />
</includeonly><br />
<noinclude><br />
This template displays a banner about hosted tool ownership and applies the owner's category to the including page.<br />
<br />
<nowiki><br />
{{Hosted|Demo Owner}}<br />
</nowiki><br />
==Maintenance==<br />
This tool is owned by Demo Owner and hosted at Asmbly for members to use. Please [https://asmbly.org/problem submit a problem report] if maintenance is required.<br />
</noinclude></div>Jonhttps://wiki.asmbly.org/index.php?title=Template:Owned&diff=3209Template:Owned2025-01-06T16:52:44Z<p>Jon: </p>
<hr />
<div><includeonly><br />
==Maintenance==<br />
This tool is owned by Asmbly Makerspace for the use of its members. Please [https://asmbly.org/problem submit a problem report] if maintenance is required.<br />
[[Category:Owned]]<br />
</includeonly><br />
<noinclude><br />
This template displays a banner about maintenance for tools owned by Asmbly<br />
<br />
<nowiki><br />
{{Owned}}<br />
</nowiki><br />
==Maintenance==<br />
This tool is owned by Asmbly Makerspace for the use of its members. Please [https://asmbly.org/problem submit a problem report] if maintenance is required.<br />
</noinclude></div>Jonhttps://wiki.asmbly.org/index.php?title=Form_2&diff=3201Form 22025-01-02T05:15:19Z<p>Jon: </p>
<hr />
<div>{{boneyard}}<br />
<br />
Asmbly has two Formlabs Form 2 desktop SLA printers: one hosted, and one owned by Asmbly. We also have Form Wash and Form Cure post-processing equipment. Only resin purchased from Asmbly may be used in these printers.<br />
<br />
{{ToolPhoto|Form2.jpg}}<br />
{{ToolPhoto|FormPost.jpg}}<br />
<br />
== Maintenance ==<br />
After a failed print, it may be helpful to print a few layers of this "cleaning mesh", then remove it, to pull off residue from the previous job. Formlabs has a [https://support.formlabs.com/s/article/Cleaning-a-failed-print-with-the-cleaning-mesh?language=en_US help page] for this for the Form3 printer, but the official mesh doesn't seem to be available.<br />
<br />
[[File:Form2-cleaning-mesh-hex.stl]]<br />
<br />
== Resources ==<br />
* [[Media:Form2_User_Manual.pdf|Form2 User Manual]]<br />
* [[Media:Form_Wash_User_Manual.pdf|Form Wash User Manual]]<br />
* [[Media:Form_Cure_User_Manual.pdf|Form Cure User Manual]]</div>Jonhttps://wiki.asmbly.org/index.php?title=Wood_River_Mortiser&diff=3199Wood River Mortiser2024-12-27T17:03:25Z<p>Jon: </p>
<hr />
<div>{{boneyard}}<br />
Asmbly owns a Wood River 151223 Benchtop Mortiser<br />
<br />
{{ToolPhoto|Mortiser.jpg}}<br />
<br />
=== Specifications ===<br />
* Motor: ½ HP, 115V, 60 Hz, TEFC<br />
* Spindle Speed: 1,725 RPM<br />
* Chuck Capacity: 3/8"<br />
* Chisels: 1/4", 5/16", 3/8", and 1/2<br />
* 5" stroke<br />
* Min. under hold down: 1"<br />
* Max. under hold down: 4-1/4"<br />
* Fence size: 3" Height x 14-1/2" Long<br />
* Base Size: 17" Deep x 35” Long with extensions<br />
<br />
== Resources ==<br />
* [[Media:Steel_City_25200_Manual.pdf|User Manual]] (Steel City Tool Works variant)<br />
* [https://www.woodcraft.com/products/woodriver-benchtop-mortiser-with-chisels-bits Woodcraft]</div>Jonhttps://wiki.asmbly.org/index.php?title=Organization&diff=3195Organization2024-12-10T03:48:06Z<p>Jon: Add links to public documents and board meeting minutes</p>
<hr />
<div>Asmbly's organization structure consists of two main groups: the board, who are in charge of strategy and governance, and volunteer leaders and paid staff, who are in charge of getting stuff done. Sometimes an individual volunteer serves in multiple roles, but this isn't always the case. See [[Leadership]] for info on current and past appointments.<br />
<br />
While the organization chart below reflects reporting structure within Asmbly, we as an organization value collaboration and see all positions as having direct relationships with one another so that we may effectively reach our shared goals.<br />
<br />
[[File:Asmbly Org Chart.png|frameless|800x800px]]<br />
<br />
== The Board ==<br />
Asmbly's board consists of a President, a Secretary, a Treasurer, and (as of 2021) two "at large" board members with no specific duties. Board terms are staggered so not everybody's up for replacement in the same year.<br />
<br />
Officially board terms are two years, but people can be replaced mid-term by either resignation or ejection.<br />
<br />
At this time, new board members are elected by majority of the current board.<br />
<br />
The Board operates according to Asmbly's bylaws, as amended from time to time. These (and other Asmbly public documents) may be found [https://drive.google.com/drive/folders/1d6pFaw7LAfkfgCCxQQfldOosOEJSG0v9 here]. Minutes of board meetings may be found [https://drive.google.com/drive/folders/1izGozNaR1nJrbMZfT-XMzEZSffJKgcq5 here] once they've been reviewed and accepted by the board.<br />
<br />
;President<br />
: The board president owns the agenda and generally runs board meetings. Asmbly's president is a voting member of the board.<br />
;Secretary<br />
: The board secretary is responsible for meeting minutes, governing documents, and official policies of Asmbly.<br />
;Treasurer<br />
: The board treasurer is responsible for Asmbly's overall budget. As of now the treasurer is also responsible for day-to-day accounts receivable and payable, but could be a staff or assistant volunteer responsibility in the future.<br />
;At-Large Board Members<br />
: An At-Large board member doesn't have any specific responsibilities beyond participating in board work and voting on motions before the board.<br />
<br />
== Volunteer/Paid Leaders ==<br />
The day-to-day operation of Asmbly is largely driven by volunteer leaders, although we aim to someday transition all of these to paid positions. Some of these roles are filled by board members but none of them need be. Each volunteer/paid leader is essentially the top of an ad-hoc pyramid; they may manage their teams and delegate as they see fit, but are ultimately responsible that stuff gets done.<br />
<br />
;Executive Director<br />
: The Executive Director has overall authority over all staff and volunteers at Asmbly, answering only to the board.<br />
;Director of Outreach<br />
: The Director of Outreach has authority over Asmbly's outreach efforts, including partnerships and sponsorships, outreach programs and events.<br />
'''Program Manager'''<br />
: The Program Manger is a paid leadership position at Asmbly that oversees our three core pillars: education, membership, and outreach. This person manages Education and Membership teams to ensure programs run smoothly and works closely with the Director of Outreach on expanding Asmbly's reach.<br />
;Shop Area Leads<br />
:Each major shop area may have designated shop area leads. These individuals take on a leadership role within their designated areas to ensure that equipment is well maintained, in good working order, and meets the needs of membership. They work closely with other leaders, staff, and stewards in their designated areas.<br />
:More details about this program can be found [https://wiki.asmbly.org/index.php/Shop_Area_Leads_Program here].<br />
<br />
==Unfilled Leadership Roles==<br />
Asmbly is interested in filling additional leadership roles if/when we can find the right volunteers<br />
<br />
;Director of Education<br />
:The Director of Education has authority over everything related to classes and training, including instructors, curricula and scheduling.<br />
;Director of Development<br />
:The Director of Development has authority over Asmbly's public interactions, including marketing, advertising, and fundraising.<br />
<br />
==Staff==<br />
Asmbly has a limited number of paid staff who are responsible for ensuring some of the basic critical operations of the organization are maintained. Below are roles that currently exist.<br />
<br />
;Membership & Volunteer Coordinator<br />
:The Membership Coordinator is responsible for responding to emails sent to [mailto:membership@asmbly.org membership@asmbly.org] and leading weekly orientation sessions. They help members with any onboarding or system issues they experience. They collaborate with all other departments in the organization to ensure the needs of the membership are met. They actively engage members in the community to help members feel connected and supported. They organize volunteer committees to help Asmbly's operations and goals.<br />
;Education Coordinator<br />
:The Education Coordinator is responsible for ensuring classes are on the schedule, ideally at least 45 days in advance. They onboard new instructors, respond to class requests, determine appropriate cadence for classes, and other administrative tasks related to education. They work closely with other members of the Education Team to ensure education offerings at Asmbly are high quality and readily available.<br />
;Facilities Coordinator<br />
:The Facilities Coordinator is responsible for the physical space and its infrastructure, including space planning, networks, utilities, HVAC, and access controls. Volunteer stewards work closely with the Facilities Coordinator to ensure tool maintenance and repair is taken care of. The Facilities Coordinator helps develop and enforce operational policies and procedures within shops in collaboration with Shop Area Leads. They are also responsible for completing purchase orders and overseeing tool acquisitions.<br />
<br />
==Past Roles==<br />
These are roles that have existed at some point in Asmbly's history that are not currently filled.<br />
<br />
;Lead Instructor<br />
:The Lead Instructor is responsible for vetting instructors and evaluating new classes. They assist instructors in developing teaching skills as well as class curriculum. They work closely with other members of the Education Team to provide input on class cadence, size, and complexity level.<br />
<br />
;General Manager<br />
:The General Manager has authority over all goings-on in the space, including tool acquisition/disposition, project planning and execution, member onboarding and discipline, operational policies and procedures. The General Manager also has authority over the space and its infrastructure, including space planning, networks, utilities, HVAC, and access controls. Volunteer stewards report to the General Manager and work with them to ensure tool maintenance and repair is taken care of.<br />
<br />
[[Category:Operations]]</div>Jonhttps://wiki.asmbly.org/index.php?title=Organization&diff=3194Organization2024-12-10T02:45:57Z<p>Jon: </p>
<hr />
<div>Asmbly's organization structure consists of two main groups: the board, who are in charge of strategy and governance, and volunteer leaders and paid staff, who are in charge of getting stuff done. Sometimes an individual volunteer serves in multiple roles, but this isn't always the case. See [[Leadership]] for info on current and past appointments.<br />
<br />
While the organization chart below reflects reporting structure within Asmbly, we as an organization value collaboration and see all positions as having direct relationships with one another so that we may effectively reach our shared goals.<br />
<br />
[[File:Asmbly Org Chart.png|frameless|800x800px]]<br />
<br />
== The Board ==<br />
Asmbly's board consists of a President, a Secretary, a Treasurer, and (as of 2021) two "at large" board members with no specific duties. Board terms are staggered so not everybody's up for replacement in the same year.<br />
<br />
Officially board terms are two years, but people can be replaced mid-term by either resignation or ejection.<br />
<br />
At this time, new board members are elected by majority of the current board.<br />
<br />
The Board operates according to Asmbly's bylaws, as amended from time to time. These (and other Asmbly public documents) may be found [https://drive.google.com/drive/folders/1d6pFaw7LAfkfgCCxQQfldOosOEJSG0v9?usp=sharing here]. Minutes of board meetings may be found [https://drive.google.com/drive/folders/1izGozNaR1nJrbMZfT-XMzEZSffJKgcq5?usp=sharing here] once they've been reviewed and accepted by the board.<br />
<br />
;President<br />
: The board president owns the agenda and generally runs board meetings. Asmbly's president is a voting member of the board.<br />
;Secretary<br />
: The board secretary is responsible for meeting minutes, governing documents, and official policies of Asmbly.<br />
;Treasurer<br />
: The board treasurer is responsible for Asmbly's overall budget. As of now the treasurer is also responsible for day-to-day accounts receivable and payable, but could be a staff or assistant volunteer responsibility in the future.<br />
;At-Large Board Members<br />
: An At-Large board member doesn't have any specific responsibilities beyond participating in board work and voting on motions before the board.<br />
<br />
== Volunteer/Paid Leaders ==<br />
The day-to-day operation of Asmbly is largely driven by volunteer leaders, although we aim to someday transition all of these to paid positions. Some of these roles are filled by board members but none of them need be. Each volunteer/paid leader is essentially the top of an ad-hoc pyramid; they may manage their teams and delegate as they see fit, but are ultimately responsible that stuff gets done.<br />
<br />
;Executive Director<br />
: The Executive Director has overall authority over all staff and volunteers at Asmbly, answering only to the board.<br />
;Director of Outreach<br />
: The Director of Outreach has authority over Asmbly's outreach efforts, including partnerships and sponsorships, outreach programs and events.<br />
'''Program Manager'''<br />
: The Program Manger is a paid leadership position at Asmbly that oversees our three core pillars: education, membership, and outreach. This person manages Education and Membership teams to ensure programs run smoothly and works closely with the Director of Outreach on expanding Asmbly's reach.<br />
;Shop Area Leads<br />
:Each major shop area may have designated shop area leads. These individuals take on a leadership role within their designated areas to ensure that equipment is well maintained, in good working order, and meets the needs of membership. They work closely with other leaders, staff, and stewards in their designated areas.<br />
:More details about this program can be found [https://wiki.asmbly.org/index.php/Shop_Area_Leads_Program here].<br />
<br />
==Unfilled Leadership Roles==<br />
Asmbly is interested in filling additional leadership roles if/when we can find the right volunteers<br />
<br />
;Director of Education<br />
:The Director of Education has authority over everything related to classes and training, including instructors, curricula and scheduling.<br />
;Director of Development<br />
:The Director of Development has authority over Asmbly's public interactions, including marketing, advertising, and fundraising.<br />
<br />
==Staff==<br />
Asmbly has a limited number of paid staff who are responsible for ensuring some of the basic critical operations of the organization are maintained. Below are roles that currently exist.<br />
<br />
;Membership & Volunteer Coordinator<br />
:The Membership Coordinator is responsible for responding to emails sent to [mailto:membership@asmbly.org membership@asmbly.org] and leading weekly orientation sessions. They help members with any onboarding or system issues they experience. They collaborate with all other departments in the organization to ensure the needs of the membership are met. They actively engage members in the community to help members feel connected and supported. They organize volunteer committees to help Asmbly's operations and goals.<br />
;Education Coordinator<br />
:The Education Coordinator is responsible for ensuring classes are on the schedule, ideally at least 45 days in advance. They onboard new instructors, respond to class requests, determine appropriate cadence for classes, and other administrative tasks related to education. They work closely with other members of the Education Team to ensure education offerings at Asmbly are high quality and readily available.<br />
;Facilities Coordinator<br />
:The Facilities Coordinator is responsible for the physical space and its infrastructure, including space planning, networks, utilities, HVAC, and access controls. Volunteer stewards work closely with the Facilities Coordinator to ensure tool maintenance and repair is taken care of. The Facilities Coordinator helps develop and enforce operational policies and procedures within shops in collaboration with Shop Area Leads. They are also responsible for completing purchase orders and overseeing tool acquisitions.<br />
<br />
==Past Roles==<br />
These are roles that have existed at some point in Asmbly's history that are not currently filled.<br />
<br />
;Lead Instructor<br />
:The Lead Instructor is responsible for vetting instructors and evaluating new classes. They assist instructors in developing teaching skills as well as class curriculum. They work closely with other members of the Education Team to provide input on class cadence, size, and complexity level.<br />
<br />
;General Manager<br />
:The General Manager has authority over all goings-on in the space, including tool acquisition/disposition, project planning and execution, member onboarding and discipline, operational policies and procedures. The General Manager also has authority over the space and its infrastructure, including space planning, networks, utilities, HVAC, and access controls. Volunteer stewards report to the General Manager and work with them to ensure tool maintenance and repair is taken care of.<br />
<br />
[[Category:Operations]]</div>Jonhttps://wiki.asmbly.org/index.php?title=Organization&diff=3193Organization2024-12-10T02:40:45Z<p>Jon: </p>
<hr />
<div>Asmbly's organization structure consists of two main groups: the board, who are in charge of strategy and governance, and volunteer leaders and paid staff, who are in charge of getting stuff done. Sometimes an individual volunteer serves in multiple roles, but this isn't always the case. See [[Leadership]] for info on current and past appointments.<br />
<br />
While the organization chart below reflects reporting structure within Asmbly, we as an organization value collaboration and see all positions as having direct relationships with one another so that we may effectively reach our shared goals.<br />
<br />
[[File:Asmbly Org Chart.png|frameless|800x800px]]<br />
<br />
== The Board ==<br />
Asmbly's board consists of a President, a Secretary, a Treasurer, and (as of 2021) two "at large" board members with no specific duties. Board terms are staggered so not everybody's up for replacement in the same year.<br />
<br />
Officially board terms are two years, but people can be replaced mid-term by either resignation or ejection.<br />
<br />
At this time, new board members are elected by majority of the current board.<br />
<br />
The Board operates according to Asmbly's bylaws, as amended from time to time. These (and other Asmbly public documents) may be found [https://drive.google.com/drive/folders/1d6pFaw7LAfkfgCCxQQfldOosOEJSG0v9?usp=sharing here].<br />
<br />
;President<br />
: The board president owns the agenda and generally runs board meetings. Asmbly's president is a voting member of the board.<br />
;Secretary<br />
: The board secretary is responsible for meeting minutes, governing documents, and official policies of Asmbly.<br />
;Treasurer<br />
: The board treasurer is responsible for Asmbly's overall budget. As of now the treasurer is also responsible for day-to-day accounts receivable and payable, but could be a staff or assistant volunteer responsibility in the future.<br />
;At-Large Board Members<br />
: An At-Large board member doesn't have any specific responsibilities beyond participating in board work and voting on motions before the board.<br />
<br />
== Volunteer/Paid Leaders ==<br />
The day-to-day operation of Asmbly is largely driven by volunteer leaders, although we aim to someday transition all of these to paid positions. Some of these roles are filled by board members but none of them need be. Each volunteer/paid leader is essentially the top of an ad-hoc pyramid; they may manage their teams and delegate as they see fit, but are ultimately responsible that stuff gets done.<br />
<br />
;Executive Director<br />
: The Executive Director has overall authority over all staff and volunteers at Asmbly, answering only to the board.<br />
;Director of Outreach<br />
: The Director of Outreach has authority over Asmbly's outreach efforts, including partnerships and sponsorships, outreach programs and events.<br />
'''Program Manager'''<br />
: The Program Manger is a paid leadership position at Asmbly that oversees our three core pillars: education, membership, and outreach. This person manages Education and Membership teams to ensure programs run smoothly and works closely with the Director of Outreach on expanding Asmbly's reach.<br />
;Shop Area Leads<br />
:Each major shop area may have designated shop area leads. These individuals take on a leadership role within their designated areas to ensure that equipment is well maintained, in good working order, and meets the needs of membership. They work closely with other leaders, staff, and stewards in their designated areas.<br />
:More details about this program can be found [https://wiki.asmbly.org/index.php/Shop_Area_Leads_Program here].<br />
<br />
==Unfilled Leadership Roles==<br />
Asmbly is interested in filling additional leadership roles if/when we can find the right volunteers<br />
<br />
;Director of Education<br />
:The Director of Education has authority over everything related to classes and training, including instructors, curricula and scheduling.<br />
;Director of Development<br />
:The Director of Development has authority over Asmbly's public interactions, including marketing, advertising, and fundraising.<br />
<br />
==Staff==<br />
Asmbly has a limited number of paid staff who are responsible for ensuring some of the basic critical operations of the organization are maintained. Below are roles that currently exist.<br />
<br />
;Membership & Volunteer Coordinator<br />
:The Membership Coordinator is responsible for responding to emails sent to [mailto:membership@asmbly.org membership@asmbly.org] and leading weekly orientation sessions. They help members with any onboarding or system issues they experience. They collaborate with all other departments in the organization to ensure the needs of the membership are met. They actively engage members in the community to help members feel connected and supported. They organize volunteer committees to help Asmbly's operations and goals.<br />
;Education Coordinator<br />
:The Education Coordinator is responsible for ensuring classes are on the schedule, ideally at least 45 days in advance. They onboard new instructors, respond to class requests, determine appropriate cadence for classes, and other administrative tasks related to education. They work closely with other members of the Education Team to ensure education offerings at Asmbly are high quality and readily available.<br />
;Facilities Coordinator<br />
:The Facilities Coordinator is responsible for the physical space and its infrastructure, including space planning, networks, utilities, HVAC, and access controls. Volunteer stewards work closely with the Facilities Coordinator to ensure tool maintenance and repair is taken care of. The Facilities Coordinator helps develop and enforce operational policies and procedures within shops in collaboration with Shop Area Leads. They are also responsible for completing purchase orders and overseeing tool acquisitions.<br />
<br />
==Past Roles==<br />
These are roles that have existed at some point in Asmbly's history that are not currently filled.<br />
<br />
;Lead Instructor<br />
:The Lead Instructor is responsible for vetting instructors and evaluating new classes. They assist instructors in developing teaching skills as well as class curriculum. They work closely with other members of the Education Team to provide input on class cadence, size, and complexity level.<br />
<br />
;General Manager<br />
:The General Manager has authority over all goings-on in the space, including tool acquisition/disposition, project planning and execution, member onboarding and discipline, operational policies and procedures. The General Manager also has authority over the space and its infrastructure, including space planning, networks, utilities, HVAC, and access controls. Volunteer stewards report to the General Manager and work with them to ensure tool maintenance and repair is taken care of.<br />
<br />
[[Category:Operations]]</div>Jonhttps://wiki.asmbly.org/index.php?title=Offsite_Services&diff=3135Offsite Services2024-10-17T01:41:40Z<p>Jon: </p>
<hr />
<div>This page is a summary of all the off-site/third-party/cloud services utilized by Asmbly and how we use them.<br />
<br />
= Current Systems = <br />
== Neon == <br />
Neon is our member management system. We intend for it to be the sole interface for administrative tasks and the source of truth for member authentication and authorization. We've been pretty successful at the latter, less so with the former -- board members and some volunteer leads still juggle multiple dashboards to some extent.<br />
<br />
Neon account creation starts with the [https://asmbly.org/join/ Join Form] on the website.<br />
Existing users may log into Neon at https://asmbly.z2systems.com/login.jsp<br />
<br />
Neon is a cloud service and has an [https://developer.neoncrm.com/api-v2/ API]<br />
<br />
== OpenPath ==<br />
OpenPath is our access control system. It has its own user database, but that database is automatically synced with Neon account information. Board members and some stewards have permission to access the OpenPath dashboard to modify user permissions, view access logs, and suchlike.<br />
<br />
OpenPath is a cloud service and has an [https://openpath.readme.io/reference API]<br />
<br />
== Skedda ==<br />
Skedda is the group calendaring tool we're using to schedule access to the space.<br />
<br />
Skedda has its own credential database that requires manual management of user permissions. It also unfortunately lacks any kind of published API. We have a medium-term goal of implementing some mechanism to update Skedda automatically based on member status changes in Neon, but no work is being done on that project at this time.<br />
<br />
For permission to book Asmbly spaces on Skedda, you must first sign up using the private invitation link you can find in your subscription acknowledgement email or the members-only message area of Discourse. https://yo.asmbly.org/t/skedda-invite-link/203. You might be signed into Discourse and you must be a member of the "makers" (paying members) group to view the link.<br />
<br />
Once you have created your Skedda account, you can log into Skedda directly at https://asmbly.skedda.com.<br />
<br />
== Discourse ==<br />
Discourse is the software that powers the Asmbly discussion site https://yo.asmbly.org/<br />
<br />
Discourse maintains its own credential database that requires manual management of user permissions. We have some periodic maintenance scripts that update Discourse users automatically in response to member status changes. As of now we don't plan to change Discourse to authenticate directly against Neon, because we can have Discourse users who are not and have never been Asmbly members and we don't want to put a bunch of non-members in Neon.<br />
<br />
Asmbly's Discourse instance is managed by [https://www.communiteq.com Communiteq] and has an [https://docs.discourse.org API]<br />
<br />
== SignNow ==<br />
Some time back we switched our e-sign stuff from Smartwaiver to SignNow. New-and-improve features include emailing signers copies of their documents, and uploading them to Asmbly's Gdrive. SignNow *kind of* has an API -- it can trigger [https://zapier.com/apps/signnow/integrations Zapier], which is good enough for us.<br />
<br />
== Zapier ==<br />
Zapier is a sorta no-code cloud workflow automation service. It supports limited webhook-style automations, but fortunately one of the actions is "execute arbitrary Python code" so we can do whatever we want in response to a SignNow document or Google Forms submission.<br />
<br />
== Mediawiki ==<br />
The Asmbly wiki runs on Mediawik. The ATXHS wiki did as well, but became a maintenance sink so we're no longer keeping that online. <br />
<br />
The Asmbly wiki authenticates users via Discourse -- if you have an Asmbly Discourse account, you also have a wiki account.<br />
<br />
Both wikis are self-hosted off site on AWS.<br />
<br />
== Wordpress ==<br />
The [http://www.asmbly.org public-facing website] runs on Wordpress. <br />
<br />
Wordpress is hosted off site and has an [https://developer.wordpress.org/rest-api/ API]<br />
<br />
== QuickBooks ==<br />
We use QuickBooks for our banking and accounts payable. Instructors are paid via QuickBooks.<br />
<br />
== PayPal ==<br />
We use PayPal for generating miscellaneous invoices, including Co-Working and storage rentals. This is partially a workaround for the fact that Neon doesn't support multiple concurrent subscriptions for a user (ie you couldn't have both a membership subscription and a storage rental subscription that both automatically renew month-to-month).<br />
<br />
== Square ==<br />
We use Square for easier checkout of supplies that can be purchased onsite at Asmbly.<br />
<br />
== Google Workspace ==<br />
Space leadership uses Google Workspace for mail, document sharing, the usual office stuff. As a non-profit organization we can use it free of charge. Many volunteers also use Asmbly's Google Workspace and we have a Shared Drive that is open for all in the Asmbly domain.<br />
<br />
== Slack == <br />
Space leadership uses Slack for day-to-day operational communications.<br />
<br />
== 1Password == <br />
1Password is a password manager which Asmbly uses to store all passwords for Asmbly accounts and securely share them with relevant parties. Asmbly has a Teams account with a limited number of seats.<br />
<br />
== Clockify == <br />
Clockify is a free time tracking software. We use it for our hourly staff to track time for wages.<br />
<br />
== TechSoup == <br />
TechSoup is a nonprofit organization that provides other nonprofits with access to software and technology at discounted prices. We use this resource for discounts on AWS and other subscription services we use. Each time we consider adding new services, we check TechSoup to ensure we're getting the best option for the best price.<br />
<br />
== Mailchimp ==<br />
Mailchimp is used for our email announcements and monthly(ish) update / newsletter mailings. We are currently evaluating Flodesk and may migrate away from Mailchimp. <br />
<br />
Users may sign up for the list [http://eepurl.com/gZuGvz here]<br />
Users may unsubscribe from the list using personalized links in the footer of each Mailchimp email.<br />
<br />
( Administrative question: Are users automatically added to the mail chimp list at some point in the signup process? Answer: No, not currently. We periodically export all Neon users as CSV to update our mailing list.) <br />
<br />
Mailchimp is a cloud service and has an [https://mailchimp.com/developer/ API]<br />
<br />
== Flodesk ==<br />
Flodesk is used for our email announcements and monthly(ish) update / newsletter mailings. <br />
<br />
Users may sign up for the list [https://asmbly.myflodesk.com/rgwdmleitd here]<br />
Users may unsubscribe from the list using personalized links in the footer of each Flodesk email. <br />
<br />
Flodesk is a cloud service and has an [https://developers.flodesk.com/ API] <br />
<br />
== Canva == <br />
Canva is a web-based content creation app that allows for creating a wide range of types of content and directly ordering prints. We use Canva for branded content creation including flyers, social media posts, animations, slide decks, signage, and more. As a non-profit organization we have a Pro account free of charge. Our Canva is loaded with all of our branded content including brand colors, fonts, logo variations, photos, graphic elements, templates, and more. Canva also has a large library of content that can be used in creations.<br />
<br />
== Hootsuite == <br />
Hootsuite is a social media management platform that we use to schedule posts across multiple social media platforms.<br />
<br />
== Basecamp == <br />
Basecamp is a simple, web-based project management platform. We use it for coordinating and planning tasks for special events and various ongoing projects.<br />
<br />
== SignUpGenius == <br />
SignUpGenius is used for organizing volunteers for special events. It allows us to create a page for the volunteer event and list options for tasks volunteers can easily sign up for without having to create an account.<br />
<br />
<br />
<br />
=Deprecated Services=<br />
== Smartwaiver ==<br />
We used to use Smartwaiver for tracking liability waivers from members and visitors. All active e-sign documents have been moved to SignNow, but we maintain our SmartWaiver account so we can access the document archive.<br />
<br />
== Freshbooks ==<br />
ATXHS used to use Freshbooks for member invoicing before they switched to Neon. We still have some old-school members who never bothered to make Neon accounts, so we're keeping Freshbooks around as long as they keep renewing their memberships.<br />
<br />
Since a Neon account is required for facility access via OpenPath, any remaining Freshbooks members are basically inactive supporters. We appreciate them!<br />
<br />
[[Category:Operations]]</div>Jonhttps://wiki.asmbly.org/index.php?title=Offsite_Services&diff=3134Offsite Services2024-10-17T01:39:26Z<p>Jon: </p>
<hr />
<div>This page is a summary of all the off-site/third-party/cloud services utilized by Asmbly and how we use them.<br />
<br />
= Current Systems = <br />
== Neon == <br />
Neon is our member management system. We intend for it to be the sole interface for administrative tasks and the source of truth for member authentication and authorization. We've been pretty successful at the latter, less so with the former -- board members and some volunteer leads still juggle multiple dashboards to some extent.<br />
<br />
Neon account creation starts with the [https://asmbly.org/join/ Join Form] on the website.<br />
Existing users may log into Neon at https://asmbly.z2systems.com/login.jsp<br />
<br />
Neon is a cloud service and has an [https://developer.neoncrm.com/api-v2/ API]<br />
<br />
== OpenPath ==<br />
OpenPath is our access control system. It has its own user database, but that database is automatically synced with Neon account information. Board members and some stewards have permission to access the OpenPath dashboard to modify user permissions, view access logs, and suchlike.<br />
<br />
OpenPath is a cloud service and has an [https://openpath.readme.io/reference API]<br />
<br />
== Skedda ==<br />
Skedda is the group calendaring tool we're using to schedule access to the space.<br />
<br />
Skedda has its own credential database that requires manual management of user permissions. It also unfortunately lacks any kind of published API. We have a medium-term goal of implementing some mechanism to update Skedda automatically based on member status changes in Neon, but no work is being done on that project at this time.<br />
<br />
For permission to book Asmbly spaces on Skedda, you must first sign up using the private invitation link you can find in your subscription acknowledgement email or the members-only message area of Discourse. https://yo.asmbly.org/t/skedda-invite-link/203. You might be signed into Discourse and you must be a member of the "makers" (paying members) group to view the link.<br />
<br />
Once you have created your Skedda account, you can log into Skedda directly at https://asmbly.skedda.com.<br />
<br />
== Discourse ==<br />
Discourse is the software that powers the Asmbly discussion site https://yo.asmbly.org/<br />
<br />
Discourse maintains its own credential database that requires manual management of user permissions. We have some periodic maintenance scripts that update Discourse users automatically in response to member status changes. As of now we don't plan to change Discourse to authenticate directly against Neon, because we can have Discourse users who are not and have never been Asmbly members and we don't want to put a bunch of non-members in Neon.<br />
<br />
Asmbly Discourse is hosted off site and has an [https://docs.discourse.org API]<br />
<br />
== SignNow ==<br />
Some time back we switched our e-sign stuff from Smartwaiver to SignNow. New-and-improve features include emailing signers copies of their documents, and uploading them to Asmbly's Gdrive. SignNow *kind of* has an API -- it can trigger [https://zapier.com/apps/signnow/integrations Zapier], which is good enough for us.<br />
<br />
== Zapier ==<br />
Zapier is a sorta no-code cloud workflow automation service. It supports limited webhook-style automations, but fortunately one of the actions is "execute arbitrary Python code" so we can do whatever we want in response to a SignNow document or Google Forms submission.<br />
<br />
== Mediawiki ==<br />
The Asmbly wiki runs on Mediawik. The ATXHS wiki did as well, but became a maintenance sink so we're no longer keeping that online. <br />
<br />
The Asmbly wiki authenticates users via Discourse -- if you have an Asmbly Discourse account, you also have a wiki account.<br />
<br />
Both wikis are self-hosted off site on AWS.<br />
<br />
== Wordpress ==<br />
The [http://www.asmbly.org public-facing website] runs on Wordpress. <br />
<br />
Wordpress is hosted off site and has an [https://developer.wordpress.org/rest-api/ API]<br />
<br />
== QuickBooks ==<br />
We use QuickBooks for our banking and accounts payable. Instructors are paid via QuickBooks.<br />
<br />
== PayPal ==<br />
We use PayPal for generating miscellaneous invoices, including Co-Working and storage rentals. This is partially a workaround for the fact that Neon doesn't support multiple concurrent subscriptions for a user (ie you couldn't have both a membership subscription and a storage rental subscription that both automatically renew month-to-month).<br />
<br />
== Square ==<br />
We use Square for easier checkout of supplies that can be purchased onsite at Asmbly.<br />
<br />
== Google Workspace ==<br />
Space leadership uses Google Workspace for mail, document sharing, the usual office stuff. As a non-profit organization we can use it free of charge. Many volunteers also use Asmbly's Google Workspace and we have a Shared Drive that is open for all in the Asmbly domain.<br />
<br />
== Slack == <br />
Space leadership uses Slack for day-to-day operational communications.<br />
<br />
== 1Password == <br />
1Password is a password manager which Asmbly uses to store all passwords for Asmbly accounts and securely share them with relevant parties. Asmbly has a Teams account with a limited number of seats.<br />
<br />
== Clockify == <br />
Clockify is a free time tracking software. We use it for our hourly staff to track time for wages.<br />
<br />
== TechSoup == <br />
TechSoup is a nonprofit organization that provides other nonprofits with access to software and technology at discounted prices. We use this resource for discounts on AWS and other subscription services we use. Each time we consider adding new services, we check TechSoup to ensure we're getting the best option for the best price.<br />
<br />
== Mailchimp ==<br />
Mailchimp is used for our email announcements and monthly(ish) update / newsletter mailings. We are currently evaluating Flodesk and may migrate away from Mailchimp. <br />
<br />
Users may sign up for the list [http://eepurl.com/gZuGvz here]<br />
Users may unsubscribe from the list using personalized links in the footer of each Mailchimp email.<br />
<br />
( Administrative question: Are users automatically added to the mail chimp list at some point in the signup process? Answer: No, not currently. We periodically export all Neon users as CSV to update our mailing list.) <br />
<br />
Mailchimp is a cloud service and has an [https://mailchimp.com/developer/ API]<br />
<br />
== Flodesk ==<br />
Flodesk is used for our email announcements and monthly(ish) update / newsletter mailings. <br />
<br />
Users may sign up for the list [https://asmbly.myflodesk.com/rgwdmleitd here]<br />
Users may unsubscribe from the list using personalized links in the footer of each Flodesk email. <br />
<br />
Flodesk is a cloud service and has an [https://developers.flodesk.com/ API] <br />
<br />
== Canva == <br />
Canva is a web-based content creation app that allows for creating a wide range of types of content and directly ordering prints. We use Canva for branded content creation including flyers, social media posts, animations, slide decks, signage, and more. As a non-profit organization we have a Pro account free of charge. Our Canva is loaded with all of our branded content including brand colors, fonts, logo variations, photos, graphic elements, templates, and more. Canva also has a large library of content that can be used in creations.<br />
<br />
== Hootsuite == <br />
Hootsuite is a social media management platform that we use to schedule posts across multiple social media platforms.<br />
<br />
== Basecamp == <br />
Basecamp is a simple, web-based project management platform. We use it for coordinating and planning tasks for special events and various ongoing projects.<br />
<br />
== SignUpGenius == <br />
SignUpGenius is used for organizing volunteers for special events. It allows us to create a page for the volunteer event and list options for tasks volunteers can easily sign up for without having to create an account.<br />
<br />
<br />
<br />
=Deprecated Services=<br />
== Smartwaiver ==<br />
We used to use Smartwaiver for tracking liability waivers from members and visitors. All active e-sign documents have been moved to SignNow, but we maintain our SmartWaiver account so we can access the document archive.<br />
<br />
== Freshbooks ==<br />
ATXHS used to use Freshbooks for member invoicing before they switched to Neon. We still have some old-school members who never bothered to make Neon accounts, so we're keeping Freshbooks around as long as they keep renewing their memberships.<br />
<br />
Since a Neon account is required for facility access via OpenPath, any remaining Freshbooks members are basically inactive supporters. We appreciate them!<br />
<br />
[[Category:Operations]]</div>Jonhttps://wiki.asmbly.org/index.php?title=Main_Page&diff=2933Main Page2024-06-14T04:10:26Z<p>Jon: </p>
<hr />
<div>{{ToolPhoto|asmbly_mural.png}}<br />
<br />
Welcome to the Asmbly Makerspace Wiki. If you're just browsing, here are some popular categories:<br />
<br />
<!-- Exclude system categories and categories related to hosted tool ownership<br />
...Scribunto has a *lot* of system categories! --><br />
<tagcloud>exclude=Overhauling,Overhauled,Stubs,Legacy_Classes,Boneyard,Covid,Danny_Miller_Owned,Joe_Ngo_Owned,Jeff_McAdams_Owned,Sarah_James_Owned,Pages_with_broken_file_links,Training_Required,James_Manley_Owned,Scott_Wynd_Owned,Jon_Eklund_Owned,James_Freeman_Owned,Stephannie_Behrens_Owned,Russell_Miller_Owned,Extra_Cost,Articles_with_excerpts,Lua-based_templates,Articles_with_broken_excerpts,Pages_with_TemplateStyles_errors,Pages_with_incorrect_protection_templates,Module_test_cases,Modules_in_beta,Pages_with_script_errors,Scribunto_modules_with_errors,TemplateStyles_stylesheets_with_errors,Template_documentation_pages,Modules_subject_to_page_protection,Pages_used_in_system_messages_needing_protection,Lua_metamodules,Pages_with_ignored_display_titles</tagcloud></div>Jonhttps://wiki.asmbly.org/index.php?title=Main_Page&diff=2932Main Page2024-06-14T04:09:59Z<p>Jon: </p>
<hr />
<div>{{ToolPhoto|asmbly_mural.png}}<br />
<br />
Welcome to the Asmbly Makerspace Wiki. If you're just browsing, here are some popular categories:<br />
<br />
<!-- Exclude system categories and categories related to hosted tool ownership<br />
...Scribunto has a *lot* of system categories! --><br />
<tagcloud>exclude=Overhauling,Overhauled,Legacy_Classes,Boneyard,Covid,Danny_Miller_Owned,Joe_Ngo_Owned,Jeff_McAdams_Owned,Sarah_James_Owned,Pages_with_broken_file_links,Training_Required,James_Manley_Owned,Scott_Wynd_Owned,Jon_Eklund_Owned,James_Freeman_Owned,Stephannie_Behrens_Owned,Russell_Miller_Owned,Extra_Cost,Articles_with_excerpts,Lua-based_templates,Articles_with_broken_excerpts,Pages_with_TemplateStyles_errors,Pages_with_incorrect_protection_templates,Module_test_cases,Modules_in_beta,Pages_with_script_errors,Scribunto_modules_with_errors,TemplateStyles_stylesheets_with_errors,Template_documentation_pages,Modules_subject_to_page_protection,Pages_used_in_system_messages_needing_protection,Lua_metamodules,Pages_with_ignored_display_titles</tagcloud></div>Jonhttps://wiki.asmbly.org/index.php?title=Main_Page&diff=2931Main Page2024-06-14T04:09:29Z<p>Jon: </p>
<hr />
<div>{{ToolPhoto|asmbly_mural.png}}<br />
<br />
Welcome to the Asmbly Makerspace Wiki. If you're just browsing, here are some popular categories:<br />
<br />
<!-- Exclude system categories and categories related to hosted tool ownership<br />
...Scribunto has a *lot* of system categories! --><br />
<tagcloud>exclude=Overhauling,Overhauled,Boneyard,Covid,Danny_Miller_Owned,Joe_Ngo_Owned,Jeff_McAdams_Owned,Sarah_James_Owned,Pages_with_broken_file_links,Training_Required,James_Manley_Owned,Scott_Wynd_Owned,Jon_Eklund_Owned,James_Freeman_Owned,Stephannie_Behrens_Owned,Russell_Miller_Owned,Extra_Cost,Articles_with_excerpts,Lua-based_templates,Articles_with_broken_excerpts,Pages_with_TemplateStyles_errors,Pages_with_incorrect_protection_templates,Module_test_cases,Modules_in_beta,Pages_with_script_errors,Scribunto_modules_with_errors,TemplateStyles_stylesheets_with_errors,Template_documentation_pages,Modules_subject_to_page_protection,Pages_used_in_system_messages_needing_protection,Lua_metamodules,Pages_with_ignored_display_titles</tagcloud></div>Jonhttps://wiki.asmbly.org/index.php?title=Precision_Matthews_1054TV_Mill&diff=2796Precision Matthews 1054TV Mill2024-01-12T15:12:51Z<p>Jon: </p>
<hr />
<div>{{ToolUnavailable}}<br />
The Precision Matthews 1054-TV is a Bridgeport-style knee mill featuring 3-axis DRO, 3-axis power feed, and a power drawbar. It's used for accurately machining/drilling metals and other materials.<br />
<br />
The power head is 3hp variable-speed with back gear for a total speed range of 70-4200rpm. Speed control is mechanical, so reducing speed increases torque.<br />
<br />
{{Required|Manual Milling}}<br />
<br />
{{ToolPhoto|PM1054TV.jpg}}<br />
<br />
== Controls ==<br />
[[File:Screenshot 2024-01-12 at 8.53.28 AM.png|left|500px]]<br />
{| class="wikitable"<br />
|+<br />
|4<br />
|Back Gear Selector<br />
|-<br />
|5<br />
|Spindle Brake<br />
|-<br />
|6<br />
|Spindle Speed Control<br />
|-<br />
|7<br />
|Motor Switch<br />
|-<br />
|8<br />
|Quill Auto Feed On/Off<br />
|-<br />
|9<br />
|Quill Fine Feed Handwheel<br />
|-<br />
|10<br />
|Quill Auto Feed Rate Selector<br />
|-<br />
|11<br />
|Quill Auto Feed Direction Plunger<br />
|-<br />
|12<br />
|Quill Auto Feed Lever<br />
|-<br />
|13<br />
|Micrometer Depth Stop<br />
|-<br />
|14<br />
|Quill Lock<br />
|-<br />
|15<br />
|Quill Manual Feed Handle<br />
|}<br />
<br />
<br style="clear:both" /><br />
== Specifications ==<br />
{| class="wikitable"<br />
|+<br />
|Table Length<br />
|54"<br />
|-<br />
|Table Depth<br />
|10"<br />
|-<br />
|Overall Width (A)<br />
|107"<br />
|-<br />
|X axis travel<br />
|36"<br />
|-<br />
|Y axis travel<br />
|15"<br />
|-<br />
|Z axis (knee) travel<br />
|16.9"<br />
|-<br />
|Spindle nose to table surface (min)<br />
|2"<br />
|-<br />
|(max)<br />
|26"<br />
|-<br />
|Spindle centerline to Z ways (min)<br />
|5.5"<br />
|-<br />
|max<br />
|26"<br />
|-<br />
|Ram travel<br />
|20"<br />
|-<br />
|Quill travel<br />
|5"<br />
|-<br />
|Head Tilt Left/Right<br />
|±90º<br />
|-<br />
|Head Tilt Front/Back ("nod")<br />
|±45º<br />
|-<br />
|Turret Rotation<br />
|360º<br />
|-<br />
|approximate weight<br />
|3000lbs<br />
|}<br />
{{ToolPhoto|PM1054_Floorplan.png}}<br />
<br />
== Accessories ==<br />
The table is equipped with 16mm (5/8" compatible) T-slots.<br />
<br />
== Tooling ==<br />
This mill uses the same R8 collet system as the [[Rong Fu RF-45 Mill]] so any mill tooling we have will fit either machine. The bigger motor on the PM1054 means it can run bigger tools and/or work tougher materials than the RF-45. Pay attention to your speeds and feeds!<br />
<br />
== Resources ==<br />
* [[Media:PM1054 manual.pdf|Manual]]<br />
<br />
{{Owned}}<br />
[[Category:Machining]]</div>Jonhttps://wiki.asmbly.org/index.php?title=Precision_Matthews_1054TV_Mill&diff=2795Precision Matthews 1054TV Mill2024-01-12T15:00:15Z<p>Jon: </p>
<hr />
<div>{{ToolUnavailable}}<br />
The Precision Matthews 1054-TV is a Bridgeport-style knee mill featuring 3-axis DRO, 3-axis power feed, and a power drawbar. It's used for accurately machining/drilling metals and other materials.<br />
<br />
The power head is 3hp variable-speed with back gear for a total speed range of 70-4200rpm.<br />
<br />
{{Required|Manual Milling}}<br />
<br />
{{ToolPhoto|PM1054TV.jpg}}<br />
<br />
== Controls ==<br />
[[File:Screenshot 2024-01-12 at 8.53.28 AM.png|left|thumb]]<br />
{| class="wikitable"<br />
|+<br />
|4<br />
|Back Gear Selector<br />
|-<br />
|5<br />
|Spindle Brake<br />
|-<br />
|6<br />
|Spindle Speed Control<br />
|-<br />
|7<br />
|Motor Switch<br />
|-<br />
|8<br />
|Quill Auto Feed On/Off<br />
|-<br />
|9<br />
|Quill Fine Feed Handwheel<br />
|-<br />
|10<br />
|Quill Auto Feed Rate Selector<br />
|-<br />
|11<br />
|Quill Auto Feed Direction Plunger<br />
|-<br />
|12<br />
|Quill Auto Feed Lever<br />
|-<br />
|13<br />
|Micrometer Depth Stop<br />
|-<br />
|14<br />
|Quill Lock<br />
|-<br />
|15<br />
|Quill Manual Feed Handle<br />
|}<br />
<br />
== Specifications ==<br />
{| class="wikitable"<br />
|+<br />
|Table Length<br />
|54"<br />
|-<br />
|Table Depth<br />
|10"<br />
|-<br />
|Overall Width (A)<br />
|107"<br />
|-<br />
|X axis travel<br />
|36"<br />
|-<br />
|Y axis travel<br />
|15"<br />
|-<br />
|Z axis (knee) travel<br />
|16.9"<br />
|-<br />
|Spindle nose to table surface (min)<br />
|2"<br />
|-<br />
|(max)<br />
|26"<br />
|-<br />
|Spindle centerline to Z ways (min)<br />
|5.5"<br />
|-<br />
|max<br />
|26"<br />
|-<br />
|Ram travel<br />
|20"<br />
|-<br />
|Quill travel<br />
|5"<br />
|-<br />
|Head Tilt Left/Right<br />
|±90º<br />
|-<br />
|Head Tilt Front/Back ("nod")<br />
|±45º<br />
|-<br />
|Turret Rotation<br />
|360º<br />
|-<br />
|approximate weight<br />
|3000lbs<br />
|}<br />
{{ToolPhoto|PM1054_Floorplan.png}}<br />
<br />
== Accessories ==<br />
The table is equipped with 16mm (5/8" compatible) T-slots.<br />
<br />
== Tooling ==<br />
This mill uses the same R8 collet system as the [[Rong Fu RF-45 Mill]] so any mill tooling we have will fit either machine. The bigger motor on the PM1054 means it can run bigger tools and/or work tougher materials than the RF-45. Pay attention to your speeds and feeds!<br />
<br />
== Resources ==<br />
* [[Media:PM1054 manual.pdf|Manual]]<br />
<br />
{{Owned}}<br />
[[Category:Machining]]</div>Jonhttps://wiki.asmbly.org/index.php?title=File:Screenshot_2024-01-12_at_8.53.28_AM.png&diff=2794File:Screenshot 2024-01-12 at 8.53.28 AM.png2024-01-12T14:59:32Z<p>Jon: </p>
<hr />
<div>Head controls of PM935-series mill</div>Jonhttps://wiki.asmbly.org/index.php?title=Precision_Matthews_1054TV_Mill&diff=2793Precision Matthews 1054TV Mill2024-01-12T14:53:42Z<p>Jon: </p>
<hr />
<div>{{ToolUnavailable}}<br />
The Precision Matthews 1054-TV is a Bridgeport-style knee mill featuring 3-axis DRO, 3-axis power feed, and a power drawbar. It's used for accurately machining/drilling metals and other materials.<br />
<br />
The power head is 3hp variable-speed with back gear for a total speed range of 70-4200rpm.<br />
<br />
{{Required|Manual Milling}}<br />
<br />
{{ToolPhoto|PM1054TV.jpg}}<br />
<br />
== Specifications ==<br />
{| class="wikitable"<br />
|+<br />
|Table Length<br />
|54"<br />
|-<br />
|Table Depth<br />
|10"<br />
|-<br />
|Overall Width (A)<br />
|107"<br />
|-<br />
|X axis travel<br />
|36"<br />
|-<br />
|Y axis travel<br />
|15"<br />
|-<br />
|Z axis (knee) travel<br />
|16.9"<br />
|-<br />
|Spindle nose to table surface (min)<br />
|2"<br />
|-<br />
|(max)<br />
|26"<br />
|-<br />
|Spindle centerline to Z ways (min)<br />
|5.5"<br />
|-<br />
|max<br />
|26"<br />
|-<br />
|Ram travel<br />
|20"<br />
|-<br />
|Quill travel<br />
|5"<br />
|-<br />
|Head Tilt Left/Right<br />
|±90º<br />
|-<br />
|Head Tilt Front/Back ("nod")<br />
|±45º<br />
|-<br />
|Turret Rotation<br />
|360º<br />
|-<br />
|approximate weight<br />
|3000lbs<br />
|}<br />
{{ToolPhoto|PM1054_Floorplan.png}}<br />
<br />
== Accessories ==<br />
The table is equipped with 16mm (5/8" compatible) T-slots.<br />
<br />
== Tooling ==<br />
This mill uses the same R8 collet system as the [[Rong Fu RF-45 Mill]] so any mill tooling we have will fit either machine. The bigger motor on the PM1054 means it can run bigger tools and/or work tougher materials than the RF-45. Pay attention to your speeds and feeds!<br />
<br />
== Resources ==<br />
* [[Media:PM1054 manual.pdf|Manual]]<br />
<br />
{{Owned}}<br />
[[Category:Machining]]</div>Jonhttps://wiki.asmbly.org/index.php?title=Precision_Matthews_1054TV_Mill&diff=2792Precision Matthews 1054TV Mill2024-01-12T14:45:28Z<p>Jon: </p>
<hr />
<div>{{ToolUnavailable}}<br />
The Precision Matthews 1054-TV knee mill is a 3HP variable-speed Bridgeport-style knee mill featuring 3-axis DRO, 3-axis power feed, and a power drawbar. It's used for accurately machining/drilling metals and other materials.<br />
<br />
{{Required|Manual Milling}}<br />
<br />
{{ToolPhoto|PM1054TV.jpg}}<br />
<br />
== Specifications ==<br />
<br />
<br />
{| class="wikitable"<br />
|+<br />
|Table Length<br />
|54"<br />
|-<br />
|Table Depth<br />
|10"<br />
|-<br />
|Overall Width (A)<br />
|107"<br />
|-<br />
|X axis travel<br />
|36"<br />
|-<br />
|Y axis travel<br />
|15"<br />
|-<br />
|Z axis (knee) travel<br />
|16.9"<br />
|-<br />
|Spindle nose to table surface (min)<br />
|2"<br />
|-<br />
|(max)<br />
|26"<br />
|-<br />
|Spindle centerline to Z ways (min)<br />
|5.5"<br />
|-<br />
|max<br />
|26"<br />
|-<br />
|Ram travel<br />
|20"<br />
|-<br />
|Quill travel<br />
|5"<br />
|-<br />
|Head Tilt Left/Right<br />
|±90º<br />
|-<br />
|Head Tile Front/Back ("nod")<br />
|±45º<br />
|-<br />
|approximate weight<br />
|3000lbs<br />
|}<br />
{{ToolPhoto|PM1054_Floorplan.png}}<br />
<br />
== Accessories ==<br />
<br />
<br />
== Tooling ==<br />
This mill uses the same R8 collet system as the [[Rong Fu RF-45 Mill]] so any mill tooling we have will fit either machine. The bigger motor on the PM1054 means it can run bigger tools and/or work tougher materials than the RF-45. Pay attention to your speeds and feeds!<br />
<br />
== Resources ==<br />
* [[Media:PM1054 manual.pdf|Manual]]<br />
<br />
{{Owned}}<br />
[[Category:Machining]]</div>Jonhttps://wiki.asmbly.org/index.php?title=Precision_Matthews_1054TV_Mill&diff=2791Precision Matthews 1054TV Mill2024-01-12T14:41:35Z<p>Jon: </p>
<hr />
<div>{{ToolUnavailable}}<br />
The Precision Matthews 1054-TV knee mill is a 3HP variable-speed Bridgeport-style knee mill featuring 3-axis DRO, 3-axis power feed, and a power drawbar. It's used for accurately machining/drilling metals and other materials.<br />
<br />
{{Required|Manual Milling}}<br />
<br />
{{ToolPhoto|PM1054TV.jpg}}<br />
<br />
== Specifications ==<br />
<br />
<br />
{| class="wikitable"<br />
|+<br />
|Table Length<br />
|54"<br />
|-<br />
|Table Depth<br />
|10"<br />
|-<br />
|Overall Width (A)<br />
|107"<br />
|-<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|}<br />
{{ToolPhoto|PM1054_Floorplan.png}}<br />
<br />
== Accessories ==<br />
<br />
<br />
== Tooling ==<br />
This mill uses the same R8 collet system as the [[Rong Fu RF-45 Mill]] so any mill tooling we have will fit either machine. The bigger motor on the PM1054 means it can run bigger tools and/or work tougher materials than the RF-45. Pay attention to your speeds and feeds!<br />
<br />
== Resources ==<br />
* [[Media:PM1054 manual.pdf|Manual]]<br />
<br />
{{Owned}}<br />
[[Category:Machining]]</div>Jonhttps://wiki.asmbly.org/index.php?title=File:PM1054_Floorplan.png&diff=2789File:PM1054 Floorplan.png2024-01-12T14:39:30Z<p>Jon: </p>
<hr />
<div></div>Jonhttps://wiki.asmbly.org/index.php?title=File:PM1054_manual.pdf&diff=2788File:PM1054 manual.pdf2024-01-12T14:39:02Z<p>Jon: </p>
<hr />
<div></div>Jonhttps://wiki.asmbly.org/index.php?title=Precision_Matthews_1054TV_Mill&diff=2786Precision Matthews 1054TV Mill2024-01-12T14:38:44Z<p>Jon: Created page with "{{ToolUnavailable}} The Precision Matthews 1054-TV knee mill is a 3HP variable-speed Bridgeport-style knee mill featuring 3-axis DRO, 3-axis power feed, and a power drawbar...."</p>
<hr />
<div>{{ToolUnavailable}}<br />
The Precision Matthews 1054-TV knee mill is a 3HP variable-speed Bridgeport-style knee mill featuring 3-axis DRO, 3-axis power feed, and a power drawbar. It's used for accurately machining/drilling metals and other materials.<br />
<br />
{{Required|Manual Milling}}<br />
<br />
{{ToolPhoto|PM1054TV.jpg}}<br />
<br />
== Specifications ==<br />
<br />
<br />
{{ToolPhoto|PM1054_Floorplan.png}}<br />
<br />
== Accessories ==<br />
<br />
<br />
== Tooling ==<br />
This mill uses the same R8 collet system as the [[Rong Fu RF-45 Mill]] so any mill tooling we have will fit either machine. The bigger motor on the PM1054 means it can run bigger tools and/or work tougher materials than the RF-45. Pay attention to your speeds and feeds!<br />
<br />
== Resources ==<br />
* [[Media:PM1054_manual.pdf|Manual]]<br />
<br />
{{Owned}}<br />
[[Category:Machining]]</div>Jonhttps://wiki.asmbly.org/index.php?title=TandyPro_Edging_%26_Creasing&diff=2775TandyPro Edging & Creasing2024-01-03T01:52:32Z<p>Jon: Jon moved page TandyPro Edging Creasing to TandyPro Edging & Creasing without leaving a redirect</p>
<hr />
<div><br />
Use the edging and creasing machine for all kinds of freehand decorative work.<br />
<br />
{{ToolPhoto|TandyPro_Edging_Creasing.jpg}}<br />
<br />
== Resources ==<br />
* [[Media:TandyPro_Edging_Creasing_manual.pdf|Instruction Manual]]<br />
<br />
{{Owned}}<br />
[[Category:Leatherworking]]</div>Jonhttps://wiki.asmbly.org/index.php?title=Brother_SE625_Embroidery_Machine&diff=2773Brother SE625 Embroidery Machine2023-12-29T02:08:22Z<p>Jon: </p>
<hr />
<div>The Brother SE625 is a computerized sewing machine with capability to embroider 4x4 inches. [https://wiki.asmbly.org/index.php/Designing_for_the_Brother_Embroidery_Machine This page] gives more information on how to design and import your own designs<br />
<br />
{{ToolPhoto|Brother_SE625.jpg}}<br />
<br />
== Resources ==<br />
* [[Media:Se600 quick reference.pdf|Quick Reference]]<br />
* [[Media:Se600 operation manual.pdf|Operation Manual]]<br />
* [[Media:Se600 embroidery design guide.pdf|Embroidery Design Guide]]<br />
<br />
{{Owned}}<br />
[[Category:Textiles]]</div>Jonhttps://wiki.asmbly.org/index.php?title=File:Brother_SE625.jpg&diff=2772File:Brother SE625.jpg2023-12-29T01:57:43Z<p>Jon: </p>
<hr />
<div></div>Jonhttps://wiki.asmbly.org/index.php?title=Brother_SE625_Embroidery_Machine&diff=2771Brother SE625 Embroidery Machine2023-12-29T01:56:16Z<p>Jon: Created page with "The Brother SE625 is a computerized sewing machine with capability to embroider 4x4 inches. [https://wiki.asmbly.org/index.php/Designing_for_the_Brother_Embroidery_Machine Thi..."</p>
<hr />
<div>The Brother SE625 is a computerized sewing machine with capability to embroider 4x4 inches. [https://wiki.asmbly.org/index.php/Designing_for_the_Brother_Embroidery_Machine This page] gives more information on how to design and import your own designs<br />
<br />
{{ToolPhoto|Brother_SE625.jpg}}<br />
<br />
== Resources ==<br />
* [[Media:Se625 quick reference.pdf|Quick Reference]]<br />
* [[Media:Se625 operation manual.pdf|Operation Manual]]<br />
* [[Media:Se625 embroidery design guide.pdf|Embroidery Design Guide]]<br />
<br />
{{Owned}}<br />
[[Category:Textiles]]</div>Jonhttps://wiki.asmbly.org/index.php?title=Boss_FC-6012_PRO_Fiber_Laser&diff=2769Boss FC-6012 PRO Fiber Laser2023-12-28T02:08:59Z<p>Jon: </p>
<hr />
<div>{{ToolUnavailable}}<br />
<br />
Asmbly has purchased a gently used Boss FC-6012 PRO fiber laser. We're currently getting it set up and developing training materials.<br />
<br />
{{Required|Fiber Laser}}<br />
<br />
<big>THIS IS A CLASS 4 LASER DEVICE! EYE PROTECTION IS REQUIRED! WORK AREA PROTECTION IS REQUIRED!</big><br />
<br />
{{ToolPhoto|Boss_FC-6012.jpg}}<br />
<br />
This machine is equipped with a 700W IPG source and a 5'x10' sawtooth work area.<br />
<br />
This system consists of<br />
*Boss FC-6012 Pro CNC chassis<br />
*IPG YLR-700-MM-WC fiber laser source<br />
*RayTools BT240S laser cutting head<br />
*S&A CWFL-1000BN recirculating chiller<br />
<br />
==Material Capacity==<br />
*Mild Steel 6mm<br />
*Stainless Steel 3mm<br />
*Aluminum 2mm<br />
<br />
==Resources==<br />
*[[Media:IPG_YLR_Series.pdf|IPG YLR Laser Manual]]<br />
*[[Media:Raytools_BT240S.pdf|BT240 series Manual]]<br />
*[[Media:SA_CWFL_Series.pdf|S&A CWFL series Manual]]<br />
<br />
{{Owned}}<br />
[[Category:Metal_Shop]]</div>Jonhttps://wiki.asmbly.org/index.php?title=Boss_FC-6012_PRO_Fiber_Laser&diff=2768Boss FC-6012 PRO Fiber Laser2023-12-28T02:06:36Z<p>Jon: </p>
<hr />
<div>{{ToolUnavailable}}<br />
<br />
Asmbly has purchased a gently used Boss FC-6012 PRO fiber laser. We're currently getting it set up and developing training materials.<br />
<br />
{{Required|Fiber Laser}}<br />
<br />
<big>THIS IS A CLASS 4 LASER DEVICE! EYE PROTECTION IS REQUIRED! WORK AREA PROTECTION IS REQUIRED!</big><br />
<br />
{{ToolPhoto|Boss_FC-6012.jpg}}<br />
<br />
This machine is equipped with a 700W IPG source and a 5'x10' sawtooth work area.<br />
<br />
This system consists of<br />
*Boss FC-6012 Pro CNC chassis<br />
*IPG YLR-700-MM-WC fiber laser source<br />
*RayTools BT240S laser cutting head<br />
*S&A CWFL-1000BN recirculating chiller<br />
<br />
==Material Capacity==<br />
*Mild Steel 6mm<br />
*Stainless Steel 3mm<br />
*Aluminum 2mm<br />
<br />
==Resources==<br />
*[[Media:IPG_YLR_Series.pdf|IPG YLR Laser Manual]]<br />
*[[Media:Raytools_BT240S.pdf|BT240 series Manual]]<br />
*[[Media:SA_CWFL_Series.pdf|S&A CWFL series Manual]]<br />
<br />
{{Owned}}<br />
[[Category:Metalworking]]</div>Jonhttps://wiki.asmbly.org/index.php?title=File:Boss_FC-6012.jpg&diff=2767File:Boss FC-6012.jpg2023-12-28T02:05:20Z<p>Jon: </p>
<hr />
<div></div>Jonhttps://wiki.asmbly.org/index.php?title=File:IPG_YLR_Series.pdf&diff=2766File:IPG YLR Series.pdf2023-12-28T02:01:58Z<p>Jon: </p>
<hr />
<div></div>Jonhttps://wiki.asmbly.org/index.php?title=File:Raytools_BT240S.pdf&diff=2765File:Raytools BT240S.pdf2023-12-28T02:01:41Z<p>Jon: </p>
<hr />
<div></div>Jonhttps://wiki.asmbly.org/index.php?title=File:SA_CWFL_Series.pdf&diff=2764File:SA CWFL Series.pdf2023-12-28T02:01:27Z<p>Jon: </p>
<hr />
<div></div>Jonhttps://wiki.asmbly.org/index.php?title=Fiber_Laser_Class&diff=2763Fiber Laser Class2023-12-28T02:00:42Z<p>Jon: </p>
<hr />
<div>Asmbly is developing a class for use of the new fiber laser.<br />
<br />
{{ClassFooter}}</div>Jonhttps://wiki.asmbly.org/index.php?title=Fiber_Laser_Class&diff=2762Fiber Laser Class2023-12-28T02:00:34Z<p>Jon: </p>
<hr />
<div>Asmbly is developing a class for use of the new fiber laser.<br />
<br />
[[Category:Classes]]</div>Jonhttps://wiki.asmbly.org/index.php?title=Fiber_Laser_Class&diff=2761Fiber Laser Class2023-12-28T02:00:24Z<p>Jon: </p>
<hr />
<div>Asmbly is developing a class for use of the new fiber laser.<br />
<br />
[[Classes]]</div>Jon