The details: My intent was that each developer would have their own project where they have edit privileges but other users do not, and that there be a main project where the developers have no modify privileges and only a Builder account has privileges higher than Super Operator. To that end the Builder account has the DataStage Administrator component role, and the dev users have the DataStage User component role. Additionally, the dev users have the Prod Manager project role within their specific project and the Super Operator project role within all the other projects (including the main project).
Given this configuration I used the Builder account to open ISM, integrate version control, and perform the initial commit. All of those operations work fine for the Builder account but the developer accounts do not have access to any of the source-control operations (those items are grayed out on their context menus).
A. Does this sound like a permissions issue
![Question :?:](./images/smilies/icon_question.gif)
B. Am I going too far trying to isolate everyone's work to this degree
![Question :?:](./images/smilies/icon_question.gif)
C: Is this how ISM is intended to be used or am I missing the boat entirely
![Question :?:](./images/smilies/icon_question.gif)
D: What kind of deployment process do you use
![Question :?:](./images/smilies/icon_question.gif)
edit - corrected some spelling.