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.
Hi Nova,
Great to meet you in person at Jive World! Good news for when you upgrade to 4.0, as this issue has been nicely addressed with the new permission settings in the admin console. Until then, there's not really a good solution that I know of...
That is good to know as this was an issue that we also needed to solve - especially with sensitive HR related issues.
Jive combines the most powerful features of collaboration software, community software,
social networking software & social media monitoring into the leading SBS solution.
© Copyright 2000–2010 Jive Software. All rights reserved.
915 SW Stark St., Suite 400, Portland, OR 97205
Sales: 877-495-3700 | General: 503-295-3700
Privacy Policy | Sitemap | Jobs | Contact Us