Skip to main content
When a prospect gets an invitation, most of them click the sender’s profile before they decide. Profile Studio lets you keep those profiles in step with your offer without logging in to each LinkedIn account. It is for LinkedIn senders only. It lives in two places:
  • A sender’s Profile tab: edit one sender’s profile, see its quality score, pending changes and history.
  • Senders → Profiles: the view across all senders, with Changes, Templates, Experiments and Insights.
Nothing is ever changed on LinkedIn by AI on its own. Every change is a draft until a person submits it, and every change goes through the same safety checks.

​
What you can edit

On top of the per-field limits:
  • At most 4 profile changes per sender per week, so a profile is never rewritten in one sitting.
  • One profile change per sender per day. Changes are scheduled inside the sender’s working hours, at least an hour apart across the workspace.
Some edits are never allowed: turning on Open to work, notifying the sender’s network, changing names, and adding the same new position to several profiles at once.
Adding a position records it on a real person’s work history, and it cannot be removed through the platform. Only do it with that person’s confirmation.

​
When a profile can be changed

A change is refused, with the reason and what to do about it, unless:
  • The sender is Connected and not paused.
  • The sender signed in with the hosted sign-in link or browser sign-in. Accounts connected only by Chrome extension cookie can’t be edited, because the platform can’t confirm who owns them.
  • The sender has reached warm-up level 1. At level 0 the profile-edit allowance is zero.
  • At least 72 hours have passed since the sender connected or reconnected. LinkedIn watches new sessions closely.
  • The sender’s health score is 50 or more.
  • The field isn’t locked by a running experiment.
You can still prepare drafts while a sender isn’t eligible. The Profile tab shows what is blocking it at the top.

​
Editing one sender

Open the sender and go to the Profile tab.
1

Refresh the snapshot

Press Refresh snapshot to read the current profile from LinkedIn and score it. This uses one profile view from the sender’s daily allowance. The editor shows the current value of each field next to your proposed value.
2

Edit the fields

Open a field, type the new value, and watch the live preview on the right. Each field shows how many changes are left in its period. AI headline and AI About write a draft from the profile and an optional brief; you edit it before anything happens.
3

Save or schedule

Save draft keeps your work. Schedule change books it into the sender’s next free working-hours slot. You can add a note explaining why.
After a change lands, the platform reads the profile back a few minutes later and confirms each field. If LinkedIn didn’t take a field, the change shows as Partly applied with the fields that failed. Nothing is retried on its own.

​
Change statuses

If LinkedIn ends the sender’s session while a change is waiting, the change goes back to Draft. It is never re-applied on reconnect without someone submitting it again.

​
Reverting a change

Open History on the Profile tab and press Revert on an applied change. Before anything is queued, you see what can be restored and how faithfully: A rollback is an ordinary change: it uses a profile-edit slot and follows the same limits.

​
Profile quality score

The Profile quality card scores the profile out of 100 from the last snapshot and lists what to fix, most serious first. The score also appears as a badge on the Senders list and on the sender’s page. A critical failure keeps the sender from moving up a warm-up level until it’s fixed. The score is refreshed weekly for senders that use Profile Studio.

​
Templates and bulk apply

Go to Senders → Profiles → Templates to keep a whole cohort’s headlines and About sections aligned with one offer. Managers can create templates. A template holds a headline, an About section and a custom link, with variables such as {{first_name}}, {{company}}, {{title}}, {{client}}, {{location}}, {{custom.region}} and fallbacks like {{offer|faster month-end closes}}. Sender values fill in from each sender’s last snapshot. Photos and job entries are per sender and aren’t templated.
1

Apply to senders

Press Apply to senders on a template and pick the senders. Add custom variables for this run if you need them.
2

Preview

Press Preview. You see the rendered text for every sender, and which ones are excluded and why (limits, warm-up, health, a running experiment).
3

Apply

Press Apply to N senders. Each sender gets its own change, spread out at one sender per hour.
Link to a sequence connects a template to a sequence, so you can see which senders in its pool match the template. It never changes profiles on its own.

​
Experiments

Go to Senders → Profiles → Experiments to test two headlines or two About sections against invitation acceptance. Managers can start experiments.
1

Set it up

Press New experiment, name it, choose Headline or About, and write Variant A and Variant B. Pick at least 4 senders; they are split at random into two balanced groups.
2

Washout

Every sender’s profile changes to its variant. Invitations sent before the change, and during the washout days after it (3 by default), are left out of both groups, because those prospects saw the old profile.
3

Running

The experiment counts invitations sent after the washout. It’s Ready to read once each group has enough resolved invitations (120 by default).
4

Read and conclude

Press Readout to see each group’s acceptance rate, the 95% interval on the difference and a plain verdict. Conclude and apply the winner changes the other group’s profiles to the winning variant.
The readout only declares a winner when the whole interval is on one side of zero. Otherwise it says Not conclusive and tells you roughly how many more invitations it would need. While an experiment runs, its field is locked for other edits on those senders. Abandon cancels pending changes; applied ones stay as they are.

​
Insights

Senders → Profiles → Insights puts each LinkedIn sender’s profile score next to its health, invitations and acceptance rate over the last 30 days, and compares the average acceptance of senders scoring 70 or more with those below. Acceptance shows n/a under 10 invitations.

​
Owner permission

A sender’s profile is someone’s professional identity. If your senders belong to clients or their employees, you can require the account owner’s own permission before anything on their profile changes. This is off by default. The workspace Owner turns it on in Settings → Workspace → Behaviour → Require the account owner’s permission for profile edits. See Workspace settings.
  • No permission is needed. Schedule change books every change directly.
  • The Owner permission card on the Profile tab says permission is off.
  • The owner isn’t emailed about changes.
  • Every other rule on this page still applies: limits, warm-up, the 72-hour wait, health, sign-in method and pacing.

​
Getting permission (when it’s on)

  • Ask the owner (Managers): enter the owner’s email, pick the fields and the mode, and optionally how many days it lasts. The owner gets a link, valid for 7 days, that needs no login. They can narrow the request or decline it. Only request Direct permission from people who have already agreed to it.
  • This is my account: if you own the LinkedIn account yourself, record permission for your own profile. You are still emailed after every change.
  • Revoke removes a permission. Changes waiting on it are cancelled.
If email delivery isn’t set up for your workspace, or the sender has no owner email, the app shows the link so you can pass it on yourself. Showing it is recorded in the audit log.

​
Using Claude or ChatGPT

With the Claude connector or the ChatGPT plugin, you can ask for a sender’s profile score, history and experiments, and have your assistant draft a profile change. Submitting a change, reverting one, applying a template in bulk and starting or concluding an experiment all wait for your yes. See MCP functions reference.