# Setting up an organisation

> A Teams licence attaches to an organisation, so create that first. Then buy or attach the licence, invite people, and add a team.

A Teams licence belongs to an **organisation**, not to the person who pays for
it, so the organisation comes first: create it, license it, invite people, add
a team.

An organisation whose licence is not active is read-only. It refuses
invitations, new teams, subdomain changes, settings edits and publishing,
and each refusal says why. It still lets you buy the licence.

> [!STEPS]
>
> === Create the organisation
>
> **Dashboard → Settings → Teams & orgs → New organization**. The **Create
> new** menu has the same entry. Give it a name and a slug. The slug becomes
> its URL, `blueprintr.io/orgs/<slug>`. Description and website are optional.
> Creating an organisation is free, and you become its owner.
>
> === Buy the licence
>
> Open the organisation, choose **Settings**, then **Billing**. On the
> **Teams plan** card set **Seats**, then choose **Subscribe** for the monthly
> or the yearly plan. Checkout takes a card and your acceptance of the terms.
> Only the organisation's owners and admins can do this, and the seat count
> cannot be lower than its current membership. You count as one.
>
> The same controls are on **Dashboard → Licensing & Billing** under **Your
> organisations**.
>
> === Confirm the licence landed
>
> Payment returns you to the Billing page. Within a few seconds the Teams plan
> card changes from **No active plan** to the number of seats you bought.
> Refresh if it has not. **Plan & seats** and **License**, in the same
> settings, show seat usage and the licence history.
>
> === Invite people
>
> **Settings → Manage members → Invite by email**. Each member takes a seat,
> and a pending invitation reserves one until it is accepted, revoked or
> expires. Seats are changed from Licensing & Billing, not from the members
> page.
>
> === Add a team
>
> **Settings → Teams → New team**. A team has its own members and its own
> content, and inherits the organisation's licence. Add one when a group needs
> its own content boundary. Projects belong in
> [portfolios](/foliums/blueprintr-user-guide/organise/portfolios-and-folders)
> instead.

> [!NOTE]
> If you signed up from the **Team** plan on the pricing page, Blueprintr
> remembers that for a week. Finishing your profile takes you straight to
> **New organization**, creating the organisation opens its **Billing** page,
> and until a plan is active the dashboard shows a strip with the next step:
> **Create organisation** while you own none, or **Subscribe** for the
> organisation you already own.
>
> If Blueprintr granted your licence by hand rather than through Checkout, the
> dashboard shows a **You're licensed for Teams** strip with a **Create
> organisation** link instead. Create the organisation, then send support its
> slug. Support attaches the licence.

## After the licence

> [!TILES 3]
>
> === [Members and invitations](/foliums/blueprintr-user-guide/teams/members-and-invitations)
>
> Roles, seats, and what removing someone takes with it.
>
> === [Subdomains and custom domains](/foliums/blueprintr-user-guide/sharing/subdomains-and-custom-domains)
>
> Give the organisation its own address.
>
> === [Foliums](/foliums/blueprintr-user-guide/foliums)
>
> Documentation sites are organisation-owned and need the licence.