NetSuite Administrator key terms

A named bundle of permissions and preferences assigned to a user account that determines which records, pages, and actions the user can access. A user can hold multiple roles and switch between them.

A granular right granting a role the ability to view, create, edit, or delete a specific record type or perform a specific action. Permissions carry levels such as None, View, Create, Edit, and Full.

The security model where access is granted through roles rather than to individual users directly. Administrators change a role once and every user holding it inherits the updated access.

A tab-based workspace in the NetSuite interface grouping related menus and pages, such as Accounting, Sales, or Support. A role's assigned centers determine which tabs a user sees after login.

A legal or reporting entity within a NetSuite OneWorld account. Transactions, records, and roles can be restricted to subsidiaries so users only see data for the entities they are responsible for.

A separate copy of a production NetSuite account used to test configuration, customizations, and integrations safely. Refreshing a sandbox overwrites it with current production data and setup.

An early-access environment that lets administrators test upcoming NetSuite version changes before they reach production. It mirrors production data and is used to catch breakage in customizations and workflows.

A login control requiring a second verification factor beyond a password, such as a one-time code. Administrators can enforce it by role and manage device resets for locked-out users.

An authentication setup where users log in once through an external identity provider and are passed into NetSuite. It is configured per account and can be required or optional for roles.

A user-defined record structure created to store data that standard NetSuite records do not cover. Administrators define its fields, permissions, naming, and whether it appears in menus or search.

A field added to a standard or custom record to capture additional information. Its type, sourcing, display, and role restrictions are configured by an administrator without code.

A configurable classification dimension, such as a custom department or project code, that can be added to transactions and records. It enables filtering and reporting on company-specific categories.

NetSuite's JavaScript-based programming model for extending and automating the platform. Scripts respond to record events, scheduled jobs, user interface actions, and inbound or outbound data flows.

A SuiteScript type that runs in the user's browser to react to page events such as field changes and saves. It validates entries and adjusts the form before data reaches the server.

A server-side SuiteScript type triggered before or after a record is loaded, created, edited, or deleted. It enforces business logic that must run regardless of how the record is changed.

A server-side SuiteScript entry point that renders a custom page or handles a request from a user or external system. It is commonly used for custom forms and integration endpoints.

A SuiteScript type exposing a custom endpoint that external systems call over HTTP to read or write NetSuite data. Authentication and payload handling are defined by the script author.

A no-code automation built in SuiteFlow that triggers on record events and executes states, actions, and conditions. It can send emails, set fields, create records, and enforce approvals.

A stage within a SuiteFlow workflow that defines the conditions for entering it and the actions taken while a record sits there. Transitions move a record between states.

A reusable query that filters records, chooses displayed columns, and can drive lists, reminders, or reports. Administrators set its audience and role restrictions to control who can run it.

A formatted output built on NetSuite data, ranging from standard financial statements to custom reports assembled from searches. Reports can be scheduled for delivery and restricted by role.

A configurable panel on a role's home dashboard that surfaces searches, reports, reminders, key performance indicators, or custom content. Portlets are assigned per role and per center.

A connection that moves data between NetSuite and another system, typically through web services, RESTlets, or file exchange. Administrators monitor its logs, tokens, and error handling.

A credential model where an integration uses a token and secret tied to a role instead of a user password. It supports machine-to-machine access without storing user credentials.

A data-loading tool that maps a comma-separated file's columns to NetSuite fields to create or update records in bulk. Administrators preview results and review error logs before committing.

The process of loading legacy or external data into NetSuite using imports, templates, or integration tools. It typically involves field mapping, validation, and reconciliation against source totals.

A setting that flags records, such as customers or vendors, whose names or identifiers match existing ones during entry or import. It helps keep master data clean.

Any administrator-made change to NetSuite's standard behavior, including custom fields, forms, records, and scripts. Customizations must be tracked and re-tested across releases.

An alternative layout of fields, subtabs, and actions for a standard or custom record. Administrators assign forms to roles so different teams see only the fields relevant to them.

A system log recording changes to records, including who made the change and when. Administrators use it to investigate data issues, permission problems, and suspicious activity.

A record of user login attempts and outcomes, including failures, role selections, and IP addresses. It supports security investigations and troubleshooting of access complaints.

The record representing a person in the system, linked to a user account and its assigned roles. Deactivating or editing it affects login access and record ownership.

A SuiteScript deployment that runs automatically on a defined schedule without user interaction. It is used for recurring data cleanup, batch processing, and synchronization tasks.

The NetSuite workflow engine used to build no-code automations with states, transitions, and actions. It is preferred over scripting when business logic is simple and maintainable by administrators.

A per-role setting controlling defaults such as landing center, time zone, date format, and email options. Preferences let one user experience different behavior depending on the active role.

Account-wide settings that shape the platform, including features enabled, company information, and defaults. Enabling a feature can add records, permissions, and menus across the account.

The act of turning on optional NetSuite capabilities in account setup. Some features are irreversible once enabled and can change available roles, records, and workflows.