Short answer
Claude onboarding by role starts with one written pack per job: the seat, role, project and skills a new hire gets on day one. At CoworkConsultant.com I write each pack once, so you can add the next person in that job and they start from the same setup as the last one.
The first rollout went fine. Then someone new joins in March. You open Add member, paste an email, leave the defaults, and the new hire opens Claude to a blank chat and asks the next desk what to do.
The setup lives in your head, so every later hire gets a thinner version. This isn’t a training course or a checklist for your first five seats. It’s the page you open each time someone joins a role you already have. Before your first rollout? Start with the five seat onboarding checklist.
The first choice is the seat. On the Team plan you can mix and match seat types, so most roles sit on a Standard seat and the heavy user gets Premium.
| What the invite does | What it means for the pack |
|---|---|
| The email must use one of your organization’s allowed email domains | Get the work address before the start date |
| You choose the seat type and set the role and permissions in the invite | The pack decides both before you open the dialog |
| A pending invitation takes a seat right away | Don’t invite someone who hasn’t signed yet |
| Bulk add takes several emails at once | Two hires in one role go in one pass |
| Skills the owner provisions reach every member, switched on | A new member finds the shared skills already there |
Sources: Anthropic’s help articles on members and on organization skills.
Claude Onboarding by Role: The Four Slots in a Day One Pack
A pack is one page per job, not per person. It settles four things before the invite.
- Seat. Standard for most jobs. Premium only for the person who lives in Claude all day and needs more capacity.
- Role. User for almost everyone. Admin for the one person who adds members with you. An organization can have only one Primary Owner, and that stays you.
- Project. The shared project the job lives in, with its instructions already written. Project sharing and organization wide skills deployment are both listed as Team plan features.
- Skills. Every member gets the skills you provision, so the pack names the two or three this job actually uses.

When I set this up for a client at CoworkConsultant.com, I write the pack in the client’s words. A dental office bookkeeper and a roofing company bookkeeper do different weeks.
Three Packs I Write for a Small Office
Most small teams start with three.
- Office manager. Standard seat, Admin role, so you’re not the only one who can add a member. Project: office operations. Skills: house letters, meeting notes.
- Bookkeeper. Standard seat, User role. Project: month end. Skills: reconciliation notes, the house email voice.
- Project lead. Premium if they work long documents all day, otherwise Standard. User role. Project: one per client. Skills: the weekly client update, the proposal outline.
Same job twice? Same pack. For what each person does on their first morning, see what each role gets on day one. If your skills were written for you alone, read how I write skills by role first.
Apply the Pack When You Send the Invite
- Open Organization settings > Members and click Add member.
- Paste the work email. Two hires in one role? Paste both, one per line.
- Set Role and Tier from the pack. Tier is the seat type.
- Click Add member and send the person the project name.

Two things catch owners. A pending invite uses a seat before anyone accepts, and one left sitting expires. So I send it the week the person starts. The pack covers day one, and the questions that come back a week later belong in a short week two refresher.
Let me give you an example. A design firm hires a second project lead. On Monday the owner opens the project lead pack, pastes her work email, picks User and Premium, and sends it. She accepts, and the weekly client update skill is already on in her skills list. She opens her first client’s project, pastes Friday’s site notes and asks for the update. Claude returns it in the firm’s format: done, next, and what the client must decide.
Want the packs written for your roles? Book a short call with CoworkConsultant and leave knowing what each job gets.
New Pack or Copy One? Decide Before the Invite
A job you already have? Copy that pack and change only the email. A new job? Write the pack first.

A new job no current skill covers needs more than settings. That’s where a custom plugin build bundles its skills, and a company with several departments goes to custom plugin development on Strategized.ai.
Hire one person a year? Skip the packs. An afternoon side by side does it, and my two hour onboarding session is the agenda.
Michael’s take
The first five people get your full attention. Number six gets whatever you remember on a busy week. That’s how one office ends up with two setups for the same job and two different answers going to the same client. For a small business, the client notices before you do. One page per role keeps the sixth hire on the same footing as the first.
Write Your First Pack Before the Next Hire
Pick the role you hire for most and fill in five lines:
- Role name, in your own words
- Seat: Standard or Premium, and why
- Role: User or Admin
- Project: the one shared project they open first
- Skills: the two or three organization skills this job uses
Prompt: draft a day one pack for one role
I'm writing a one page onboarding pack for my bookkeeper role. Here is what that person does each week: [paste your notes]. Turn it into five lines: role name, seat (Standard or Premium, with one reason), role (User or Admin), the shared project they open first, and the two or three skills the job uses most. Then list anything in my notes that fits none of the five.
Claude returns five lines and a list of loose ends. Save it next to the shared project, where the next invite starts.
Rather write the packs with me? Book a free 20 minute call at any hour on my open calendar. You’ll leave with your most common role’s pack drafted.
When onboarding packs belong to whoever handles HR, a done-for-you Claude setup for small business HR configures the roles, projects and skills for each new hire.
Frequently Asked Questions
What should Claude onboarding by role include for a new hire?
A seat type, a role, the shared project they open first and the skills the job uses. CoworkConsultant.com writes these as one page per job, so every hire in that role starts the same way.
Can I pick Claude Team seats and roles while inviting a member?
Yes. CoworkConsultant.com sets both in the Add member dialog, the seat type under Tier and the role beside it, so the pack’s choices go out with the invite.
Do pending invites use Claude Team seats before someone accepts?
Yes, a pending invitation takes a seat right away. CoworkConsultant.com sends invites the week a person starts, since an unaccepted invite also expires and has to be resent.
Does Claude onboarding for employees include the organization’s skills?
Yes, once an owner provisions them. CoworkConsultant.com builds each pack on this: provisioned skills reach every member switched on, and anyone can turn one off.
