Feature Requests

When a class or session is full, let members join a waitlist instead of being turned away, and fill freed spots from it automatically. What this would cover: * Join when full. Members who find a class full can join its waitlist in one step, and see their place in line. * A waitlist size you set per class, or no limit. * Automatic promotion. When someone cancels, the next person on the waitlist gets the spot and is told by email. For paid classes, they get a set time to pay before the spot moves to the next person. * Admins see who is waiting, can move someone up or remove them, and can turn the waitlist on or off for each class. * Full classes show "Join waitlist" instead of disappearing from members' class lists. Today a full class simply refuses new registrations. Upvote or comment if a waitlist would help your space, and tell us how you handle full classes now.

Connect MakerVera to the other tools your makerspace already uses through a documented API, instead of copying data by hand or exporting spreadsheets. What this could include: * Create API keys for your makerspace, each with its own permissions (for example read-only), and revoke them at any time. * Read and update members, memberships, check-ins, equipment bookings, classes and events, and store orders. * Webhooks that notify your own systems when something happens, such as a new member signing up, a membership lapsing, or a class booking. * Public API documentation with examples, and rate limits that suit small scripts as well as larger integrations. Typical uses: syncing members with your CRM, mailing list or accounting software; building custom dashboards or displays in the space; and connecting campus or organisation systems. Upvote if you'd use this, and comment with what you'd connect MakerVera to first.

Use MakerVera in Turkish. Members and admins could pick Türkçe as their language, and a makerspace could set it as its default. The member app, the admin screens and the emails MakerVera sends (receipts, confirmations, reminders) would all appear in Turkish. This would let makerspaces in Turkey, and Turkish-speaking communities elsewhere, run their space without asking members to work in English, Spanish or French, the languages offered today. If you'd use this, vote and tell us in a comment which parts matter most to you first: member screens, admin screens or emails.

Run kids’ and family classes: parents add their children to their account, sign the whole family up in one checkout, and can cover everyone with a family membership. Youth programs are one of the best ways a makerspace grows its community. This feature lets you run them in MakerVera without workarounds. What’s Planned * Households. A member creates a household, adds their children, and invites the other adults in the family. Children don’t need an email or a login. The parent manages everything. * Classes for the right ages. Set an age range on any class, and choose whether it’s drop-off (kids only) or accompanied (kids plus an adult). Families only see the sign-up options that fit. * One checkout for the whole family. Parents pick who’s coming and pay for everyone at once. Children’s tickets use the parent’s member or public price. On accompanied classes you set the adult ticket price, and it can be free. * Accurate class capacity. Every attendee takes a spot, so a class of 12 holds 12 people, whether that’s 12 kids or 4 adults with 8 kids. * Family memberships. Create family plans with your own price, number of adults and number of children. One payer covers the household. * Instructor-ready rosters. Rosters show which attendees are children, their ages, and the parent’s contact details. Attendance works the same as for adults. * Supervised-only authorizations. Equipment authorizations children earn in class are marked supervised-only, and become full authorizations automatically when they become adults. Good to know * Households, youth classes and family memberships are on the Professional plan. * Children never have their own accounts. Every MakerVera account holder must be an adult: 18 or older in most places. * Children’s information is kept to a minimum (name and birthdate), is visible only to their family and your staff, and is never used for analytics. Not included yet: digital waivers, guest tickets for people without an account, and teen accounts. Upvote or comment if those matter to you.

For makerspaces run as not-for-profit corporations: keep the records your board and members' meetings need inside MakerVera instead of a spreadsheet. What this could include: * Mark membership plans as voting or non-voting, and see who your current voting members are. * Export a register of current and former members (name, address, membership class, dates joined and left). * Keep a register of directors and officers with their roles and terms. * Collect a complete mailing address from voting members. * Send an AGM or members' meeting notice to every voting member, even those who turned off announcements, and download proof of who it was sent to. Laws such as Ontario's Not-for-Profit Corporations Act require these records; similar rules exist in other provinces and US states. Upvote if your makerspace is a not-for-profit, and comment with where you're incorporated and which of these you'd use first.

Makerspaces often receive donations through platforms other than MakerVera (GoFundMe, Network for Good, PayPal, a bank transfer). Today those gifts live outside MakerVera, so a member's profile and the makerspace's donation totals only reflect what came through MakerVera checkout. This request adds a way for admins, managers, and accountants to bring those donations into MakerVera: Record a single external donation by hand, or upload a CSV of many at once, with the source platform recorded on each one. Donations are matched to existing member accounts by email. Rows that don't match go to a review screen where you can search for and pick the right account, exclude rows, and then accept or cancel the whole upload. Nothing is saved until you accept. Donors who don't have a MakerVera account are kept as donor records (no account is created for them). If they later sign up with the same email, their past donations attach to the new account automatically. A "Total Donated" figure on each member's profile, a Donations view in the Transactions tab with the source shown on every donation, and a Donations report that breaks giving down by source and by whether the donor has an account. A way to void a donation or an entire upload that was entered by mistake.

Turn a tablet at your front desk or counter into a self-service kiosk for your makerspace. Members check themselves in, and buyers shop your store, without staff having to step in. The printed check-in QR poster you can use today stays free on every plan. Kiosks add stronger check-in and more ways to use a shared screen. What we're thinking * Pair a tablet. Admins pair any tablet to their makerspace as a kiosk, and can remove it at any time. You can run as many kiosks as you like. * Rotating check-in code. The kiosk shows a check-in QR code that changes every 30 seconds, so a photo of the code stops working within about a minute. Members scan it with their phone to check in, and each check-in counts toward their visits like any other. * The kiosk scans the member. Members can instead hold up the card code in their MakerVera app to the tablet camera, or type a personal check-in number. Members without a smartphone can check in too. * Privacy on a shared screen. Kiosk screens show only the member's first name. When a check-in is refused, the kiosk shows the same general message every time, so a member's allowance or account details never appear on screen. * Store kiosk. Put your store on a counter tablet. Buyers build a cart on the kiosk, then pay on their own phone through your makerspace's normal store checkout. No card reader is needed, and the tablet never handles card details. Good to know * Kiosks are a single add-on per makerspace, not billed per device, with a free trial. They're included on the Professional plan. * In the first version, store buyers need a MakerVera account to check out. * If the tablet loses its connection, it shows an offline message rather than recording check-ins. Ideas we're still exploring: waiver and guest sign-in at the kiosk, staff shortcuts (today's bookings and classes), selling day passes at the kiosk, tap-to-pay card readers, store checkout without an account, and check-ins saved while offline. Upvote or comment to tell us which of these matter most to you.

Let members enter the hours in a typical week when they're available. Admins see everyone's availability combined as a heatmap, which shows when an event or class would reach the most people. Schedules change at least every semester, so availability should reset on a regular schedule (for example each term), and members should be asked to update it.

A member may be suspended more than once. Each suspension should require a documented reason and be kept in a history on the member's profile: who suspended them, when, why, and when they were reinstated. Admins should also be able to easily find and review currently suspended members.

Universities and similar organizations often run makerspaces in several locations (sites) under one organization. Requested: group workspaces (and their equipment) under a site, and add a site admin role that can manage only the sites they're assigned to, while organization admins still see everything.