When Creating Shared Configuration Project Can You Make It "Unshared" Later

[Robert W_ Olsen]

A customer requested they wanted 8 Projects created from a single Project that they had access to and editted, but they wanted these new projects to be available for them to further edit in the future.  Using that baseline project, I created other projects using "shared configuration", so I can get all of the same schemes but then went through the process of copying and renaming the Schemes.  The customer has since told me that they cannot access and edit the workflows/screens.  Is this because I originally used "shared configuration" and once used, the project will be "flagged" as a shared configuration and non-Jira admins cannot edit these?  I assumed if I copied and renamed the schemes that they would then have access.

[Robert W_ Olsen · Accepted solution]

I believe there was some confusion on the customers part.  There are parts of the Project that are shared and some that are not,  The Issue Workflow/Screens that are "not shared" are editable by the customer.  This is a non-problem and has been resolved.