How does your institution deal with Blueprint Courses permissions, roles and workflows?

[ken_i_mayer]

I'm here because some of our schools at Georgetown want to try out Blueprint courses, and I'm trying to grant them permissions.

However, we restrict the "Courses add/edit/delete" permission to only admins in our IT department, because we do not want people accidentally breaking SIS_ID associations or deleting courses.

How does your institution deal with Blueprint courses and the necessary permissions?

[ken_i_mayer]

We've considered 

• using the API to manage permissions for Blueprint courses, which apparently Indiana University has done, creating a Blueprint Manager LTI tool (https://kb.iu.edu/d/apvn)
• giving school instructional designers or admins a Blueprint sandbox subaccount with full rights, where they can develop and test Blueprint courses and synch them, but then our team would move the courses into the school main folder and do the synching to live courses ourselves. This would create a lot of extra work for us.

What do your institutions do? Ideally the best solution would be for Instructure to make the Courses add/edit/delete permission more granular, so that one could have the ability to add or edit, but not delete, or edit specific fields, but not SIS_IDs, or just be granted the basics that would allow the Blueprint permissions to work.