Knowledge Base
> Getting Started
Invite your first teammate
How to add someone to your Talinty workspace, what they'll see, and which role to give them.
| 2 Min Read
Pick a role first
Talinty uses role-based permissions. Picking the right role from the start saves you cleanup later. The four standard roles:
Owner. Full access, including billing and workspace deletion. You can have more than one Owner, but treat it carefully. Best for
the person or people who own the relationship with Talinty (whoever signed the contract, whoever pays the bill).
Admin. Manages users, jobs, integrations, and settings. Can't change billing. Best for talent acquisition leads, HR ops, or
whoever runs the workspace day to day.
Recruiter. Creates and manages jobs, candidates, assessments, and feedback. Can't add or remove users. Best for the team
members who do the actual recruiting work.
Hiring Manager. Sees only the jobs they're assigned to. Full collaboration tools (feedback, mentions, scorecards) inside those
jobs, nothing outside them. Best for engineering managers, sales leaders, anyone outside the recruiting team who participates in
hiring for their own team.
A few quick principles for picking roles:
Default to the most restrictive role that lets the person do their job. You can always grant more access; revoking access after the
fact gets awkward.
Reserve Owner for the smallest possible group, ideally one or two people. Owners can delete the workspace; that's a meaningful
power.
Hiring Managers don't need to see roles they're not interviewing for. Assign them to specific jobs to keep their view focused.
Note for the docs team: confirm role names and permission boundaries against the live product before publish. Adjust the list above
to match. The pattern (one-line description plus a "best for" note) is the pattern to keep.
Send the invite
Go to Settings → Team.
Click Invite teammate in the top right.
Enter their work email, pick a role, and (optionally) assign them to specific jobs.
Click Send invite.
Talinty emails them a link that's valid for seven days. Until they accept, the invite shows as Pending on the Team page, where you
can resend or revoke it.
[Illustration: Screenshot of the Invite teammate modal with the role selector and job assignment field highlighted.]
What your teammate sees on their end
When they click the invite link, they go through a shorter version of the onboarding flow:
They confirm their name and set a password.
They land on the dashboard with the role you assigned.
If they're a Hiring Manager assigned to specific jobs, those are the only jobs they'll see in the Jobs list. Everything else is hidden
from them by design. They won't see "missing" content or know there are other roles in the workspace; the view is clean.
If they have Recruiter, Admin, or Owner access, they see the full workspace from the moment they log in.
Help them get oriented
A few small things make a real difference the first time someone new lands in your workspace:
Tag them in a candidate profile with @theirname. They'll get a notification and learn how feedback flows inside Talinty in one
move.
Share a tab with them on a live role. It's the fastest way to communicate what you've already filtered and scored, without a
thirty-minute walkthrough.
Ask them to turn on email notifications in their profile settings. Talinty defaults to in-app only, which is quiet until they remember
to check.
Point them to this knowledge base. The Getting Started section takes them about an hour; it'll save you a lot of "where do I
find..." Slack messages.
Managing teammates after the fact
Things change. People change roles, leave the team, or take on new responsibilities. From Settings → Team, you can:
Change someone's role. Useful when a recruiter gets promoted to lead, or when a hiring manager gets brought into the recruiting
team full time.
Reassign their jobs. Especially for Hiring Managers, whose access is scoped per role.
Resend or revoke pending invitations. Pending invites expire after seven days; you can resend before then or revoke at any time.
Deactivate a former teammate. When someone leaves, deactivate rather than delete. Deactivation preserves their notes,
feedback, and audit trail so the historical record of past hires stays intact. Their access is revoked immediately.
A note on security
Owners and Admins can see, edit, and delete a lot. Treat those roles like the keys to the building, because that's effectively what
they are. A few simple practices:
Limit Owner access to one or two people.
Use SSO once it's available in your workspace, and require it for Admin and Owner roles.
Review the Team page quarterly. Deactivate anyone who's left.
Don't share login credentials, ever. If two people need access, invite both of them.