Configure a signature once per workspace. Every post — from composer, chat, RSS auto-post, API, or agent — gets it appended automatically. Per-platform overrides, variable substitution, and a preview block that means nothing is ever silently inserted.
One signature that applies to every platform unless an override exists.
Different signatures for LinkedIn vs X vs Instagram — fallback to workspace default if unset.
{{name}}, {{site}}, {{cta}} resolve at publish time per workspace context.
The resolved signature is shown in the composer above publish — nothing silent.
Disable the signature on any single post without touching workspace settings.
Composer, chat, repurpose, auto-post, public API — same signature pipeline.
Agency clients can’t see each other’s signatures — enforced at the DB layer.
Aidelly resolves the signature before validating X/IG/LinkedIn char limits.
Open the Post Signatures section. One row per platform, plus a "workspace default" row.
Use plain text or the variable shortcuts ({{name}}, {{site}}, {{cta}}). Toggle "enabled by default".
Every new post in the composer shows the resolved signature in a preview block above the publish button.
Toggle off, or edit the post text — the signature snaps to the bottom and updates live.
A short block — typically your CTA, sign-off, contact line, or affiliate disclosure — that Aidelly automatically appends to the bottom of every post. Set it once at the workspace level and stop pasting "👉 link in bio" into every caption.
Yes. Define a workspace-default signature, then optionally override it per platform — a longer CTA for LinkedIn, a shorter one for X, a hashtag block for Instagram. Platform overrides fall back to the workspace default when not set.
{{name}} resolves to the workspace name, {{site}} to your linked website, {{cta}} to your default call-to-action stored in brand memory. Variables are resolved at publish time, so the same signature template adapts per workspace when an agency uses it across clients.
Every composer shows a signature preview block right above ComposerExtras with a toggle to disable it for that one post. Nothing is ever silently appended — what you see in the preview is exactly what publishes.
Yes — Aidelly resolves the signature before checking limits. X auto-trims the preview so the resolved caption + signature fits in 280 chars (or 25,000 if you have X Premium long posts enabled).
Signatures live in their own table (post_signatures) and are workspace-scoped via membership RLS — separate from brand memory, so you can change tone without touching the signature, or A/B test signature copy without re-running brand questions.