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

# Organization Settings

> Group projects and members under one organization with a shared credit pool. Fund the pool, allocate a budget per project, and manage member roles.

An organization groups your projects and teammates under one shared credit pool. Instead of every project owner buying their own credits, the organization owner funds a pool once and allocates a budget to each project. When a project's budget runs out, its paid actions pause. Nobody's personal credits are touched.

**What this page enables:** agencies and larger teams get one place to pay, one place to distribute credits, and a hard budget per client or department.

**Where to find it:** go to **Settings** > **Organization** in the Personal group.

<Info>
  Organizations are optional. If you run one project with one card, [Billing](/en/settings/billing) is all you need. Create an organization when several projects should draw from the same credits.
</Info>

## Create an organization

<Steps>
  <Step title="Open Organization settings">
    Go to **Settings** > **Organization**. If you have none yet, the page shows **Create organization**.
  </Step>

  <Step title="Name it">
    Click **New organization**, enter a name such as your company or agency name, and click **Create**. You become its owner.
  </Step>
</Steps>

If you belong to more than one organization, switch between them with the **Organization** selector at the top of the page. Rename one at any time under **Rename organization**.

## Fund the credit pool

The overview shows the pool as **Total**, **Allocated** and **Available**. To add credits, enter an amount under **Move credits to pool** and click **Fund pool**.

Credits move from your personal account into the organization. They are not duplicated, so the same credit can never be spent twice. Only the organization owner can fund the pool.

## Invite members

Under **Members**, enter a teammate's **Email address**, choose a **Role** and click **Add member**. Three roles exist:

| Role       | What they can do                                                                            |
| ---------- | ------------------------------------------------------------------------------------------- |
| **Owner**  | Everything, including funding the pool and deleting the organization. One per organization. |
| **Admin**  | Manage members and projects, attach their own projects, and allocate budgets.               |
| **Member** | Belong to the organization and work in its projects according to their project role.        |

**Remove member** takes someone out of the organization. They keep their WISEPIM account and lose only organization access.

## Attach projects and allocate budgets

The **Projects & budgets** table lists every attached project with its **Allocated**, **Used** and **Remaining** credits.

<Steps>
  <Step title="Add the project owner as an admin">
    A project can only be attached by its own owner. Invite that person to the organization with the **Admin** role.
  </Step>

  <Step title="Attach the project">
    The project owner opens Organization settings, picks the project under **Attach a project** and clicks **Attach**. Ownership of the project does not change, and the owner keeps all existing access.
  </Step>

  <Step title="Allocate a budget">
    The organization owner enters a number of credits in the **Add budget** column and clicks **Allocate**. The hint under the table shows how many credits are still unallocated in the pool.
  </Step>
</Steps>

<Warning>
  When a project budget reaches zero, paid actions in that project pause until you allocate more. The project owner's personal credits are never used as a fallback.
</Warning>

Projects that were attached before this rule existed can still charge their owner's personal credits when the organization budget is empty. Such a project shows a **Protect owner** button. Click it to stop that fallback.

**Detach project** removes a project from the organization. The project itself is not deleted.

## Delete an organization

The **Danger zone** at the bottom holds **Delete organization**. Deleting removes its members and project links permanently and cannot be undone. Detach projects you want to keep first, and allocate or spend the remaining pool.

## Act on what you find

<AccordionGroup>
  <Accordion title="A client project ran out of budget mid-run">
    Allocate more credits under **Projects & budgets**. Paused work resumes from where it stopped; check [Process Tracker](/en/other-features/process-tracker) for tasks waiting on credits.
  </Accordion>

  <Accordion title="You want to see which project spends the most">
    Open [Usage](/en/settings/usage) and group by **Project** or **Organization**. The **Used** column here shows the lifetime total per project; Usage shows it over time.
  </Accordion>

  <Accordion title="A project owner is not in the organization yet">
    You cannot attach their project for them. Add them as an **Admin**, ask them to attach the project, then allocate a budget. This keeps project ownership where it is.
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="Usage Settings" icon="chart-bar" href="/en/settings/usage">
    See how credits are spent per project, member and action.
  </Card>

  <Card title="Billing Settings" icon="credit-card" href="/en/settings/billing">
    Buy the credits that fund the organization pool.
  </Card>

  <Card title="Agencies" icon="briefcase" href="/en/essentials/agencies">
    Run multiple client catalogs from one account.
  </Card>

  <Card title="Team Management" icon="users" href="/en/teams/team-management">
    Set project-level roles for the people you invite.
  </Card>
</CardGroup>