Skip to main content
Skip table of contents

Physical Records Management Plugin Configuration

To set up Physical Records Management properly, you must configure the plugin first (using either SQL Authentication or Windows Authentication). This establishes your connection to the SQL database. Then, you can configure the Physical Records Management connection. Each authentication method is described below.

Setting Up the Plugin using SQL Authentication

  1. Open the SQL Server Management Studio.

  2. In Object Explorer, right-click your server name, and then click Properties. The Server Properties window opens.

  3. From the left pane, click the Security page, and then select SQL Server and Windows Authentication mode in the Server authentication section. (Note: Windows Authentication mode is selected by default.)

    You can skip this step if the SQL Server and Windows Authentication mode setting has already been set on this server.  (If this option has not already been set, a message displays telling you that the server will need to be restarted.)


  4. Click OK to close the window.

  5. Return to Object Explorer, right-click your server name again, and select Restart.

  6. If the User Account Control window box appears, click Yes.

  7. When prompted if you want to perform the action, click Yes. The SQL Server Database Engine restarts.

  8. Return to Object Explorer and expand the Security folder.

  9. Right-click the Logins folder and select New Login... The Login - New window opens.

  10. Enter the credentials for a new SQL Server Authentication login. (For information on creating a new login, see Microsoft's SQL documentation.)

    Note: Ensure that you uncheck the box for "User must change password at next login".

  11. Click OK to create the new login.

  12. Under Select a page, click User Mapping. The User Mapping page displays.

  13. Give db_reader and db_writer access to any Manager Web databases, including the following SQL Server databases, for the new SQL login you just created.

    • InformationLifecycle

    • PhysicalRecordsManagement (or the database name you entered during the installation process)



  14. Under Select a page, click Securables. The Securables/Permissions window displays.

  15. Under the "Permissions for" section at the bottom, scroll down to Connect SQL, ensuring that under the Grantor column, the name of your new SQL Server authentication login is listed there.

  16. Select the checkbox under the Grant column.

  17. Click OK. This concludes the steps required in SQL Server Management Studio.

  18. Next, sign in to Records Management's Manager Web as "Administrator" to create a Service account for the Physical Records Management plugin.

  19. Click Settings > Plugins. The plugins list displays.

  20. Click the ellipsis (...) to the right of the Physical plugin. The Edit window displays.

  21. Click the Enabled checkbox.

  22. Enter values for SQL Server and SQL Database.

  23. Click the Use SQL Authentication checkbox.

  24. Enter the Username and Password for the login you created in SQL Server Management Studio.

  25. Click Save. The Edit window closes, and the following occurs:

    • The Physical tab displays at the top of the Manager Web Main Menu.

    • The following new roles appear on the Secure tab:

      • Physical Administrator

      • Physical User

Setting Up the Plugin using Windows Authentication

  1. Create a new service account for the Physical Records Management user.

  2. Click Settings > Plugins to see the list of available plugins by name.

  3. Click the ellipsis (...) next to the desired plugin name to open the Edit window.

  4. Check the Enabled box. (This activates the Physical tab on the Records Management main menu.)

  5. Enter the name of your SQL Server and your SQL Database.

  6. Click Save. The Edit window closes, and the following occurs:

    • The Physical tab displays at the top of the Manager Web Main Menu.

    • The following new roles appear on the Secure tab:

      • Physical Administrator

      • Physical User





JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.