LinkedIn Writing configures the assistant's writing style and instructions. You need access to the settings page; company-wide changes require authority over the shared defaults. The advanced custom system-prompt controls are shown only to the privileged roles recognized by this page.

What you’ll see

The LinkedIn Writing page, where you pick a Voice, such as Friendly or Professional, for messages the LinkedIn sidebar writes.

Confirm which settings you are editing

  1. Open Settings → AI Assistant → LinkedIn Writing.
  2. Read Who does this apply to? before touching a field.
  3. Distinguish the company default from your personal override. A personal override replaces only the fields changed there; the rest comes from the company settings.
  4. Inspect Voice, Style, Guardrails, Identity, and Per message type.

Voice presets include Friendly, Professional, Sharp, Consultative, and Custom. Style controls include formality, sentence length, language, first-name opening, emoji, sign-off, and maximum characters. Guardrails include call-to-action preferences and instructions about what to include or avoid.

Edit deliberately

This page autosaves changes after settings have loaded. There is no final Save Changes step that makes exploratory typing harmless. Confirm the intended scope and approved wording first, then edit only those fields.

Per-message settings cover Connection request, Comment reply, Cold email opener, and Inbound reply, with tone overrides, instructions, and example messages. Use examples approved for reuse without copying private customer conversations into shared defaults.

The page's displayed character guidance is not a verified statement of LinkedIn's current platform limits. Review generated text against the actual destination's requirements when using it.

Check the result

Wait for saving to finish and read the success notification or service error. Reload the same scope and confirm the intended fields persisted. A local style change is not evidence of a generated message, a LinkedIn connection, or a sent communication.

If loading or saving fails, avoid making further edits until the stored scope is clear. An advanced prompt should not be used to bypass the account's operational permissions.

Related: Task Autonomy, Communication, Settings.

Screenshots

The screenshot for this guide is shown above, under “What you’ll see”.