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

# How Postiz works

> The words Postiz uses, defined once

Postiz has a small vocabulary that the rest of these docs, the API and the
support channels all assume. This page defines it once.

## Organisation

Everything you own lives inside an **organisation**: channels, posts, media,
tags, team members and settings. You can belong to more than one, and when you
do, an organisation switcher appears in the top bar. Switching reloads the app
into that organisation's data.

The first person to register creates the organisation and becomes its owner.
Others join by invitation, see [Team](/general/settings/team).

## Channel

A **channel** is one connected social account: one X profile, one LinkedIn
page, one Discord server, one subreddit-capable Reddit account. Connecting the
same platform twice gives you two channels.

<Note>
  The app says **channel**. The Public API and the CLI say **integration**. They
  are the same object. Anywhere the API asks for an `integration.id`, it wants
  the ID of a channel, which you can copy from the channel's context menu.
</Note>

Channels can be **disabled** rather than deleted. A disabled channel keeps its
history and stops being available for posting. On cloud, disabling is how you
free a slot when you hit your plan's channel cap.

## Customer

A **customer** is a group of channels, normally one client of yours. Assigning
channels to a customer lets you filter the whole calendar down to that client,
and select all of their channels at once in the composer.

Customers also unlock an invite link: you can send a client a link that lets
them connect their own account into your organisation without having an account
of their own. See [Client groups and invite links](/general/channels/customers).

## Post and post group

When you schedule one piece of content to five channels, Postiz stores five
**posts** that share a **group**. That is why the API has both `deletePost` and
`deletePostsFromGroup`, and why deleting from the calendar removes the whole
set by default.

Inside a single post you can have multiple parts: a thread on X, a post plus
comments on LinkedIn. Part one is the post, the rest are thread items or
comments depending on what the platform supports. See
[Threads and comments](/general/composer/threads-and-comments).

## Global vs per-channel content

By default you write once in the **Global** tab and every selected channel gets
the same text. Unlocking a channel's own tab detaches it, so you can rewrite
that version without touching the others. Mentions are only available on a
detached channel, because a handle is only meaningful on one platform.

## Settings

Each platform has its own **settings**: a YouTube title and privacy level, a
Reddit subreddit and flair, a Pinterest board. They appear in the composer next
to the preview, and in the API as a `settings` object with a `__type` naming
the platform. Some are required and the post will not save without them.

## Tag

A **tag** is a coloured label on a post. The colour is what the post card shows
on the calendar, which makes tags the practical way to see campaign, client or
content type at a glance.

## Set

A **set** is a saved selection of channels and their settings. When you start a
new post, Postiz offers your sets so you can load "the client A channels,
configured the way I always configure them" instead of rebuilding it.

## Signature

A **signature** is a block of content you append to posts. One signature can be
marked auto-add, and it is then inserted into every new post automatically.

## Time slot

Each channel has a list of **time slots**, the times of day it normally posts.
Slots drive three things: the rows in the calendar's Day view, the "next
available slot" that RSS auto-posting uses, and the `find-slot` API endpoint.
They are a scheduling convenience, not a restriction: you can always post at a
time that is not a slot.

## Post state

| State         | Meaning                                                                        |
| ------------- | ------------------------------------------------------------------------------ |
| **Draft**     | On the calendar, never publishes. Prefixed `Draft:` on the card                |
| **Scheduled** | Queued for its date. This is the normal state                                  |
| **Published** | Sent to the platform. The card links to the live post                          |
| **Error**     | The platform rejected it. The card gets a red ring and the reason in a tooltip |

## Preview link

Every post has a public preview page. Sharing that link lets a client read the
post as it will appear and leave comments, without an account. See
[Share a post for approval](/general/approvals).

## Plug

A **plug** is an automation attached to a channel that fires after a post
publishes, for example auto-reposting it later or adding a follow-up comment.
Plugs exist for a handful of platforms only. See [Plugs](/general/automations/plugs).