Project Permissions in Thrive allow for an additional layer of control over who gets to view and add specific details, including notes, outreaches, events, scorecards, documents, and more.
Confirm “Edit Project” Permissions
In order to create a project, you need to be assigned a role that has edit permissions at the project level: Engagement Coordinators, Researchers, Recruiters, Partners, and Admins all have this permission enabled with Thrive’s System Roles. Hiring Managers and Candidates can view projects, but can only see the details that your team chooses to share with them.
Adding the Project Team
When a project is created, the creator is assigned to the Internal Team, which means they automatically have edit access to the project. From there, they can assign other Internal Team members who will also have view and edit rights by default.
Create a Project
Click on the Action Button (the + icon at the top-right of your screen)
Select Create a Project from the drop-down
Add other users as Internal Team members
Designate yourself or other users as the project’s Team Lead (optional)
Click Create
Once you’ve created your project, you can add or edit project team members and grant additional permissions to the project team.
Note: When creating a project, the "Team lead" is now required and the "Internal team member(s)" are optional to allow for a more efficient and streamlined flow
Add “Edit-Access” Team Members on a Project
On the project page, click on the hyperlinked project name (e.g. CFO) at the top left–this opens the project side panel where you can access Team Members
Navigate to the Other tab
Select Team from the dropdown
Click the + icon to add more team members
Click the More Actions ⋮ icon (three dots) to designate a team member as the Team Lead (note: there can only be one team lead assigned per project) or remove a user from a project
The Internal team members you add in this manner will have edit access to your project, which means they can add people, notes, outreaches, move candidates into different stages, update the project’s status, schedule interviews with candidates, see compensation, documents, add connections, make associations, and list out references and referrals.
Add “View-Access” Team Members on a Project
If you want to grant an internal team member view-only access on a project, where they can see the status, but not make any edits, here’s how to add them.
Click on the More Actions ⋮ button (three dots) in the upper-right of the project page (If you have the project side panel open, you’ll need to exit out of this first)
Select Share
Type in the team member you wish to add and select their name from the drop-down (note: You can only add people who have been assigned user roles in Thrive)
Ensure their permission is set to Viewer
Click Save
View-only access on a project is suitable for senior leaders who want to check on progress occasionally, but are not conducting the day-to-day work.
Project Visibility
Unless they are marked confidential during creation, by default, projects are shared with all internal users within the organization, giving them view-only access. This helps teams collaborate and maintain awareness of collective work.
Project owners, those who have been designated as the Team Lead, can restrict search visibility from other internal users who are not assigned as Team Members on the search. This prevents the rest of the firm from seeing it.
How to Restrict Project Visibility
Click on the More Actions ⋮ icon (three dots) in the upper-right of the project page (If you have the project side panel open, you’ll need to exit out of this first)
Select Share
Under General Access, change Internal Access from Viewer to Restricted
Click Save
Do Team Leads on projects have special privileges?
No, Team Leads and Team Members have the same privileges–this label exists to help Internal Team members understand who to reach out to for guidance if needed.
Project owners (the users who created the project), however, do have one special privilege: They can restrict project visibility from other internal users who have not been assigned as Internal Team member to work on the project.
What is the difference between a Team Lead and an Internal Team member in terms of project visibility?
Team Leads and Team Members have the same visibility into the project. They will see all published notes and scorecards, in addition to events, outreaches, documents, associations, and compensation. Neither Team Leads nor Team Members will see private notes or scorecards of other team members that have not been published.
Sharing Controls
Project owners can manage project access using the "Share" button. To get there, click the More Actions ⋮ icon (the three dots in the upper right-hand corner of the Projects page).
They can grant specific individuals access to the project, defining whether they have view or edit access. They can restrict the default access for all internal users.
Confidential Projects
There's a specific mode for sensitive searches called "Confidential Projects". These projects are marked to limit visibility and editing only to the assigned project team. Instead of displaying the actual project details in listings, a project code name appears.
Confidential projects only appear in search results if you search by the project code name. Despite being confidential, you can still share the project directly with specific individuals if needed.
The confidential status can be toggled on or off at any time.
Hiring Manager Visibility
The Hiring Manager view is a dedicated interface that hides recruiter-specific details. To access it, click the More Actions ⋮ icon (the three dots in the upper right-hand corner of the projects page), and select “View as a Hiring Manager.”
You will see their view with a banner at the top, and can click around to ensure all of the notes and scorecard information present is acceptable to share with a Hiring Manager.
To hide notes and scorecards, recruiters can change the permissions from visible to hidden.
Can I limit what a user sees, even if they are on a project team? Yes, project owners can restrict access to a project, and specific permissions like viewing compensation data can be toggled off for collaborators.
Are project permissions the same for all internal users? No, depending on the user role, certain team members may not have the ability to view or edit projects. For team members who do have these permissions, once they are assigned to that project, their permissions may vary depending on whether they are granted Viewer or Editor access.
What’s the difference between Viewer and Editor access on a project?
Viewer access allows users to see project details, including job title, status, team members, project strategy, job description, target companies, benchmark candidates, documents, project notes (subject to specific note visibility settings), scorecards (subject to specific scorecard visibility settings), and analytics.
Editor access allows users to modify the project. They can take actions like defining the job parameters and strategy, adding or updating team members, adding or editing project notes, adding or editing documents, managing candidates within the project stages (like dragging and dropping on the Kanban board), adding candidates to the project, assigning tasks related to the project or candidates, managing scorecards, scheduling events for candidates on the project, and changing the project status. They also can set the compensation as confidential.
What are the default permissions for projects?
When a project is created, the creator automatically has edit access. Assigned team members also automatically have edit access by default and other internal users have view access, assuming they have the correct permissions enabled to view projects.
For confidential projects, only the assigned project team has edit access by default. Permissions are assigned by the project owner.
Additionally, team members granted Editor access to a particular project can change the visibility of notes and scorecards from visible to private, restricting this content from other team members and hiring managers.
Why can I download a project summary in one search, but not the other?
This means you are not a member of the search team and need to be granted permission.