Skip to main content

Sourcing Teams

  • SmartRecruit


A sourcing team is a collection of individuals who have been invited by community organizers to manage the community and its prospects.

Sourcing Team Roles & Permissions

There are two roles in a community's sourcing team, Sourcers, and Participants. Users who have a CRM seat (you can read more about CRM seats below) can be added either as Sourcers or Participants to communities while users without a CRM seat can only be added as Participants.

When users are added as participants to a community, they have limited permissions:

Permission Sourcer Participant
Administrate the community (ie change description, change community status etc.) check.png close.png
Add existing candidates from ATS check.png check.png
Add/import new prospects check.png close.png
Send a direct message to prospects check.png check.png
Update prospects' community status check.png check.png
Create and view notes on prospects check.png check.png
Add and remove tags from prospects check.png check.png
Add prospects to a job check.png check.png
Create new segments or add prospects to existing segments check.png close.png
Create, launch, view, and edit campaigns check.png close.png
Create, publish, view, and edit lead capture forms check.png close.png
Create and re-run connected searches check.png close.png

Like hiring team roles for jobs, sourcing team roles set a user's permissions at the level of each community. A given user may have a different sourcing team role in different communities. 

System Roles & Permissions

Users who have an Admin or Extended system role and a CRM seat can access all communities with the same rights of a Sourcer even if they aren't part of the community's sourcing team.

Access Groups & Permissions

Users who have a CRM seat and are part of an access group have the same rights with a Participant in communities that share the same Org Field values with their access group.

Assigning CRM seats

Seats are assigned via User Management:AssignCRMSeat.png

A user's system role (e.g., Admin, Extended) also affects their ability to create and see other communities for which they are not on the sourcing team:

  • Admins and Extended user who have a CRM seat can create and see all communities.
  • Standard users with a CRM seat can create communities, but can view only their own communities.

Any user without a CRM seat, regardless of their system role, may be added to a community as a participant.