G'day Corion,

++ Thanks for your response and advice.

Although I didn't have any formal plan for this, what I originally had in mind was closest to the group approach you outline; however, the comaintainer approach does have advantages. Accordingly, I'm considering a model (which uses a bit of both) along these lines:

• A company account, as per group approach, controlled by the IT Manager (probably with credentials held by an additional person, e.g. SysAdmin Manager).
• IT Manager to grant and revoke comaintainer privileges to developers as necessary.

[For anyone interested, "The PAUSE Operating Model" has details about comaintainers, privileges, and so on.]