Overview
System Requirements
Installing
Upgrading
Getting Support
The User Interface
The Toolbar
Configuration
Extract File Management
Receipt Settings
Process Settings
Server administration
Input File Viewer
File Storage
File Storage Management
Previews
The Rules Engine
Rules Interface
Creating Rules
Removing Rules
Using Templates
Purging
How to set up Purging
Manual Purging
Reporting
The Statistics Report
The Preview Report
Summary File
Action Logs
Changes Logs
User Creation Settings
1. General Options
2. Account Options
3. Path Options
4. WTS Options
5. Advanced Options
Using Placeholders
Setting Security Groups
Folder Access Rights
Email Alerts
Further Information
Domain Administration         Overview
Match Freezing
Glossary
 

Setting Security Group Membership

When adding or updating a user, the user can also be added to a designated security groups. The rules for the security groups are:

  • It must be a security group (not distribution group)
  • The notes field (on the security group) must contain a string which is the same as the value of a field from the extract file for the user being added. The string must end in a semi-colon (;)
  • The security group must be set up as described before the import takes place
  • The name of the security group is irrelevant
  • Security groups can exist anywhere on the directory (dependant on User Admin Pack configuration)

The field on the extract file to be used to manage security groups is set in the User Admin Pack. It is set to Office by default.

The full field is used by default. If a subset of the field is required, this can also be specified in the User Admin Pack.

Users are put into a security group by matching the text in the security groups note field against the specified field on the user on the extract file.

In addition there is an enhanced functionality, where the field can be split into two zones (one of two characters and one of four characters separated by a "."). This enables a single user to be placed into two security groups.

The user will be added to all security groups which match either the full code or the first two characters of the code. For example, a user in department "cc.thea" would be put in every security group which contains either the string "cc;" or the string "cc.thea;" in its notes field.

This enables generic security permissions to be set up at a high level (cc) and more specific permissions at a lower level (cc.thea).

Below are two example security groups. Someone in department "cc.acut" would belong to both groups, whereas someone in the group "cc.thea" would only belong to the left-hand group.