Skip to main content
A team groups people, agents, content, and tasks for a focused area of your business, such as Finance or AP. Owners and admins manage who belongs to it, the defaults its agents follow, and the documents and files agents can read.
Team Settings showing General, Task defaults (Human confirms / Agent can complete), and other sections

Team Settings

Most actions on this page are limited to Owners and Admins of the team (or workspace admins). Members can use the team but not change its membership or settings.

Members and roles

Each team member has a role that sets what they can do inside the team.

Add a member

You add people who are already in your workspace. To bring a new person into the workspace first, see Workspaces and people.
1

Open the team's Members surface

From the team header, open Members (or go to Settings → Access → Manage members).
2

Add a member

Click Add member, pick an existing Workspace member, and choose a Role (Owner / Admin / Member).
3

Adjust later

Change a member’s role inline, or remove them from the team.
Personal teams and the Company team don’t add members here — everyone in the workspace is already in the Company team, and personal teams belong to one person. Manage workspace-wide membership from Workspaces and people.
Assigning the Owner role prompts an ownership-transfer confirmation. Removing a member runs a lifecycle impact check for their assigned work, owned content, and run-as automations, and lets you reassign that work to a replacement before they leave. Review it before confirming.

Team settings

Open Settings from the team header to manage how the team behaves.
Edit the team’s icon, name, identifier, and description, then Save. The identifier (Team ID) appears in metadata.
Set the completion policy that new tasks in this team inherit:
  • Human confirms — agents send finished work to Needs Review instead of marking it done. A person approves before the task moves to Complete.
  • Agent can complete — agents may mark their own work done.
This default applies to new tasks only; existing tasks keep their current setting. See Reviewing and approving agent work for how Needs Review works.
Review the team’s access scope and Manage members (see Members and roles above).
Manage the labels used to tag this team’s tasks, plus shared workspace labels, in the label manager. Labels are color-coded and filterable on the Tasks views.
See how much the team is using: number of documents, files, and storage used.
Archive or Delete the team. Both run an impact check first.
Archiving or deleting a team affects its tasks, content, and any agents scoped to it. These actions are disabled for managed teams (personal and Company). Read the impact check before you confirm.
Managed teams — your personal team and the workspace Company team — show read-only notices in places. They can’t be renamed, archived, deleted, or have members added through these screens.

Team defaults in practice

The Human confirms vs Agent can complete choice is the main lever for how cautious a team is. A Finance team that drafts collections emails or vendor-bill recommendations usually keeps Human confirms on, so every output lands in Needs Review before anyone acts on it. A reporting team that only runs read-only SuiteQL might allow agents to complete on their own.
Task defaults govern when a task is considered done. They’re separate from write approvals, which pause an agent before it writes to NetSuite regardless of the team default. See Approving and rejecting AI actions.

Team content

Each team has its own Content — the documents, files, folders, and knowledge its agents can read and write alongside you.
  • Browse and filter with the All / Documents / Files / Knowledge filter, and toggle List or Grid.
  • Create with New document, New folder, or Upload (drag-and-drop).
  • Organize by opening, pinning, or moving items into folders, and bulk download or delete.
The Knowledge filter shows only items that have been made searchable for agents. Turning a file into agent knowledge is what lets agents and automations pull it in as context.

Documents

Create rich documents agents can read and write.

Files

Upload, preview, and edit files in a team.

Agent knowledge

Make files searchable for agents and automations.

Next steps

Teams overview

What a team is and the team Overview dashboard.

Tasks overview

See and manage the work a team’s agents do.

Reviewing and approving work

How Needs Review and approvals fit together.

Workspaces and people

Invite and manage people across the workspace.