In this guide1 / 5
Beta approval is separate from staff roles and website sharing. An owner must also allow access through the hosting service when the website has a restricted audience. The owner can pause new requests, approve accounts, assign cohort labels and revoke admission. Revocation preserves saved records and access to feedback and account-data requests.
All supported catalog configurations remain available. A supported printer or valid exported mesh is not evidence that every nozzle, filament or physical combination has been tested. Read Known issues on /beta before starting.
Open /beta and sign in. When approved-account access is enabled, submit a short request describing what you want to test. Return to this page to check its status.
After approval, follow the first-print checklist. Choose your actual printer, nozzle, material and slicer, export a small part and inspect it in the slicer.
Print a small calibration sample, record observations after cooling, and repeat the result before preparing a full plate.
An invitation does not grant an administrative role. Expired, revoked and used links cannot be accepted. Closed entry pauses acceptance, and an invitation cannot restore a revoked or suspended account. Contact the owner when a replacement or access review is needed. Keep the personal link private.
Open the personal invitation link from the Studio owner. The link is intended for one account email and can be used once before its expiry.
Create a Nexlock account and verify its email in the same browser, or sign in with an existing account or Google. Use the account email named by the invitation. For a linked Google login, your canonical Nexlock email is used.
Return to the invitation and choose Accept invitation. Your access is granted only after the server confirms acceptance. If you lose the page during signup, reopen the original link.
New saved parts, fit profiles, defaults, legacy result records and mesh uploads belong to the signed-in account. Older shared records are preserved in an owner-only archive and are not automatically assigned to a tester. Ask the owner to review recovery if you need an older record.
Browser drafts are local to this device and separated by signed-in account. An older device draft is retained separately; it is not silently adopted by a signed-in account. Save important work to your account and export a copy before switching devices.
Private uploads have account storage and upload-rate limits in addition to individual file limits. Open Profile settings → Account data to see usage, review abandoned uploads and request help. Removing an abandoned upload does not remove a file attached to saved work.
Avoid including pairing codes, secrets or unrelated personal information. Feedback is visible to you and authorized staff. Use an approved private delivery method for an account export; a public download link is not appropriate.
Use the support link on /beta, or open Feedback. Include the steps, expected result, observed result and exact printer setup. New reports record the Studio build automatically while the product remains v1.0.0.
For an account export or deletion review, open Profile settings → Account data and submit the request from the affected account.
Track the request in account settings. Staff must verify identity and scope before fulfilling it; submitting a request does not immediately delete records.
Program settings and membership changes retain revisions. The release checklist also requires a monitored health endpoint, a tested database-plus-upload restore, approved-source rollback practice, clean Windows installation and recorded physical prints. Local automated checks do not establish live monitoring or successful physical prints.
In Studio Admin → Beta access, review the welcome text, known issues and support link. Choose Beta for approved testers, Public for open registration, or Closed for owner/staff access, then confirm the reviewed change.
Review each applicant, approve the intended account and assign a cohort label. Confirm access with a separate tester account before widening the audience.
Pause applications when capacity is reached. Use Closed to stop registrations and ordinary member sign-in and Studio access while preserving saved work. The owner and assigned staff retain maintenance access; a revoked member remains blocked from Studio.