As stated under system users we use roles with an optional group in InfoGlue to control access. This is true for tool users as well as for extranet/intranet users. In 1.2 the extranet users and roles were separated from the internal ones but since 1.3 this changed to make administration easier and more consistent.

A small company will probably have at least 2-4 roles in the system depending on how they want to divide the responsibility and access between their staff. Often there are many, many more roles especially if extranet functionality is to be used.

The roles listing looks like this:


Important: The role anonymous must be available if you want to be able to protect content and pages internally in the tools but still want anyone to look at them on the public sites. All users not logged in through the extranet feature automatically get logged in as user anonymous and has the role anonymous. Be sure not to change anything on this role.

Important: The role cmsUser must be available and all users who should be able to access the tools should be part of this role. Be sure not to change anything on this role. Make sure not to add external users to this role as this means they can access the tools if you have not infrastructural barriers as well to that environment.

It’s a very simple list just like the users were and if we enter the details by clicking the role name we get the following screen:



Basically we just set the attributes in the table below and we are also able to set which system users is part of this role.

Field name

Typical values


Role name

Webmaster or whatever the role should be.

This value is for presentation only.



This value is for presentation only.

As with system users you can have properties on roles. This means you can set attributes on a role which also gives users in that role those attributes. Examples might be if you have an extranet role called “Regulars” on a e-business site they would have a attribute called “discount”. The same procedure for choosing content type to base which attributes a role should have applies here as for system users except that content types that are to be listed in the drop must be of type Role properties type.

You will see a new button called “Edit Role Properties” when you have selected a content type and the interface there will allow you to enter information in the same way you do when editing content.

From InfoGlue 2.9.6 and forward you can state priority on role and group-properties. Let’s say a user has 3 roles all with a WYSIWYG-config connected to it. Then the prio can help in getting the user to get the right config. The field is called "PropertyPriority” and is added automatically to the role properties form.