Automated UXPin Designer Onboarding
When a new designer is added to a UXPin project, WebRun confirms their project access, copies the team starter files and design system reference into a Google Drive onboarding folder built just for them, and posts a Slack checklist showing what is set up and what is still pending, so the new hire has everything ready on day one.
How do I onboard a new designer onto a UXPin project quickly?
WebRun watches for new designers added to a UXPin project, confirms their access, and builds a Google Drive onboarding folder with the team starter files and design system reference. It posts a Slack checklist showing what is ready and what is pending, so a new hire has everything set up before their first design review.
- New designers start with files and access ready, not a scavenger hunt
- The design lead sees setup status in Slack without asking around
- Every onboarding folder is built the same way, every time
Built for design team leads · UX managers · product design agencies · in house design 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
app.uxpin.comin a real browser with your saved login - no setup, no API keys. -
1
UXPin - confirm project access
WebRun opens UXPin to confirm project access. - Open UXPin and confirm the new designer has been added to the right project
- Check their role and permissions match what was requested
- Note the project name and design system it uses
Done when The new designer's UXPin access is confirmed.
-
2
Google Drive - build the onboarding folder
WebRun opens Google Drive to build the onboarding folder. - Create a Google Drive onboarding folder for the new designer
- Copy in the starter files, brand assets, and design system reference
- Share the folder with their account only
Done when The onboarding folder exists with every starter file copied in.
-
3
Slack - post the setup checklist
WebRun opens Slack to post the setup checklist. - Post a Slack checklist to the design channel showing project access, folder, and reference links
- Mark each item ready or still pending
- Tag the design lead to confirm anything still outstanding
Done when The team has a Slack checklist showing setup status.
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
Does it grant UXPin access itself?
No. WebRun confirms access someone already granted and reports on it. It does not invite people or change permissions in UXPin.
What goes in the Drive folder?
The team starter files, brand assets, and design system reference your team keeps for onboarding, copied fresh so the new designer has their own set.
What if something is still missing?
The Slack checklist marks it pending instead of hiding it, so the design lead can see exactly what still needs a hand before the new hire starts.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.