Volunteer Beta Testing
Try InkRider before general release, report what breaks, and help us polish the Word add-in. Participation is invitation-based, voluntary, and not paid work.
Voluntary and unpaid
Beta testing is a volunteer program. You choose whether to participate, how much time to spend, and whether to file reports.
InkRider does not pay wages, fees, or other compensation for testing or feedback unless we agree otherwise in a separate signed agreement.
When your account is enrolled, you must accept the Volunteer Beta Testing Agreement in the app before using pre-release access.
Full legal terms: Volunteer Beta Testing Agreement
What testers may receive
Perks vary by cohort and are not guaranteed. We will tell you what applies when your access is enabled.
Early access
Use pre-release builds and features before they are broadly available.
Complimentary plan access
During the program, we may grant complimentary access that mirrors a paid plan tier (for example Pro) so you can exercise real workflows.
Direct influence
Your bug reports and feedback help prioritize fixes and shape launch quality.
Launch consideration
Active testers may be offered discounted paid plans or extended trials after the program ends. This is discretionary, not a entitlement.
How to join
We enroll testers manually after you have an InkRider account.
- 1
Create an account
Register with the email you want us to enable. If you already have an account, you can use that instead.
- 2
Tell us you are interested
Reply to your invitation email or contact support with the email on your account and which workflows you plan to test.
- 3
Wait for enrollment
We enable program access and any complimentary tier from the admin console. This is usually within one business day.
- 4
Accept the agreement in the app
On first sign-in after enrollment, review and accept the Volunteer Beta Testing Agreement, then install or open the Word add-in.
How to test effectively
Use realistic documents
Work with copies of real Word files you care about. Save backups before running cells or batch operations.
Exercise your actual workflow
Notebooks, anchoring, runtimes, imports, and batch execution are high-value areas. Try the paths you would use after launch.
Note your environment
Record Windows or Mac, Word desktop vs Word on the web, and approximate Word build if you know it.
Try to reproduce issues
If something fails once, try again with a clean document or fresh session so we can tell flukes from real defects.
Respect confidentiality
Pre-release builds are confidential. Do not post public screenshots or reviews of unreleased features without our written approval.
How to report bugs
Use our public feedback repository for most reports. It keeps issues structured and searchable for a small team.
Include in every report
- Short summary in the title
- Steps to reproduce, in order
- Expected behavior vs what actually happened
- Surface: Word add-in, account dashboard, or website
- Platform: Windows/Mac and Word desktop or web
- Screenshots or screen recordings with confidential content redacted
- InkRider or add-in version if shown in the UI
Do not post passwords, API keys, tokens, or confidential client document content in public issues. Use the contact page for sensitive or security-related reports.
We read every report but cannot guarantee fixes, timelines, or individual replies.
Sensitive reports: support@inkrider.com via the contact page
InkRider beta testing FAQ
Common questions about volunteer testing, reporting, and access.
Ready to help?
Create an account, then reply to your invitation or contact support to request enrollment.