Skip to main content

How a Global Admin knows about the communities to modify?



Moderation in Connections 4.5  is an awesome feature, but may be pretty cumbersome. If you decide to moderate everything before it get published (ex-ante), you will enforce an strict rule over you social network. If you moderate after publishing (ex-post) ,you are basically relying on good will of other users flagging content around your organization. 

IBM Connections not offers you the very powerful role of Global Admin. It's a J2EE role, it is present both on Communities and Search (and other features too), but now let's focus on these two features.
So, a global admin can do everything on every community: great stuff, but how he gets to know a community exists?  With the basic community ui you have access to 

1) Communities you own
2) Communities you are a member of
3) Public communities

And the global admin role technically is neither of three. That's why the global admin role is also on search application, where he can see everything. So global admin could simply go to the search panel and looks for all communities? Well, the problem is search UI by default  will not accept a blank search argument. So you have to search for a letter, or something. So you won't have access to every community! How you can do this without using wsadmin script? Very simply using the atom feed!

http://connections.ibm.com/communities/service/atom/communities/all

This will show you every community you are entitled to see! So, if you are global admin, it will allow you to modify every community in your Connections! 

Comments

Popular posts from this blog

Multiple controllers with Spring Boot

Remember, when you want to have multiple controllers with Spring Boot, you should always name them differently in the annotation, otherwise they will not work So these two together will NOT work (or just one of them will work) These two instead WILL work.

Can't use the newest npm when node is installed with brew (MacOs)

Even though I installed and reinstalled node with brew, with last versione 11.8.0, apparently it kept using the last version fdecollibus$ npm install --global gatsby-cli npm WARN npm npm does not support Node.js v11.8.0 npm WARN npm You should probably upgrade to a newer version of node as we npm WARN npm can't make any promises that npm will work with this version. npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9. npm WARN npm You can find the latest version at https://nodejs.org/ /usr/local/Cellar/node/11.8.0/bin/gatsby -> /usr/local/Cellar/node/11.8.0/lib/node_modules/gatsby-cli/lib/index.js + gatsby-cli@2.4.8 npm -v gave me back version 5.6.0. I've therefore noticed that  /usr/local/lib/node_modules had wrong permissions assigned to root:wheel. A chown did not fix the problem: I've had to manually delete the content of the folder (cd / usr/local/lib/node_modules and -careful - type rm -rf ...