Help & guidance
Operator help
Practical guidance for makerspace operators evaluating or using MakerOps.
What should I bring to a pilot conversation?
Bring your approximate member count, equipment list, current tools and your most time-consuming workflow. Use sample or redacted records, not your full member database.
Can we migrate existing records?
Discuss current exports and required fields first. Import scope, cleanup, responsibilities and migration help must be agreed for your pilot; there is no automatic migration commitment.
How should we report a problem?
Email hello@makeropshq.com with your space name, affected workflow, approximate time and a redacted screenshot if useful. Do not include passwords, card details or a full member export. No public response-time SLA is offered.
How do payments relate to our space?
The product uses a connected payment account for organization payments. Confirm the owner, costs, refund permissions and chargeback responsibilities in your written agreement.
Can this control door hardware?
Do not assume a booking or active membership operates physical access hardware. Discuss specific access-control requirements before selecting a pilot.
Where are contracts and security information?
The trust center explains questions to resolve before onboarding. Request the applicable agreement and security information for your deployment before sending member data.