What is a Project-Protected Profile (PPP)?
When you go back more than a few hundred years many of us start to share the same ancestors. Large-scale collaboration can be very difficult.
This is why we created projects and started protecting certain profiles in high-conflict areas.
What is Protected on a PPP?
Merge Protection: The WikiTree ID of a Project-Protected Profile (PPP) is protected. If any new duplicates are identified, they must be merged into this profile. A PPP cannot be merged-away.
Managers of merged-in profiles do not automatically become managers of a PPP.
Management by Project
Rather than having hundreds of managers for historically-significant ancestors, individual members participate through the Project Account. The project as a whole works out controversial issues.
Some examples of projects:
- European Aristocrats
- Mayflower Ancestors
- US Presidents
- Puritan Great Migration
- New Netherland Settlers
- Dutch Roots Project
Projects are open to anyone who wants to collaborate on these profiles, and we encourage you to join.
What if Your Ancestor is Protected?
This is a good thing! It means your ancestor's profile is cared-for by experienced WikiTreers.
If your ancestor's profile is project-protected, you can't be the Profile Manager but you can participate by joining the project.
Keep in mind that you don't need to manage all your ancestors. You may not even want to be on the Trusted List for all your ancestors. You should be on the Trusted List for all close family members. You're likely to have information you want to add to their profiles, and when someone else adds or changes something you want to hear about it in your Family Activity Feed. However, you might not want to monitor all the changes to the profile of Charlemagne, for example, even if he's an ancestor of yours. Those changes would crowd your Activity Feed so it's harder to watch the profiles you care most about.
How to Protect a Profile
Leaders, see Project Protecting and Merging.
This page was last modified 16:17, 27 December 2017. This page has been accessed 10,323 times.