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

# Understand Pods

A Pod is a shared workspace for one team, customer, or initiative. It brings conversations, tasks, and files together so that members can work from the same record.

## Before you begin

Decide who needs access and what the Pod is for. Use a Restricted Pod for customer, financial, or team-private work. Use an Open Pod only when every workspace member may browse and join it.

## Create and orient yourself in a Pod

1. In **Work**, open **Pods** and choose **Create Pod**.
2. Give the Pod a durable name that describes the shared outcome, such as `Customer accounts workspace`.
3. Choose the visibility and add the initial members.
4. Open the Pod and use **Conversations** for discussion, **Tasks** for owned work, and **Files** for shared material.
5. Open **Settings** to review the description, members, default agent, and pinned Frame.

Keep one customer or initiative Pod across reporting periods. Put the period on tasks, files, and records inside the Pod rather than creating a new Pod every month. Organise the Pod by members and business theme so the same people can follow the history.

Agents can work in the same Pod: they can post a conversation, create or update a task, and save a file when their permissions allow it. A Pod is therefore a collaboration boundary, not merely a folder.

Workspace administrators can apply policies that limit who may create Open Pods or whether members may add files manually. If a visibility option or **Add** action is unavailable, ask an administrator to check the workspace policy rather than changing the Pod's data scope.

## What you should see afterward

Members can find the same conversations, tasks, and files in the Pod. The Pod description gives an agent enough orientation to answer questions and route work. Keep sensitive material in the smallest appropriate Pod because membership determines the shared scope.

## Common questions

### Should I make one Pod for every process?

Usually group work by customer, initiative, or team outcome. Split a Pod when its members or data access must be different.

### Does a folder hide a file from another member?

No. Files in a Pod are shared with its members. Use Pod membership and separate Pods for access boundaries.

### Can a task be treated as an accounting posting or payment?

No. A task records collaboration work. A connected system remains the authority for a posted or paid record.