Settings
Open SharePoint Central Administration. On the home page, in the Virto Active Directory User & Password Manager section, click Virto Active Directory User & Password Manager Settings.

The settings page has three tabs: Fieldset Management, Service account and Password expiry notifications. The settings are farm-wide and are managed in Central Administration only.
The Fieldset Management tab has three lists:
- List of available fieldsets – Shows all configured fieldsets used in the User Manager (for example, User New, User Edit, Password Change) that define which fields appear in each operation.
- List of available field formats – Contains predefined input formats and validation rules (regular expressions) that can be assigned to fields to control how values are entered and validated.
- List of Fields – Displays all fields synchronized from the domain controller together with their mapped AD attribute names, formats, and options, using user‑friendly titles for easier configuration.

List of available fieldsets settings
A fieldset defines which fields a web part shows, how they are grouped into tabs, who may use the form and what happens after saving. Each web part on a page uses one fieldset. The product comes with fieldsets for user editing, copying, creation, password change and password expiration; you can add your own with Add a new Field Set and change or delete existing ones.
A fieldset has the tabs General, Contact Information, Organization, About Me and Security and Options. Open a tab and choose a field in Add Field to add it to the tab; only the fields of List of Fields are offered, and a field can be added to a tab once. Drag a field to change its place; click the bin icon to remove it. The web part does not show tabs without fields, and shows no tab bar when only one tab has fields.

The tabs and fields described below are those of the standard User Edit fieldset. The administrator sets the tabs and fields of each fieldset, so your fieldsets can look different.
Title
Displays the name of the fieldset (e.g., User Edit). This identifies the configuration applied to profile editing forms.
General tab: Contains primary identification attributes used in Active Directory user profiles.
- First Name – User’s given name.
- Last Name – User’s family name.
- Initials – Middle initials or abbreviation.
- Add Field – Dropdown to include additional attributes such as:
- Account
- Display Name
- Location
Contact Information: Holds personal and work contact details.
- Add Field – Option to include further contact-related AD attributes.
- Mobile
- Home Phone
- Web Page
- Postal Code
- Address

Organization: Displays details related to the user’s organizational structure.
- Post Office Box
- Company
- Department
- Phone Number
- Physical Delivery Office Name
- Add Field – Dropdown menu to add additional organization-related AD attributes.

About Me: Provides user biography or other descriptive information stored in AD.

Security and Options: Defines who may use the fieldset, password rules, account options and the e-mail sent to users.
- Select users and groups with access to this FieldSet – Who can use web parts with this fieldset.
- Use captcha – Shows a CAPTCHA before saving.
- Let users who are not farm administrators search the directory in Person fields – Off by default. When it is off, a Person field without Available Logins shows the current person, and a user who is not a farm administrator cannot change it. When it is on, such users can search the directory by name and login: the search starts from 2 characters and shows up to 20 results. Farm administrators can always search, and fields with Available Logins offer their accounts either way.
- Choose authentication mode – The account that makes the changes in Active Directory:
- Application pool account – the account of the web application pool.
- Service account – the login and password entered on the Service account tab of the settings in Central Administration.
- Secure Store – the Windows credentials of a Secure Store target application; only its target application ID is entered on the Service account tab.
- Web parts – The web parts that offer this fieldset in Choose fieldset. Leave empty to offer it in every web part.
- Password validations options – Minimum and maximum length, minimum number of digits, lower case, upper case and non-alphanumeric characters, and a Password Policy Description shown to users.
- User Options – Enable user account, Require password change on next logon, Password never expires, Require email confirmation before applying changes, Receive notifications about the results of operations.
- Html message template – The e-mail sent after the operation when Receive notifications about the results of operations is selected; it can be edited only with this option on. Tokens:
{0}user name,{1}confirmation URL (empty in this e-mail, see below),{2}current page,{3}password change page,{4}password expiration page,{5}edit user page,{6}copy user page,{7}new user page. - Password Expiration page, Password Change page, Copy User page, Create User page, Edit User page – Addresses used in the e-mails.


The standard fieldsets give access to nobody. Before a web part can be used, add the users, the Active Directory groups or Everyone in Select users and groups with access to this FieldSet. A user without access sees “FieldSet access denied” with the account name. Group membership is checked in Active Directory.
A new fieldset starts with Use captcha and Enable user account on and these password rules: 6 to 18 characters, at least 2 digits, 2 lower-case letters, 2 upper-case letters and 2 non-alphanumeric characters. The rules are checked when a user changes the password, in addition to the domain password policy; set a value to 0 to turn a rule off. The standard Password Change fieldset has Require email confirmation before applying changes turned on.
Enable user account, Require password change on next logon and Password never expires apply to the accounts created with the New User and Copy User web parts. They do not change existing accounts.
Confirmation and result e-mails are sent through the SharePoint outgoing e-mail settings to the e-mail address of the SharePoint user who ran the action. If the user has no e-mail address, the message “Unable to send email. The email address is missing” is shown.
When Require email confirmation before applying changes is selected, the change is applied only after the user follows the link in the e-mail. The link works once, for 24 hours, and only for the user who started the action. The confirmation e-mail (subject “Action confirmation”) has a fixed text with the link; the Html message template is not used for it.
When Receive notifications about the results of operations is selected, the user who ran the operation receives an e-mail made from the Html message template when the operation completes. In this e-mail the token {1} is empty, because the operation is already confirmed.
List of available field formats settings
In List of available field formats, you define reusable validation templates for fields.
- Title – Display name of the format (for example, “E‑mail”) that will be shown when assigning a format to a field.
- RegExp – Regular expression that specifies which input values are considered valid for this format (for example, an email pattern).
- Comment – Help text or validation message shown to users when the input does not match the required format, guiding them to enter a correct value.

You can also create your own field format by clicking “+Add new field format” button.

In the Edit User, New User and Copy User web parts, a value that does not match the format of its field is marked under the field: the message “The value of the field “…” does not match its format.” names the field and adds the Comment of the format. Save stays unavailable until the value is corrected, and the server refuses such a value as well.
List of Fields settings
To modify any field, click the pencil icon. Click the bin icon to delete the field.

These settings define how a single user profile field behaves in your app.

General field properties
- Title – Display name of the field in the form (here: First Name).
- AD Name – Mapped Active Directory attribute that this field writes to/reads from (here: givenName). The list shows the attributes of the user class.
- Allow Empty Values – When checked, the field is optional; when unchecked, a value is required.
Data type and input rules
- Field type – Data type used for the value (here: Unicode String, suitable for text). Besides the string, number and date types, the list has Case-sensitive String, Numeric String, OID String (object identifier) and SID (security identifier). An attribute that holds a person as a distinguished name (for example Manager) can be set up as Person, which is the type such an attribute gets when you add it: the form shows a people picker, the person chosen there is written to Active Directory, and the stored person is shown in the picker.
- Allow Multiple Values – If enabled, lets the field store more than one value; when disabled, only a single value is allowed. For such a field, the form lets the user enter several values, or choose several people for a Person field.
- Date only – Offered only for attributes of the type DateTime (UTC) in the Active Directory schema. The form then offers a date without time, and the date is saved as midnight. Attributes such as accountExpires have the type Large Integer and do not offer this option.
- Input Format – Optional constraint on how the value must be entered (for example, pattern, predefined formats, etc.). The web parts do not save a value that does not match the format (see List of available field formats settings).
- Range from / Range to – Minimum and maximum allowed length or value for the field (here: from 1 to 64, which typically defines allowed character length for the string).
- Max Value Length (text fields) – The longest value the field accepts. In the Edit User, New User and Copy User web parts, a longer value is marked under the field and is not saved. Leave it empty or 0 for no limit.
- Lookup Field (text fields) – Shows the field as a drop-down list in the Edit User, New User and Copy User web parts. Enter the values in Lookup Values, one per line; a value that is not in the list is refused. A field with multiple values cannot be a lookup field.
- Available Logins (Person fields) – The accounts the field offers, instead of a search in the whole directory. Only accounts that exist in Active Directory can be added. Leave it empty to let the field search the directory (see Let users who are not farm administrators search the directory in Person fields in List of available fieldsets settings).
Field type and Allow Multiple Values are taken from the Active Directory schema of the chosen attribute and cannot be changed; the only choice is between Distinguished Name (DN) and Person for an attribute that holds a distinguished name. Range from and Range to are locked when the schema defines a range.
If you scroll down, you can see “+Add field” button. By clicking it, you can create your own field(s).

You can choose from an extensive list of AD names in the dropdown.
Each Active Directory attribute can have one field. If a field for the chosen attribute already exists, the new field is not added, and the message “A field for this Active Directory attribute already exists (…). Open it in the list to change it.” names the existing field. Versions before 3.2.1 replaced the existing field without a warning.

Service account
The fieldsets with the authentication mode Service account run their Active Directory operations under this account instead of the application pool account. Enter the Account (DOMAIN\user or user@domain) and the Password, then click Save. The password is stored encrypted and is never shown again; leave the field empty to keep it. Give the account only the rights it needs in Active Directory.
For the Secure Store mode, enter the Target application ID of a group target application of the Secure Store Service with the fields Windows User Name and Windows Password. The application pool accounts of the web applications must have access to it. The credentials are read with the application pool account, so the users of the web parts need no access to the target application (in versions before 3.2.1, the mode worked only for users who were members of the target application).
Test connection checks the account against Active Directory and shows the account and domain it connected to, or the reason it failed.
Password expiry notifications
A farm timer job runs once a day and e-mails the Active Directory users whose password expires soon. Disabled accounts, accounts whose password never expires and accounts without an e-mail address are skipped.
- Send password expiry notifications – Turns the notifications on.
- Time of day (server time) – When the job runs (default 08:00).
- First notification, days before expiry (default 10), Second notification, days before expiry (default 3, 0 = none), Daily notifications during the last days (default 0 = none).
- Containers to check – Distinguished names, one per line; leave empty to check the whole domain.
- Accounts that never get a notification – Accounts that are skipped.
- Read Active Directory with the service account of the Service account tab – Otherwise the timer service account is used.
- Message – Subject, Body (HTML), Date format, Copy to. Tokens:
{UserName},{UserDisplayName},{UserEmail},{ExpirationDate},{DaysLeft},{Today}. - E-mail delivery – SharePoint outgoing e-mail settings or Own SMTP server (server, port, SSL/TLS, login, password, sender e-mail and name).
Click Save, then Send a test e-mail to me. Run now starts the job at once; Last run shows the number of accounts checked, due today, e-mails sent and errors.
When you save the settings with Send password expiry notifications on, the farm timer job Virto Password Expiry Notifications Timer Job is created (Central Administration › Monitoring › Review job definitions), with the description “Sends the password expiry notifications configured in Central Administration.”; when you turn the notifications off, the job is removed. Before version 3.2.2, the job is called “Virto Active Directory User & Password Manager: password expiry notifications”; a job that is already registered gets the new title and description with the update. The tab shows whether the job is registered; click Refresh to update the status and the last run. Run now works only after the settings are saved with the notifications on.