Troubleshoot project-space saving or sharing
Check required fields, code, affiliation, and private or shared scope.
In this article
Find every highlighted field and distinguish required from optional values.
Confirm that the project code does not already exist in the relevant scope.
Verify active affiliation, your role, and the owning organization.
Confirm whether the change targets the private or shared side.
For sharing, verify eligibility of selected organizations, collaborators, and roles.
After a partial failure, refresh before resubmitting to avoid duplicates.
Practical guidance
After an error, reopen the project and check whether the intended change was stored before repeating it. Editing rights, shared-content rights and workflow approval are separate checks. Keep the original scope selected while diagnosing the issue, and preserve any unsaved text in an approved location.
Advanced tips
When a conflict is reported, compare your draft with the newly loaded values rather than overwriting the other contributor’s work. If saving succeeded but refreshing failed, report those two outcomes separately and avoid resubmitting a status transition already underway.