| Name | The name of the group. The name must consist of characters that are compatible with Documentum Server’s server OS code page. |
| Group Native Room | Available in repositories with Collaborative Services is enabled. If you select a room, the group is considered a private group in the room. |
| Class | Distinguishes between groups, and roles. Select Group. The server does not enforce the value of this property, and does not set the property to any value other than group. |
| E-Mail Address | The email address for the group. This is typically the email address of the group’s owner. If no value is entered in this field, the group email address defaults to the group name. |
| Owner | The owner of the group. The user you select has the Create Group privilege. If you are a superuser, you can select the owner. Otherwise, you can set this to a group of which you are a member. |
| Administrator | The administrator for the group. The administrator can modify the group. If this is null, only a superuser, and the group owner can modify the group. |
| Alias Set | The alias set for the group. |
| Global Group | If you are connected to the governing repository of a federation, this makes the group a global group. |
| Private Group | Makes the group a private group. Otherwise, the group is public. By default, groups created by users with system administrator or superuser privileges are public, and groups created by users with a lower privileges are private. |
| Dynamic Group | Makes the group a dynamic group. A dynamic group is a group comprised of potential members, any of whom can be made actual members at runtime. The default membership setting for a dynamic group is Treat users as non-members. This means that at runtime, the potential members do not automatically become actual members. At runtime, however, the application from which a user accesses the repository can request that the user be made an actual member. You can use dynamic groups to model role-based security. For example, suppose you define a dynamic group called EngrMgrs. Its default membership behavior is to assume that users are not members of the group. The group is granted the privileges to change ownership, and change permissions. When a user in the group accesses the repository from a secure application, the application can issue the session call to add the user to the group. If the user accesses the repository from outside your firewall or from an unapproved application, no session call is issued, and Documentum Server does not treat the user as a member of the group. The user cannot exercise the change ownership or change permissions permits through the group. |