Inspect here. Author in the IDE.
Mirrors docs/customer/FAQ.md. Use the Feedback button for bugs and feature requests.
Yes during open beta. Sign in with Google, GitHub, or email, set a passcode, and use the Live desk — no card required. Demo is always free (fixtures only). Tips (Buy Me a Coffee / Instapay) never unlock features. Premium checkout (Paymob — USD or EGP) is Admin Preview only and does not gate the free desk. When billing goes live we will keep a free Live tier and announce changes — beta users are not cut off without notice.
You must be 13 or older. Live is for people authorized to work on the NetSuite accounts they connect. Creating an account or signing in accepts the Terms and Privacy Policy. Demo does not need an account.
Use the Feedback button (bottom-right on every page). Choose Bug report or Feature request. Stamp version and the page you were on are attached automatically. Super Admin reviews submissions in Admin → Feedback.
Use Help in the desk header (or press ?). Marked controls get a badge. Click one for a short explanation — the action does not run. Esc or Help again to exit. Getting started and FAQ stay for longer guides.
No. Write code in Cursor or VS Code. Optionally keep using SuiteForge for SDF scaffolding and IntelliSense. Aperture is the desk around that.
Yes. Optional Cursor MCP talks to the same desk verbs (logs, inventory, tickets, jobs, expiring keys — last4 only). Install steps are in Getting started under Aperture MCP (Cursor). That server never returns full secrets. It is not the Freshservice connector.
No. Production-only companies can execute a recorded plan and roll test records back. Scripts, fields, and lists stay.
By design. Rollback removes test instances (Sales Orders, Invoices, …) in dependency order. Customization objects stay.
Key cabinet: last4 + expiry in the UI. Full material stays encrypted server-side. Reminders at 60 / 30 / 14 / 7 days. NetSuite OAuth certs and other vendors (Infobip, ZATCA, …) both belong here.
No. Live OAuth encrypts the private key and client id at rest (AES-GCM) and refuses to store secrets if the encryption key is missing. After you save, the PEM is never returned to the browser or shown again — Desk and Keys show metadata only (name, last4, cert dates). Secrets never go to Notion, tickets, localStorage, or saved ODBC connections. Each Environment has its own credential slot. Demo never reads live keys.
Yes — optional one-way view. In Settings → Connections, open the Freshservice ticket channel, paste your domain, API key, and agent email (you). Aperture lists your unsolved tickets assigned to that agent beside native tickets. Nothing writes back to Freshservice. Native Aperture tickets are unchanged. Demo skips the connector.
No. Aperture is TypeScript — SuiteScript and desk tooling stay in JS/TS.
No. Demo never reads your Live portfolio or credentials. It is a separate world: fixture clients only, a DEMO banner, and namespaced device storage. Live is Log in / Sign up. Welcome is the door between them.
It does not anymore (2.3.0-beta). Settings is tabbed (Profile, Security, Connections, Workspace). Connections holds Linked accounts (GitHub this session; Notion and Slack Connect; Google / Microsoft / Discord wait until those providers exist) and ticket channels (Notion / Jira / ClickUp / Freshservice). An enrolled authenticator shows Linked on Security, not Enroll. Super Admin tools appear under Workspace only if you are a Super Admin.
After you sign in, the desk asks for your account passcode (set during onboarding). Unlock lasts for the hours you choose in Settings → Security (default 8). Enroll an authenticator (TOTP) for step-up: when you lock with it, after several wrong passcodes, or when this device’s authorize window expires. Recovery email sends a 15-minute link (and a backup code) so you can reset the passcode if you forget it.
Email sign-up sends a confirmation link from Supabase Auth. It expires in one hour. Open it — the confirmation tab verifies, then closes after a few seconds (or continue from that page). Google and GitHub sign-in skip this step. Recovery email uses the same confirmation page with a 15-minute link.
Inventory (2.4.1-beta) and Account desk show the total across SuiteScript versions. The script list includes internal id, active/inactive, owner, and how many deployments are live (isdeployed).
Schedules under Inspect. It lists running / in-queue / last-24h instances and named Scheduled + Map/Reduce deployments from SuiteQL. Refresh re-reads the active environment.
Yes (3.2.2-beta). On SuiteQL, use Save… or Save this run after a successful Cap/Pages run. Give it a name, optional short description, and optional ticket / script links. The Saved sidebar browses All / By Script / By Ticket. Live accounts need the 18_suiteql_saved_queries.sql migration applied once; Demo uses a seed library.
Defaults in the sidebar: transaction status codes, standard records, default things, and ODBC install. Saved ODBC connections and views stay on this device. The Connect password stays in the driver — never in Aperture.
buymeacoffee.com/wassemtakashi or Instapay appreciation (wassemtakashi@instapay) — it never gates features. That helps us continue the project and develop more easy-to-use paths for developers.