> ## Documentation Index
> Fetch the complete documentation index at: https://docs.truagents.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Organizations and workspaces

> Understand the account-level container that holds your team, settings, data, and operating context in TruAgents.

## Summary

In TruAgents, **organization** should be treated as the main product term.

It is the account-level container that ties together:

* teammates
* communication settings
* integrations
* campaigns
* contacts and data sources
* operating history and reporting

## Who this is for

* New customers setting up their account
* Admins managing team and infrastructure settings
* Anyone trying to understand what data belongs together in the product

## Why the wording matters

Some products use the word **workspace** as the main container term. For TruAgents, the stronger product language is **organization**.

Simple version:

* prefer **organization** in user-facing docs
* only mention **workspace** when comparing ideas or helping someone translate from another product

## What belongs to an organization

* organization identity and configuration
* team membership
* channel setup such as email and SMS configuration
* campaigns, contacts, segments, tags, and file sets
* history, analytics, and reporting tied to that operating environment

## Why this boundary matters

The organization boundary explains:

* which teammates work together
* which settings affect everyone
* which contacts, campaigns, and communications belong together
* where reporting and history should be interpreted

Simple version: if you are asking "what is the shared operating container?", the answer is the organization.

## What an organization is not

It is not only:

* a billing record
* a sign-up form result
* a loose team list
* a label wrapped around otherwise unrelated data

The organization is the shared operating context for the product.

## Early setup implications

Because the organization sits above most other workflows, early setup decisions here have downstream effects on:

* teammate access
* email and SMS readiness
* default behavior such as timezone or approval settings
* how campaigns and communications are interpreted later

## When "workspace" is still useful wording

`Workspace` can still help when explaining the concept to someone coming from another product, but it should usually be a translation aid rather than the main term.

For example:

* "Your organization is the main shared workspace in TruAgents."

That phrasing teaches the idea without weakening the core product language.

## Common misunderstandings to avoid

* An organization is not just billing metadata.
* It is not only a team list.
* It is the boundary around most of the operating data users care about day to day.
* A problem that affects the whole organization usually should not be debugged as a single-user profile issue.

## Related operational questions

When a team is confused, the organization concept usually helps answer:

* who should have access
* which settings apply by default
* whether a workflow belongs to this account context
* whether a configuration change will affect the broader team

## Related pages

* [Onboard your organization](/getting-started/onboarding-your-organization)
* [Organization settings](/admin/organization-settings)
* [Team management](/admin/team-management)
* [Roles and permissions](/concepts/roles-and-permissions)