Skip to main content
Erstan puts AI agents to work on your NetSuite finance operations — drafting, analyzing, and acting on your data, with you in control of every change. This page explains the handful of building blocks that make that work, and how they fit together. Read it once and the rest of the docs will click into place. Each primitive links to its own deep-dive page.

​
The building blocks

Workspace

A company account bound to one NetSuite environment (production or sandbox). You can belong to several workspaces and switch between them. Everything else lives inside a workspace.

Team

A focused container inside a workspace — Finance, Sales Ops, or the workspace-wide Company team — holding its own tasks, content, agents, and members.

Agent

An AI worker that does a job for you. Built from a trigger, steps, instructions, skills, and connector tools. Three shapes: Assistant, Workforce, and Automation.

App

An interactive dashboard or tool with its own screens, data, and configured actions. Build a draft, review it, and publish it for users.

Data Source

A reusable read for Apps and Agents, with declared inputs, output columns, and a separate draft and published definition.

Sheets and Databases

Native workbooks and structured records in Content. Use Sheets for calculations and Databases for tables, relationships, and views.

Skill

A reusable package of instructions (a SKILL.md plus optional files and actions) an agent loads to do a task the same expert way every time. Published skills also show as Agent ready.

Task

Assigned work you can track, including Agent runs linked to Tasks. Tasks can move from Queued to In Progress, then Needs Review or Complete, depending on the completion policy.

Connector

A connection to an external system — NetSuite (flagship), LLM providers, Slack, MCP servers, and built-in Erstan tools — that gives agents the access and tools they need.

Knowledge

Retrieval sources agents can pull from: searchable Team Files (Agent knowledge) and Erstan-managed NetSuite product updates.

Approval (HITL)

A pause to review an action before it runs. Write-capable tools require approval by default, subject to configured policies and auto-approval settings.

​
The three agent shapes

An Agent is the AI worker you chat with, build, and run. Every agent comes in one of three shapes, depending on the job.
The product calls all three Agents. Under the hood, Assistants and Workforces are chat-first agents and Automations run as a fixed sequence — but you rarely need to think about that distinction. See Agents overview for the full picture.

​
How they fit together

The pieces stack up in a simple chain. A connector grants access, an agent does the work using skills and tools, Apps and artifacts present the results, Tasks track assigned work, and approval policies govern changes.
1

A connector gives access

Your workspace owner connects NetSuite once, and each member authorizes their own NetSuite user. An available AI model, through Erstan Managed access or a permitted customer key, powers chat and Agents.
2

An agent does the work

You chat with an agent or run one. It uses its skills for know-how and connector tools to read NetSuite data — for example, finding overdue invoices or summarizing AR aging. It can also pull from Knowledge when it needs your files or NetSuite product updates.
3

Work shows up as tasks

Assigned and scheduled work has a Task you can follow in a list or board. Chat conversations and Agent run history remain available separately; follow a linked Task when one is created.
4

Review actions and results

When an action requires approval, review the change and decide whether it runs. Tool policies and auto-approval settings determine which actions pause.

​
NetSuite, safely

Because NetSuite is the system of record, Erstan treats every write with care.
Agents act in NetSuite as you, using your own NetSuite role and permissions (per-user authorization). Each tool has a write policy — Allow, Require approval, or Deny — and write-capable actions require approval by default. Auto-approve writes can skip the prompt; turn it on only when you fully trust the agent and the action. See Security & write safety.
A workspace binds to one NetSuite environment. Production and sandbox each get their own workspace, so test work never touches live data. When NetSuite is under load, a brief “NetSuite is busy” queue can hold work and resumes automatically — no action needed.

​
Where each piece lives

Switch workspaces from the workspace switcher. Inside a workspace, Teams organize people, agents, content, and tasks. The Company team is workspace-wide; you can also create focused teams like Finance or AP. Roles are Owner / Admin / Member.
Build and run agents from the Agents library. Reusable instruction packages live under Skills. Ready-made agents, skills, and bundles come from the Solution Library.
Find Apps in Artifacts, create them from Content or Library templates, and use their Data section to configure reads, resources, and actions. Manage reusable Data Sources from the profile menu. Sheets and Databases live in Content.
Track agent work in Tasks; review outputs in the Needs Review and Approvals queues. Write actions surface as approval cards in chat and on runs.
Manage external systems under Connectors. Files and documents live in a team’s Content; make a file searchable to turn it into Agent knowledge.

​
Next steps

Quickstart

Connect NetSuite and run your first agent.

A tour of Erstan

Find your way around the sidebar and Home.

Agents overview

Go deeper on the three agent shapes.