Sets
A set is a saved composer. It holds the channels you ticked, the settings you chose on each one, and the content that was in the editor when you pressed save.Save one
Open Settings and choose the Sets tab. The tab is deep-linkable, so/settings?tab=sets takes you straight there.
1
Press Add a set
The full Create Post window opens, the same one you write in every day.
2
Pick the channels and write
Tick the avatars, open each channel’s settings, write the content. A set needs at least one character or one image in it, the same floor a draft has.
3
Press Save Set
It sits at the bottom right, in place of the scheduling buttons. A small window titled Save as Set asks for a Set Name, and the toast reads Set saved successfully.
Use one
Once a single set exists, the composer stops opening straight away. Press Create Post, or click an empty slot on the calendar, and a small window arrives first, headed Choose a set or continue without one. Click a name and the composer opens already dressed. Continue without set at the bottom starts you blank, and closing the window cancels the whole thing. Running the same four channels for one client every week? That is the set to make first.Content comes back as one shared draft, not as per-channel variants. If you rewrote the text separately for LinkedIn inside the set, reopening it gives you the first channel’s version in the global editor and you shape the rest from there. Channels and their settings are the part that survives intact.
Signatures
Every post you write ends the same way. Write that ending once. Open Settings, choose the Signatures tab at/settings?tab=signatures, and press Add a signature. You get a text box, a question, and a save button.
The list underneath shows the first few characters of each signature, an Auto Add? column reading Yes or No, and Edit and Delete next to each row.
Only one signature can be automatic. Answer Yes on a second one and the first one turns to No by itself. Your organization has exactly one automatic sign-off at a time, never two competing.
Where it lands
There are two ways a signature reaches a post. By hand. In the composer, look at the small toolbar under the editor, next to the text controls. The squiggle icon carries the tooltip Add Signature. Click it and your signatures list opens with an extra Use Signature button on every row. Press one and the text drops into the box you are writing in, after a blank line. That same window adds, edits and deletes, so you can write a new sign-off without leaving the post. By itself. Start a post from an empty calendar slot and the automatic signature is already sitting in the editor before you type a word, on its own line. Two conditions have to hold: the signature is set to Auto Add, and you did not pick a set on the way in. A set brings its own content, so she does not stack one on top of the other.The prefill belongs to the calendar slot. The Create Post button opens a blank editor, and the toolbar icon is how you add the signature there.
Tags
Tags are colored labels you put on a post. They live at the bottom left of the composer, next to the repeat control, with the date picker and the save buttons at the far right of the same bar. The control reads Add New Tag while the post carries none, and once you pick some it shows the first tag in its own color with a+2 counter for the rest.
The color is the point. On the calendar, the first tag’s color becomes the strip across the top of the post card and the tag names are written into it, so a week of client work, launches and reruns separates itself by eye without you reading a single line.
A few edges worth knowing. The × only appears on tags you have not selected on the current post, which keeps you from deleting the label you are in the middle of using. There is no rename in the picker, so a tag you have outgrown is a delete and a new one. And deleting a tag takes it out of the picker without stripping it from posts that already wear it, so old cards keep their color.
Tags survive an edit: reopen a tagged post and the picker comes back with the same rows checked.
Tags travel over the API too. The create body carries a top-level
tags array of { "value": "Launch", "label": "Launch" } objects, and she matches the label against tags that already exist in your organization. A name she does not recognize is skipped rather than created, so make the tag in the app first. Sets and signatures stay inside the app.Which plan sees what
All three belong to the organization rather than to you, so a teammate opening the composer sees your sets, your signatures and your tag colors.
The signature icon in the composer toolbar belongs to the editor rather than to the settings tab, so it stays in the toolbar whatever your plan says.
Self-hosting? With billing switched off, your account reports itself as ULTIMATE, and both tabs are in the left rail of Settings from the first login. The full rule is in Plans and limits.
Writing a post
The composer these three live in, from the editor to the three ways out.
Calendar
Where tag colors show up, and where the + starts a post with your signature in it.
Plans and limits
What each plan unlocks, and why a self-hosted install has no gates at all.
Next steps
Writing a post
Where sets, signatures and tags are applied
The calendar
How tag colours read across a month
Customers
Another way to keep a client’s work together
Posting times
The other thing you set once and reuse