Settings
The Settings page is available to NetSuite Administrators. Use it to manage global NimbusDash defaults and configure AI assistant behavior for your account.
Open Settings
Section titled “Open Settings”In NimbusDash, click Settings in the left navigation.
Only users with the NetSuite Administrator role can access this page.
Global Settings
Section titled “Global Settings”Global settings apply across NimbusDash unless a specific dashboard saves its own setting.
Default Theme
Section titled “Default Theme”Choose the default visual theme used by NimbusDash dashboards.
Available themes include:
- Quartz Dark
- Quartz Light
- Balham Dark
- Balham
- Alpine Dark
- Alpine
- Material
- Classic
Individual dashboards can still save their own dashboard-level theme. When a dashboard has its own saved theme, that dashboard setting takes precedence over the global default.
AI Configuration
Section titled “AI Configuration”AI Configuration controls whether Dash AI is enabled, which provider it uses, how much dashboard context it can send, and which roles can use it.
When enabled, Dash AI supports Dashboard Actions for grid changes and AI-generated charts. Product Support is shown in the UI but is not connected yet.
For end-user workflows, see:
Provider
Section titled “Provider”Assistant
Section titled “Assistant”Enable or disable Dash AI.
When disabled, users cannot open Dash AI or send requests even if provider credentials are configured. The Dash AI navigation item is hidden on the dashboard.
Provider
Section titled “Provider”Choose the AI provider Dash AI should use for Dashboard Actions.
- OpenAI uses your OpenAI API key stored as a NetSuite API Secret.
- Anthropic uses your Anthropic API key stored as a NetSuite API Secret.
- NimbusDash AI is listed as coming soon. This future option will use NimbusLabs-managed AI functionality with usage-based billing.
Dash AI behaves the same in the dashboard regardless of provider. Provider selection affects only the backend model call.
OpenAI API Secret ID
Section titled “OpenAI API Secret ID”Choose the NetSuite API Secret that contains your OpenAI API key.
Create and manage secrets under Setup > Company > Preferences > API Secrets. See NetSuite’s Creating Secrets guide for step-by-step instructions.
The dropdown shows available API Secrets. Select the secret for the OpenAI provider, such as a secret with an ID similar to custsecret_openai_api_key.
NimbusDash uses the NetSuite secret at runtime so the raw key does not need to be stored in NimbusDash settings.
Anthropic API Secret ID
Section titled “Anthropic API Secret ID”Choose the NetSuite API Secret that contains your Anthropic API key.
Use the same NetSuite API Secrets workflow as for OpenAI. See Creating Secrets in the NetSuite Help Center.
The dropdown shows available API Secrets. Select the secret for the Anthropic provider, such as a secret with an ID similar to custsecret_anthropic_api_key.
Model Behavior
Section titled “Model Behavior”Response Style
Section titled “Response Style”Choose how the assistant balances speed and depth.
- Fast uses a smaller response budget and lighter reasoning for quicker replies.
- Thorough allows longer, more deliberate responses for complex dashboard or chart requests.
- Custom lets administrators specify the model, token limit, and reasoning effort directly.
The model name sent to the selected provider when Response Style is set to Custom.
Examples may include provider-specific model names such as OpenAI or Anthropic models. Use a model supported by your selected provider and account.
Max Response Tokens
Section titled “Max Response Tokens”The maximum number of tokens the assistant may generate in a response.
Lower values generally produce faster, shorter responses. Higher values allow longer explanations or more detailed structured responses.
Reasoning Effort
Section titled “Reasoning Effort”Controls how much reasoning the model should use before responding, when the selected model supports this option.
Available values are:
- Default lets the model decide.
- Low favors speed.
- Medium balances speed and deeper reasoning.
- High favors more deliberate responses for complex tasks.
Some providers or models may ignore this setting.
Data Shared With AI
Section titled “Data Shared With AI”Data Context
Section titled “Data Context”Controls what dashboard data may be included in Dash AI Dashboard Actions requests.
- Schema and grid state only sends information about columns, filters, sorting, grouping, and dashboard state without row values.
- Include capped sample rows may include a limited sample of row data.
- Include capped filtered/sorted rows may include a limited set of rows based on the current filtered or sorted grid state.
Users see a short context label below the Dash AI message box that reflects this setting.
Use the most restrictive option that still supports your intended AI workflows. For sensitive data, prefer Schema and grid state only.
Row Cap
Section titled “Row Cap”Limits how many rows can be included when a data context option allows row values.
This cap helps control data exposure, request size, and provider usage.
Chart Context
Section titled “Chart Context”Chart Context
Section titled “Chart Context”Controls what chart-related context may be included in Dash AI chart requests.
- Column metadata only sends column information without calculated statistics.
- Column metadata plus deterministic stats can include summary statistics to help Dash AI recommend useful chart configurations without sending the full dataset.
Stats Row Cap
Section titled “Stats Row Cap”Limits how many rows may be used when calculating chart statistics for AI context.
Top Values
Section titled “Top Values”Limits the number of most common values included in chart context summaries.
This can help the assistant understand common categories while keeping context compact.
Default Apply Mode
Section titled “Default Apply Mode”Controls how Dash AI-proposed grid and chart changes are handled by default in Dashboard Actions.
- Preview/Explain shows the proposed change for review before applying it.
- Auto Apply can apply supported changes automatically when column mappings are resolved.
Users can still review previews before applying when Preview/Explain is selected. Auto apply skips the manual Apply click only for supported changes that do not require unresolved column confirmation.
For most accounts, Preview/Explain is the safer default because users can review assistant suggestions before they affect the dashboard or create charts.
Access
Section titled “Access”Assistant Access
Section titled “Assistant Access”Controls which NetSuite roles may use Dash AI.
- Enable Allow all roles to allow all roles to use Dash AI when it is enabled.
- Leave Allow all roles disabled and select specific roles to restrict assistant usage.
Users without access do not see the Dash AI navigation item. Administrators can always configure Settings. Role access controls Dash AI use for other roles.
Security Notes
Section titled “Security Notes”- Store API keys in NetSuite API Secrets. Do not enter raw API keys in NimbusDash settings. See Creating Secrets for how to create and restrict secrets in NetSuite.
- Restrict API secret access in NetSuite to the roles and integrations that need them.
- Review your data policy before enabling row-level context. Row caps limit exposure but do not remove the need for policy review.
- Prefer Preview/Explain for default apply mode unless users are comfortable with automatic grid and chart changes.
- Confirm that your selected AI provider, data policy, and role access settings meet your organization’s data handling requirements before enabling Dash AI.
- Remind users that AI responses should be reviewed before applying changes to production dashboards.