Automated Affinity New Starter Setup Checklists
When a designer joins, you hand WebRun their name and start date. WebRun signs in to your Affinity account, confirms a licence seat is available and which app version the studio is on, posts a tracked setup checklist to your studio Slack channel, and sends the new starter a WhatsApp message with what to install and where the shared project folder lives.
How do I set up a new designer with Affinity on their first day?
WebRun runs your designer onboarding. Given a new starter and a start date, it checks your Affinity account for a free licence seat and the studio's app version, posts a tracked setup checklist to Slack, and drafts a WhatsApp welcome with the install and folder details for approval before it sends.
- Every new designer starts with a licence, the right version, and folder access
- Setup is a tracked checklist someone signs off, not a memory game
- No first morning lost hunting for an installer or a project folder
Built for design studios · creative agencies · studio managers · in-house brand teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
affinity.serif.comin a real browser with your saved login - no setup, no API keys. -
1
Affinity - check the account, licence and version
WebRun opens Affinity to check the account, licence and version. - Sign in to your Affinity account and confirm whether a licence seat is free for the new starter
- Note the current app version the studio is standardised on and the download the new starter needs
- Record anything the studio manager has to action first, such as buying a seat or freeing one from a leaver
Done when You know whether the new starter can be licensed today and on which version.
-
2
Slack - post the setup checklist
WebRun opens Slack to post the setup checklist. - Post a setup checklist to the studio channel with the new starter's name and start date
- List each item with an owner: licence seat, app download and version, shared project folder access, and studio file naming rules
- Tick items off on the same thread as they are confirmed, so the checklist is the record the studio manager signs off
Done when The studio channel has a tracked checklist for this new starter.
-
3
WhatsApp - send the new starter their steps
WebRun opens WhatsApp to send the new starter their steps. - Draft a friendly welcome message for the new starter with the app version to install and where the shared project folder sits
- Hold the message for the studio manager to approve before it goes to a person outside the existing team chat
- Keep licence keys and passwords out of the message. Point to the studio manager for anything that needs a credential
Done when The new starter has been messaged, or the message is waiting for approval.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it buy a licence seat if none is free?
No. WebRun reports that no seat is available and leaves the purchase to your studio manager. It never spends money or places an order on your account.
Does it message the new starter automatically?
No. The welcome message is drafted and held for approval, because it goes to someone outside your existing team chat. A person sends it.
Will it share licence keys or passwords?
No. Credentials are deliberately kept out of every message and checklist. WebRun points the new starter at the studio manager for anything that needs a key or a password.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.