Specify default OU for new object creation.

This setting is deprecated.

To limit UPN suffixes when creating new objects in the Web Portal, please use Attribute policies .

Leave this setting blank to use the default list of domain suffixes.

Specify whether to display the Ticket field on the web form or not.

By default, the ticket is not displayed.

Specify whether to display the Comment field on the web form or not.

By default, the comment is displayed. 

The default UPN suffix is defined in the Default domain setting in the AD Users web query .

Cayosoft Administrator has 20 character limitation as this is Microsoft's recommendation for backward compatibility. For more details, please see this article: SAM-Account-Name attribute.

This is not a hard limit and you can increase the maximum number of allowed characters using Attribute policies .

NOTE: The primary email prefix generation rule works only if the option to Show email prefix and suffix controls is set to Yes. in all other cases, an email will be generated automatically as UserPrincipalName (UPN) regardless of its generation rule.

By Microsoft convention, UserPrincipalName should map to the user's email name. The point of the UPN is to consolidate the email and logon name spaces so that the user only needs to remember a single name.

Specify when the mail attribute must be set:

• Always

• Only when a user is created with a mailbox 

You can specify the default values for these attributes that will be displayed on the New User creation wizard.

Also to generate default values for these attributes, you could use Attribute policies .

Select which button for mailbox type must be selected by default on the New User creation wizard:

• No mailbox

• Exchange on-premises

• Exchange remote or Microsoft 365

For more information about mailbox types please see Hybrid users and remote mailboxes.

A hybrid user account is an Active Directory account that also has a corresponding Microsoft 365 account. 

Specify the way how the Microsoft 365 licenses will be assigned to a user if a matching Microsoft 365 account is going to be created:

• User selects license during creation - the Microsoft 365 licenses are selected in the Web Portal during user creation

• Use automated license rule - if you use this option, you should configure the New User | Office 365 User Enforce License. After that, when a new Microsoft 365 user is created in the Web Portal, the License Options control won't be displayed on the New User form, and the Microsoft 365 license options, specified in the automated rule,  will be assigned to this user by this rule after creation.

• Do not assign licenses during creation - new users will be created without Microsoft 365 licenses. For example, you should use this value in conjunction with the Mailbox Type set to No, mailbox if you plan to assign licenses to users with Azure AD group-based licensing.

If you use Active Directory extension attributes to store additional information for user accounts, you can select these attributes and map them to Other Attributes. For details please see this KB article: How to add custom attributes to New Object and Object Properties wizards in Web Portal.

To set labels or default values for these attributes, please use Attribute policies .

Virtual Attributes allow extending the attribute list for users in Active Directory without extending the Active Directory schema.

Select the virtual attributes from the list and map them to Virtual Attribute 1 - Virtual Attribute 25. 

For more details, please see the Virtual Attributes article.

If the user's properties depend on its organizational unit, then when creating a new user in Web Interface, it would be convenient to populate the default attribute values such as Department, Office, etc depending on the user's organizational unit.

Dynamic Attribute Mapping solves this problem.

For configuration, please see Dynamic attribute mapping in Web Portale article.