Invite your team
Add teammates, give them the right role, and get each of them to one working automation in their first ten minutes.
Inviting people is the easy part. The part that matters is what happens in their first ten minutes, because a teammate who gets one real result keeps using TalentOS and one who just pokes at a chat box does not.
Before you invite anyone
Create at least one department first. Every member belongs to a department, and the invite form will ask you to pick one. If you have no departments yet, create them from Team. Departments can match your real teams: Marketing, Operations, Client Services.
Send the invitations
- Open Team from the Manage section of the sidebar.
- Select Invite to workspace.
- Paste the email addresses. You can separate them with commas, spaces, or new lines, so pasting a column out of a spreadsheet works.
- Pick a Role. Most people should be member. The admin option appears only for the workspace owner.
- Pick a Department for the people you are inviting. Members always hold one.
- Send. Each person gets an email with a join link.
Only the workspace owner can invite admins, appoint or demote admins, or change an admin's department. Any admin can invite members, resend or revoke a member invitation, remove a member, and move members between departments.
Which role to give people
- Member: the full product. Their own Talent, their own connected tools, their own Routines, Skills, and Artifacts, and everything shared with them. This is the default and it is the right answer for almost everyone.
- Admin: everything a member has, plus governance. Admins manage the team directory, departments, connections, workspace settings, and API keys, and can view billing.
- Manager: not a separate invite option. It is an added seat you grant later from Team, on top of someone's existing role, to give them oversight of a department.
- Owner: exactly one person, set when the workspace is created. Only the owner can start, change, or cancel a plan or update the card.
What your teammate does next
They click the link, sign in, and go straight into a short setup: name their Talent, pick a face and a working style, and choose whether to connect a messaging channel. Then they land on Home.
Send them these three things along with the invite. It is the difference between adoption and a dead seat.
- Connect the one tool your work depends on, from Connections. Usually email, calendar, or team chat.
- Ask your Talent for something real you would otherwise do by hand right now.
- Turn that into a Routine. Point them at Your first Routine.
Seats and cost
A seat is any active person in the workspace, including the owner and every admin. Pending invitations are not seats and are never billed. The count updates when someone accepts, and again when someone is removed. Your credit allowance is pooled across the whole workspace rather than divided per person, so a heavy user and a light user share one pool.
A worked example
An agency owner creates Client Services and Operations departments, then invites six people in one batch. Five are members placed in their department and the operations lead is invited as an admin. The owner sends each person the Morning brief Routine guide with the invitation. By the end of the day, four people have accepted, so billing shows four new active seats while the two pending invitations cost nothing.
What to check
- They created their own workspace by mistake. This is the most common failure. If they sign up with a different email than the one you invited, nothing connects the two and they end up alone in a separate workspace. Ask them which address they used, revoke the old invitation, and invite that exact address.
- The invitation expired. Revoke it from the invitation row in Team and send a fresh one. Do not resend the old link.
- They never got the email. Check spam, then confirm the address has no typo. Revoke and re-invite if it does.
- You cannot see the Admin role option. You are an admin, not the owner. Ask the workspace owner to send that invitation.
- You cannot finish the invite because no department is listed. Create a department in Team first, then invite.