Overview

iShare may be used to display information that is sensitive or requires filtering from general use; for example: locations of domestic abuse crimes must not be widely available, detailed planning applications should only be available to those in the planning department. For further details please see Roles and User Authentication.

Enabling the Roles Editor in Studio

Before you can start to use the Roles Editor in Studio you will need to perform the Steps to enable Roles Editor in Studio.

Once these steps have been performed, the next time you open Studio, you should see the Roles Editor node.

Applying Windows Groups to iShare Roles

Now you have created your Windows Groups you can then apply these to individual iShare Roles using Studio.

Use the Add or Remove buttons to add and remove Windows Groups from the Roles Editor or click the Edit icon to amend existing details.

Name

The name for your iShare Role e.g. Planning where Planning is the name of your Map Source. This does not have to be the same but it makes it easier to quickly identify which role has been created for which Map Source.

Windows Group Name

Here you need to select one of the Windows Groups that you have created for iShare.

Windows Groups such as "Administrators", "Guests", "Remote Desktop Users", etc. listed under Groups in the Builtin container should NOT be used as bases for iShare Roles. This is because Microsoft .NET may not list an Active Directory User as belonging to these Groups on the iShare Web Service server but only as belonging to them on the Domain. This means that the user will not belong to the Role(s) in question (as we rely on the fact that they are in the Local Groups to authorise them).

Make sure that you Save all your changes in Studio by clicking the Save button. You will also need to close Studio and re-open in order to see any new roles under the Map Source Roles node.

Once you have created your iShare Roles you can then apply them to individual Map Sources and Map Layers.

Browser not supported