The ability to create users requires administrative permission in Aptify. This permission can be granted when the user record is created. By default, the sa user is the only user granted administrative permissions when Aptify is installed.

Aptify encrypts the password for untrusted users. Therefore, in order to create untrusted SQL Server Security users (that is, Username/Password-based users), your system administrative user account must have the necessary permissions to the Security Key (the Generic Entity Encryption Key, by default) that encrypts untrusted users' passwords. However, note that users do not need access to this key to successfully log in to the Aptify. See Adding User Accounts to a Security Key for details.

 

Follow these steps to create a new user:

  1. Log in to Aptify using a user account that has system administrator privileges.

    If you are logging in as a system administrator account, and you intend to create untrusted (Username/Password-based) users, your account must have permission to the Security Key that encrypts user passwords (which is the Generic Entity Encryption Key by default). See Adding User Accounts to a Security Key for more information and instructions.
     
  2. Expand the Users Administration application in the Navigation Bar.
  3. Right-click the Users service and select New Users Record to open the Aptify User Administration wizard.

    The Aptify User Administration wizard is not supported in the Aptify web interface.



  4. Step 1: Select a login method for the new user and click Next. Depending on whether Windows Integrated Security or SQL Server Security is selected, the individual's login is trusted or untrusted.
  5. Step 2: Specify the Windows account or user name and password for the new user, depending on the login security method you selected.
    1. If you selected Windows Integrated Security in the previous step, the wizard prompts you to enter the user's Windows Domain and Account. The Domain and Account lists are populated with existing domains and accounts from the network to which that user's Windows account belongs.
    2. Select a Windows domain from the Domain drop-down menu and then select or enter a user account that exists on that domain in the Account field.  

      Choosing Windows Domain and Account

    3. If you selected SQL Security, the wizard prompts for the login and password to be used by the user.
    4. Enter the new user's name in the User Name field, and enter the password twice, once in the Password field and once in the Repeat Password field. 

      Entering Login and Password
    5. Note that when specifying a Password, if the password does not meet the Windows policy requirements, an error message will appear prompting you to re-enter a new password. The Session Exceptions log contains more information about why the password change failed.
    6. If your organization is using untrusted user accounts, your users can change their own passwords after logging into Aptify. See Changing Your Password for details.
       
  6. Click Next to continue.
  7. Step 3: Select the Client Access License for the user by selecting the check box next to the appropriate License Access type.
  8. Click Next to continue.
  9. Step 4: Select the Module for which this user should be licensed by selecting the check box next to the appropriate License Access type.
  10. Step 5: In the Permit column, select the check box for each of the databases to which you want grant access to the user.
  11. Select the System Administrator option for accounts that require administrative access to the databases and the SQL server.

    When this check box is selected, Aptify automatically assigns the user a DB Owner role on the SQL server.

    If the System Administrator option is selected, the user is granted the dbowner role to the database in SQL server. This option should only be selected for administrative users who require this ability. Operations that require dbowner privileges include any action that adds a new table, database object, or login to the SQL Server, such as creating a new user, new entity, or a new stored procedure. Other actions may require sysadmin permission to the entire server. For accounts that require that level of access, you need to check the sysadmin role for that SQL Login directly within SQL Server Management Studio.



  12. If you want a system administrator account to able to create new users, select the Can Create Users option. 
  13. Confirm that the Active User option is selected and click Next to continue.
  14. Step 6: Enter the user's full name in the Name field. 

    Specifying Account Details
     
  15. If desired, enter a Description for this user account in the field provided.
  16. If desired, select an existing user account from the Copy an existing user's profile (optional) drop-down list.
      • The existing user's profile settings.
      • The existing user's displayed Applications.
      • The existing user's displayed Services.
      • The existing user's Data Control Bar button layout.
      • A copy of each of the existing user's Views and View Folders.
      • A copy of the existing user's Shortcut Bar (including Shortcuts and Shortcut Groups).
      • A copy of the existing user's personal dashboards (that is, dashboards with a User Usage Scope that are linked to the existing user).
      • A copy of the existing user's personal form templates (that is, form templates with a User Usage Scope that are linked to the existing user).

  17. Click Next to continue.
  18. Step 7: Select the Object Repository Context for the user from the drop-down list. This list includes all existing Object Contexts, as well as a <DEFAULT> option.
  19. Select the Culture for the user from the drop-down list. This list includes all existing Cultures, as well as a <DEFAULT> option.
  20. Click Next to continue.
  21. Step 8: In the Include column, select the check box for each Group to which you want to add the new user. 

    Adding User to Groups
     
  22. If you selected one or more Groups, specify one of the groups as the Primary Group in the field provided. Click Next to continue.
  23. Step 9: Create Entity Relations records as necessary.
  24. Click Finish to complete the creation of the user login.
  25. If this user needs access to credit card numbers (for example, if this user account is for an order entry clerk who will create orders and payments that use a credit card Payment Type), add the user to the Security Key that encrypts credit card numbers in the system (that is, the key that encrypts the CCAccountNumber field in the Payment Information entity).
  26. Depending on your geographic location, you may need to modify the Regional Options for the user's desktop computer and the default language for the user's SQL Server login so the system displays dates, times, numbers, and currencies in the appropriate format for that user.