(Internal) Cross-team Project sharing

🔍 Articles in This Section

Please use the following list to see additional internal articles regarding the SuccessFactors integration:

• (Internal) Projects: Overview
• (Internal) Cross-team Project sharing (📍you are here)

CRM Module: Cross-Team Project Sharing

This feature is intended to be enabled for agencies who want to share projects with a client. It is accessible from the Share dropdown on a project page, under the ‘Share with clients’ option, which will only show up for teams with CRM module enabled.

When you share a project with an email that is not associated with your Gem team, we send an email notifying that person of the project that was shared with them. This will let them see 10 prospects in the project, and a very limited set of details about those prospects, before logging in. Once they login they can see the full set of prospects in the project and their basic information. Additionally, they can copy the prospects from the project that belongs to the sharing team into a project that belongs to their own Gem team, and use that to sequence the prospects themselves, or do anything else they would like with them! They can also export a CSV of the shared project.

The flow for sharing a project with another team

What the project looks like to a logged-out user from another team

What the project looks like to a logged-in user from another team

FAQ

• Who can share a project with another team?
• Only the project owner or team admins can share a project with another team
• Can I share a project with an email that hasn’t signed up for Gem?
• Yes. They will be able to see the limited preview of 10 candidates before signing up, but must signup to see the full set of prospects and all their details.
• What data can other teams see about prospects in a shared project?
• They can only see basic information about the prospects. This currently consists of: email, first name, last name, company, job title, school, LinkedIn URL, location & phone number. This is the same set of information that is copied when copying the project, or when downloading a CSV of the project.
• Can I remove a client’s access to a project?
• Yes, by going to the same dialog you used to share the project with them, you will see a list of domains who currently have access to the project, and have the ability to revoke access to any of them.
• Do people who signup for Gem via having a project shared with them go through onboarding?
• Currently they do, though we may want to change that in the future.
• What happens when sharing with a client whose Gem team is deactivated? Or with an @gmail.com email (which are not allowed to sign up to Gem by default)?
• Sharing a project with another team does not supersede that, so they will need to contact us to re-enable their team, or whitelist them if they are an @gmail.com email (though I can’t imagine many agencies wanting to share lists of candidates with someone’s personal gmail account).
• What happens if I share a project with my own teammate (who has the same email domain as me) from the ‘Share with clients’ dialog?
• Right now it just shares them the project via email like usual. They will not be added to the list of domains the project is shared with, though the toast will say the project was shared with your own team’s domain. This is something we can improve in the future.
• Can people find projects shared with them from another team on gem.com?
• Not currently, right now they can only find these projects from the notification email that was first sent to them. This seems like something we should definitely improve in the future.
• Can team admins audit which projects are shared with another team?
• Not currently, though this seems like something we should add in the future!
• If I copy prospects from a project that was shared with me to a project on my team, will that stay in sync with the original project?
• No, but you can copy prospects from the original project again in the future and that should mostly avoid creating duplicates.

• FAQ