Why can't an "Open" project have contributors?
Often our projects start out as secret, become closed (when announced to wider business) but can never be "Open" as you kick out contributors with that change. I don't understand the logic.
Solved! Go to Solution.
Solved by rahul.bhandarkar. Go to Solution.
Hi Robin,
Project Contributors are typically 'external' users e.g. contractors/sub-contractors who work on projects but don't have the ability to create new projects or be promoted to an Admin of a project. Contributors can only see projects that they are explicitly invited to, they cannot discover other projects that are part of the hub unless they are invited. This is the main idea behind separating Members (internal) versus Contributors (external users).
An Open project provides a way for 'Members' to automatically join the project without requiring Admin approval. Open Projects would typically have content that you don't mind sharing with all the members in your hub but don't want to go through the overhead of an Admin approving each time someone in your company wants to join that project.
You can think of an Open project as a Closed Project with AutoJoin option turned ON. Infact, we are thinking about changing this in future so that there is less confusion between Open and Closed projects. There would only be Closed Projects with AutoJoin option turned ON/OFF.
Hope this helps, let me know what you think.
thanks.
If "Closed Projects with AutoJoin option turned ON." still allowed contributors I can see that working. There are projects where I would like the team to auto join (internal users) but would need contributors enabled for external users/consultants
Thanks,
Robin Capper.
I concur... I am running into that situation now. I would like my Team Members to be able to see/join Open projects, but also need outside Project Contributors to be able to access those projects.