In this guide1 / 17
Sign in and choose Studio Admin from the profile menu on the website or in Designer. The direct address is /admin. The owner has full access; assigned staff roles open only their permitted workspaces. A site invitation alone does not grant an admin role.
The server checks the current mode on protected operations. Closing access also blocks already signed-in ordinary members from Studio and pauses pending signup verification. The owner and assigned staff keep their permitted administrative access. Staff may maintain Studio while Closed unless their admission was revoked. Community titles such as Beta Tester do not grant staff entry. Public still requires a signed-in account in the self-hosted Studio; it does not expose private projects.
Opening registration does not configure email delivery. Email signup, password recovery and adding a password require the owner to finish SMTP setup and verify delivery. An existing configured Google login remains available when email delivery is unavailable.
As the owner, open Studio Admin → Beta access.
Choose Public for open account registration, Beta for registration followed by tester approval, or Closed to pause registrations and ordinary member entry.
Review the impact and confirm the change. Existing approvals and saved work are retained.
Recipients can create their own verified Nexlock login or use Google. Their canonical account email must match. Invitations do not bypass Closed mode, existing revocation or account suspension, and do not change hosting-provider sharing. Administrators can invite ordinary members; owner, staff and their own account are protected. Issued links keep their original authority until expiry or revocation, even if the issuing staff role later changes. Protected-recipient checks run again at acceptance.
As the owner or an Administrator on the self-hosted Studio, open Beta access and its Invitations controls. Enter the intended account email, an optional label and cohort, and an expiry. The default is seven days, with a maximum of thirty days.
Create the invitation and copy its link before closing the result. The full link is shown once; creating it does not send an email. Share it privately with the intended person.
Review pending, claimed, expired and revoked invitations. Revoke an unused link when it should no longer grant access. To remove an already admitted member, use the separate beta membership controls.
Owner identities and your own account are protected from these lockout actions. Administrators and Moderators can manage ordinary members; only the owner can manage other staff. Moderators cannot send recovery emails. Native security controls are unavailable for legacy Sites identities. Changes are audited and checked against the saved revision; reload if another action changed the account. A recovery request confirms queuing, not inbox delivery. No password or recovery link is shown to staff.
As the owner, Administrator or Moderator, open Members and choose Account security for a self-hosted member. Review login methods, active sessions, last sign-in and security history. The owner can also see the account email.
Choose Suspend to block the account and end sessions while preserving its saved work. Reactivate allows a new sign-in under the current beta policy; it does not restore a revoked beta membership.
Choose Sign out all devices to end sessions and invalidate older pending authentication/recovery flows without suspending the account.
As the owner or an Administrator, when email delivery is configured, request a password recovery or setup email. The member chooses their own password privately. Review the action and enter a reason before confirming it.
Administrator manages operational tools, site controls, publishing, badges, member IDs, beta feedback, ordinary-member admissions and invitations, account security and recovery, system readiness and analytics. Editor manages homepage content, roadmaps and What’s New. Moderator manages service status, badges, beta feedback and ordinary-member suspension, reactivation and session sign-out. Analyst reads overview and analytics without changing settings or opening private feedback.
Beta Tester, Creator, VIP and Member have standard Studio access. These community roles do not unlock admin tools, subscriptions or unreleased features. Role assignments do not invite people to the hosted site or change its sharing policy.
Only the configured site owner can assign roles or view complete member profiles and private images. Every admin request checks the current role; an already-open staff page cannot retain permissions after they are removed.
As the owner, open Studio Admin → Members and find the member by name or member ID. The self-hosted directory includes registered accounts, including those that have not yet entered Studio. Sites also includes recorded Studio visitors and saved profiles.
Click the member’s current role in the Role column. Review the selected role’s permissions, then save the assignment. Each person has one role.
Choose Member to remove staff permissions. The Owner role is locked and cannot be assigned or changed here.
Review the role history for earlier assignments. If another tab changed the role, reload its current assignment before saving again.
| Role | Access |
|---|---|
| Owner | Configured site owner. Full administration, private member profiles and role assignments. |
| Administrator | Manage operations, beta admissions, content and ordinary member security and recovery. Only the owner can manage staff accounts, private profiles and role assignments. |
| Editor | Publish landing page content, both roadmaps and What’s New posts. |
| Moderator | Review feedback, publish service reports, manage badges, and suspend, reactivate or sign out ordinary members. Cannot send recovery emails or manage staff accounts. |
| Analyst | Read the overview and aggregate analytics without changing settings or tracking. |
| Beta tester | A community title with standard Studio access. It does not unlock features or administrative access. |
| Creator | A community title with standard Studio access. It does not unlock features or administrative access. |
| VIP | A community title with standard Studio access. It does not include paid benefits or administrative access. |
| Member | Standard Studio access, with no administrative permissions. |
Overview shows current work queues available to your role: beta requests, open feedback, owner-only account-data requests and suspended self-hosted accounts. Queue cards open the relevant workspace. Open feedback excludes reports marked Fixed or Verified. These counts describe saved records, not automatic error monitoring.
Publishing staff see journal drafts and pending edits, plus active roadmap work. Shortcuts only lead to permitted workspaces. Refresh counts and Refresh queues reload their respective data. Optional usage reports remain in the collapsible Usage snapshot, separate from operational queues.
Customize overview retains the saved layout controls for optional shortcuts and reports. Review changes before publishing them. Changes to the overview layout do not publish a journal post or change member access.
Owners and Administrators can open System readiness to see this instance’s runtime, Studio version and diagnostic build. Read-only checks test database reads and object-storage metadata access. SMTP and social-login indicators describe configuration; they do not verify delivery or provider connectivity. Backups require a separate operator review and restore drill.
Admin activity is available to Owners, Administrators and Moderators. Filter by the available event categories, search by record ID, actor ID or action, and page through saved revisions. The server limits categories and settings scopes to the current role. Private notes, report contents, recipient emails and invitation secrets are excluded. Staff-role and global-access-policy history remain owner-only.
This is operational revision history, not a complete log of logins, page views, email delivery or hosting changes. Older site-setting revisions do not identify their actor. Detailed action reasons remain in the corresponding permitted record history.
Members opens the Member directory. Enter a name or member ID and choose Search, combine Role and Activity filters, and use the applied-filter chips or Clear all to remove them. The result summary and Previous/Next controls describe the current page. Refresh reloads the directory. Open Roles & access to compare or search staff and community role descriptions before assigning a role. Only the owner can make assignments.
For the owner, the directory uses each member’s saved avatar or profile photo, with initials when no appearance has been saved. Delegated staff receive a basic directory without private photos, profile details or printer lists. Select the name, avatar, Profile button, or View profile in the row menu to open the owner-only member profile. Its Profile, Workshop, Badges and Directory record links lead to the saved identity, printer list, awards and recorded activity. Copy member ID helps with support; Member directory returns to Members. Refresh the directory after a member saves an updated account profile.
The directory includes all registered self-hosted accounts as well as observed Studio members and saved server profiles. Account-access filters distinguish active, suspended and unverified native accounts from hosted identities. The No visits activity filter finds registered accounts that have not yet been observed in Studio. The Owner label comes from a verified owner session; other labels reflect the saved role assignment. Active indicates a visit in the last 30 days. Joined Studio is the earliest recorded Studio visit or saved server profile creation date. Dates are shown in UTC. Use the row menu to edit a custom member ID or clear it to restore the stable Studio-assigned ID.
Badge manager’s Catalog shows total, visible and new or edited draft badge counts. Search badges, filter by visibility, pick from Workshop, Milestones, Community and Special designs, preview edits, and publish changes. In Member awards, choose a member and search their badge choices; grant an available badge or confirm removal of an existing award. The Members row menu opens the same awards view. Hidden badges retain existing awards. Members see their own awards in View profile. Badge grants are manual.
Management roadmap opens the Planning board. Its summary separates all planning items, items visible after publishing, and new or edited drafts. Switch between Board and List, combine search with category and stage filters, or choose Clear filters. Planned, In progress, and Shipped organize current work; Archived reveals older items.
Assign a Category such as Landing page, Discord, or Nexlock Suite for Designer. Category labels and card accents use matching colors in Admin and on the website Roadmap. Open an item’s menu to move it between stages or archive it. Archived items can be moved back to the board.
Save item edits as drafts, then Review changes and Publish changes to save the roadmap or Discard draft changes to restore its saved state. New items are marked for the website Roadmap by default. Edit Show on the website Roadmap to keep an item internal or share it. The website shows only published, non-archived items marked for sharing. Changing the admin layout or filters does not publish an item.
What’s New posts separates total posts, published stories, unpublished drafts and live posts with draft edits. Combine All posts, Drafts, Published or Needs review with text search, Product and Category filters. Sort by Recently edited, Oldest edited or Title A–Z; browse the result pages or Clear filters. Choose New post or Edit post to work on a story.
In Write, enter the title, summary and article text; start section headings with ## and add one release-note item per line under Added, Changed or Fixed. Post settings holds the product, category, optional version and post address. The address stays fixed after the first save.
Use Choose an image or Replace image for an optional cover and fill in Image description. Remove cover clears it from the draft. Preview shows the draft story and release notes; Back to writing returns to the fields. Before you publish lists the title/address, summary, article or release notes, and cover-description checks.
Save draft keeps the work private or preserves the current live revision. Publish post makes a new post visible in What’s New, the homepage highlight when enabled, and the feed; Publish changes replaces an existing live revision. Unpublish removes the live post while keeping its draft. Website builds do not publish new journal announcements automatically.
Unsaved changes are marked in the editor. All posts offers Keep editing or Discard and leave when edits have not been saved; reloading or closing the browser page can also show its unsaved-change prompt. Save draft before leaving to retain the changes.
Status page separates Services, Incidents, and Page & resources. Its draft summary counts configured services, services reported operational, and open incidents. In Services, edit availability and details; remove a service from affected incident lists before deleting it. At least one service remains configured.
In Incidents, search the title or update text and filter All, Open or Resolved incidents. Expand a report to edit its stage, explanation and affected services. New incidents open for editing; update times are labeled UTC. Changes remain a draft until Publish changes.
Page & resources holds the page title, introduction, support link, published JSON feed and standalone MIT-licensed status starter. Services start as Not reported. These are manual administrator reports, not automatic uptime checks.
Roadmap and badge editors keep draft actions at the bottom of the dialog. Review an item’s stage and visibility, or check a badge’s profile preview, before saving its draft. Homepage and Suite settings show a draft preview alongside the fields. The save bar marks unpublished changes and stays available while you scroll. Click a switch label or use Tab and Space to change it. Disabled controls cannot be changed while publication is in progress.
Choose Review changes to validate the settings and compare the saved values with your draft. Correct any displayed field errors, review the differences, then choose Publish changes to make them live. The review step does not publish anything. Use defaults stages the original settings for this same review.
Unpublished settings exist only in the open page. Leaving an admin workspace with edits asks you to keep editing or discard them; closing or reloading the browser page can show its unsaved-change prompt. Publish the work you want to retain before leaving. This protection is not autosave or recovery after a browser crash.
Where your role can read settings but cannot publish them, Preview only identifies the form. You can explore its draft controls without a publishing action; those preview edits are not saved. Workspace links and editing tabs do not add permissions. If another session published a newer settings revision, keep a copy of any draft details you need, reload saved settings, and review the latest values before trying again.
Settings history covers admin control publications; it is not the journal’s draft history, a website-code rollback, or a backup of member profiles and private projects.
An older badge catalog cannot replace a catalog that contains newer badge identities. Hide a badge in the current catalog when you want to remove it from profiles while preserving its definition and awards.
Open Publication history and select a settings area or browse the saved revisions. Choose Review for a revision; Published changes compares it with its predecessor.
If your role can publish that area, choose Review restore. Compare Live value with Restored value to see what the selected revision would change now. Refresh preview reads the latest live settings.
Save or discard unpublished edits in that area before restoring. Check the preview and explicitly choose Publish restored settings when it is correct.
The restore creates a new revision. Earlier history remains available, and a newer concurrent publication prevents an outdated restore from overwriting it.
Open Beta feedback to review private reports from signed-in members. The owner, Administrators and Moderators can use this workspace. Filter the inbox, open a report, and review the original details and follow-up history before changing its status or priority.
Write the message intended for the reporter in the shared reply field; use the internal note field for staff-only context. Saving records a new revision. If the report changed in another session, reload it and review the newer information before retrying.
Feedback status is a support workflow and does not publish an announcement, grant access, or certify a physical print. The feedback guide explains the reporter’s side of the conversation.
Landing page settings separates Hero & notice, Navigation, Sections, Footer, Questions and Search metadata. Work on one section at a time, then publish the combined settings. Hero & notice and Sections show a draft homepage preview. Questions replaces the original homepage FAQ only after custom questions are published; an empty list keeps the original questions. Search metadata provides an illustrative title and description preview, not a guarantee of search-engine appearance.
Navigation covers the hero eyebrow, main and secondary destinations, header button label and website navigation. Footer controls the closing invitation, footer tagline and Status link. Link fields accept site paths, anchors, or complete HTTPS URLs. Hiding a navigation link does not disable its page.
Suite settings controls the default opening tool, workspace notice, MOC preview, and experimental Interlock lab entry points, with a draft workspace preview. Direct tool links and saved draft resumes keep their intended destinations. Publish changes applies the current settings when visitors next open or reload the page. Use defaults stages the original settings for review; Discard draft changes restores the saved copy. What’s New posts retain their own publishing workflow.
In Analytics, open Audience and choose 7, 30, or 90 days in UTC. The date summary identifies the selected period. New Studio members counts first visits recorded in the member directory; account registration totals are unavailable. Active users counts unique signed-in visitors who opened the homepage or Designer. Active Designers counts the subset who opened Designer. Returning users counts active visitors first seen before the selected period.
Audience over time lets you select a legend button to show or hide a series, keeping at least one series visible. Missing active-user coverage remains blank rather than connecting across unavailable dates. Use Show daily counts or Download daily CSV for day-by-day comparisons. The same person can appear on multiple days, and each period total counts them once.
About these counts identifies the first tracked day and whether tracking is paused. Dates before coverage have unavailable active counts, shown as — in the table. Subscriptions is separate from measured audience activity and remains Not connected until a billing provider is available. Refresh updates the selected report; Try again retries a failed request.
Usage events shows counts for homepage views, main button and 3D preview clicks, Designer visits, tool opens, completed imports, saved part writes, and browser exports started in Designer. Event totals can include repeat actions. Open Tracking settings to pause or resume both activity and event collection. The member directory continues to record first visits.