Sourcing Teams

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.)
Add existing candidates from ATS
Add/import new prospects
Send a direct message to prospects
Update prospects' community status
Create and view notes on prospects
Add and remove tags from prospects
Add prospects to a job
Create new segments or add prospects to existing segments
Create, launch, view, and edit campaigns
Create, publish, view, and edit lead capture forms
Create and re-run connected searches

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. 

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.

Assigning CRM seats

Seats are assigned via User Management:

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.