2 Replies Latest reply on Jan 5, 2010 2:53 PM by dennis.mondolo

    Confidential Information and Admin Rights

      We have several Space Admin at the root level who make changes to specific functions only available to them at that level. Having several of these Space Admin seemed fine until yesterday when information in a private group was made accessible to one of the root level Space Admin.

       

      If certain functions are only allowed at root level Space Admin or System Admin levels, what is best practice for being able to give access for individuals to do tactical updates (custom-css, adding new content widgets to all content page, etc.) but not have them inadvertently sent private information from a private group because they happened to be following a user's content updates.

       

      What are other companies doing around this issue?

       

      We have toyed with the idea of creating an admin account for these tactical updates, but wanted to see what other companies are doing or what Jive experts suggest.