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

# Setup Templates

> Playbooks that take one kind of organization from an empty Orgo workspace to a working setup, in order

The rest of these docs are organised by feature: one page per thing Orgo does. That is the right shape once you know what you are looking for, and the wrong shape on day one, when the question is "which of these forty features do we actually need, and in what order?"

Setup templates answer that question. Each one takes a kind of organization, names the modules and settings it needs, puts them in the order you should configure them, and links to the feature page for each step.

**Built for** the first fortnight on Orgo, and for the moment a year later when you add a part of the product you skipped.

***

## Pick your starting point

<CardGroup cols={2}>
  <Card title="Fundraising" href="/docs/platform/templates/fundraising">
    One-off and recurring giving, campaign pages, donor recognition and receipts.
  </Card>

  <Card title="Member communication" href="/docs/platform/templates/communication">
    Newsletters, discussions, notifications and system email, and which channel to use when.
  </Card>

  <Card title="Federations" href="/docs/platform/templates/federations">
    Associations whose members are companies or institutions: company membership, seats and invoicing.
  </Card>

  <Card title="Scouting and youth organizations" href="/docs/platform/templates/scouting">
    Sections by age, youth members and parents, safeguarding, progression and camps.
  </Card>

  <Card title="Political parties" href="/docs/platform/templates/political-party">
    Formal membership applications, identity checks, territorial structure, internal elections.
  </Card>
</CardGroup>

Most organizations need more than one. A trade association that fundraises and sends a monthly bulletin is running three of these at once: read the one closest to your core operation first, then borrow from the others.

The split that matters most is who your members are. If they are **organizations**, start with [Federations](/docs/platform/templates/federations), because company membership changes how joining, seats and billing work. If they are **individuals**, start with whichever of the other four describes your main activity.

***

## What a template gives you

| Section             | What it answers                                                                                     |
| ------------------- | --------------------------------------------------------------------------------------------------- |
| **What to turn on** | The exact modules and settings, with the settings path and the permission needed to change each one |
| **Setup order**     | What to configure first, so you do not have to undo work later                                      |
| **What you get**    | The need you have, mapped to the Orgo feature that serves it                                        |
| **Recipes**         | Worked configurations you can copy, marked as examples rather than defaults                         |
| **Limits**          | What Orgo does not do for this use case, stated before you build on an assumption                   |
| **Troubleshooting** | The specific things that go wrong for this kind of organization                                     |

***

## If you are not sure which applies

Answer these in order. The first one that matches is your starting point.

| If this is true                                                                       | Start here                                                       |
| ------------------------------------------------------------------------------------- | ---------------------------------------------------------------- |
| Your members are companies or institutions rather than individuals                    | [Federations](/docs/platform/templates/federations)                   |
| Joining is a formal application you approve, and you hold members' identity documents | [Political parties](/docs/platform/templates/political-party)         |
| Money from supporters who are not members is your main flow                           | [Fundraising](/docs/platform/templates/fundraising)                   |
| Your members are under 18, or you run sections by age with adult volunteers           | [Scouting and youth organizations](/docs/platform/templates/scouting) |
| Your members are individuals paying a subscription and reading what you send them     | [Member communication](/docs/platform/templates/communication)        |

If none of them fit, the feature pages stand on their own. [Organization settings](/docs/platform/organisation/index) and [Modules](/docs/platform/organisation/modules) are the two worth reading first, because everything else is switched on from there.

***

## Before any template

Three things apply whatever you are building, and doing them first saves rework:

<Steps>
  <Step title="Fill in the organization profile">
    Legal name, registration and VAT numbers, address, currency, timezone and the legal document URLs. Invoices, emails and public pages all read from it. See [Organization info](/docs/platform/organisation/organisation-info).
  </Step>

  <Step title="Decide who administers what">
    Permissions are easier to hand out than to take back, and the difference between the Orgo administrator flag and the ADMIN\_TENANT permission catches people out. See [Permissions](/docs/platform/permissions).
  </Step>

  <Step title="Turn on only the modules you will use this month">
    Every module you enable adds menu entries and settings for your admins to wade through. You can switch the rest on later. See [Modules](/docs/platform/organisation/modules).
  </Step>
</Steps>

***

## Related

* [Modules](/docs/platform/organisation/modules): every switchable module and what enabling it turns on
* [Organization settings](/docs/platform/organisation/index): the map of the settings area
* [Permissions](/docs/platform/permissions): what each permission level unlocks
* [Texts](/docs/platform/customization/labels): renaming Orgo's vocabulary to match your own
* [Home](/docs/platform/index): the full feature index