Skip to main content
Skip table of contents

Post-installation device setup

Logging in as machine administrator

After the terminal installation, if you need to log in at the MFD as machine administrator, perform the following steps:

  1. On the Authentication screen or device code flow screen or an error screen, tap and hold the logo in the upper left corner for at least 5 seconds.

  2. Enter your admin credentials.

Manual application configuration

You need to configure the terminal manually only if you haven't set the Customer domain and API key via the Terminal Deployment Tool or by configuring the terminal from the SAFEQ Cloud Web UI.

  1. Login as machine administrator to application settings (see section Logging in as machine administrator above).
  2. Update Customer domain or API key. Note that the API key field cannot be saved empty.
    How to obtain the API key: Log in to the SAFEQ Cloud Web UI and go to Security > API access keys. Click Add. Copy the key value and click Save. For more information, see API access keys.
  3. Tap Test connection.
  4. If needed, enable accounting.
    1. Fill in the machine administrator username and password. It will be used for accounting based on the device counters and for address book management. Without it, accounting will not work and the address book will display entries from previously logged users.
  5. If you wish to use proxy, tap Proxy settings.
  6. Fill and save the proxy settings.
  7. Back in the main menu, enable proxy.
  8. Tap Save configuration.
  9. The identity management URL will be updated after the Customer domain change automatically.
  10. Log out.

Manual device configuration 

The following steps are done automatically during the installation. 

Manual configuration is needed:

  • If you installed the Cloud Terminal from Ricoh App Store.
  • On G2 machines without Java enabled (the administrator is informed about this during the installation).
  • If the remote configuration fails due to an unexpected error (the administrator is notified about this situation during the installation).

Configuring USB Card Reader

Manual configuration is needed for card readers other than Y Soft card readers.

Configure the card reader in System Settings

  1. Navigate to System Settings > General Features > Program/Change USB Device List.
  2. Under Device 01:
    1.  If you have a YSoft card reader, enter values for Vendor ID: 214C and Product ID: 0202 (keyboard emulation mode).
    2. If you have a card reader from another manufacturer, you can find the Vendor ID and Product ID in Compatible Card Readers.

Set up card reader in Smart Operational Panel

  1. Navigate to User Tools / Settings > Screen Features > Screen Device Settings > IC Card Bluetooth Software Settings / External Interface Software Settings > Select IC Card Reader.
  2. Select Proximity Card Reader.
  3. Go into Proximity Card Reader Software Settings.
  4. The following screen will appear:
  5. Connect or reconnect a card reader to USB on the Smart Operational Panel.

    You can use only Smart Operational Panel USB – either a visible one or a hidden micro-USB through an adapter. The card reader will not work with MFD ports (on the back or on the side of the device).

  6. Check the settings, confirm the change, and restart the MFD.

Service menu settings

The firmware update should be updated to the latest version.

Note that devices with SmartSDK only lack the optional counter type settings. You can safely skip them.

Ask your Ricoh technician to configure the following settings for you:


Path: Optional Counter Type > Default Optional Counter Type

ID: 5-113-001

Value: 0


Path: Optional Counter Type > External Optional Counter Type

ID: 5-113-002

Value: 0


Path: Access Control >SDK Certification Device

ID: 5-401-230

Value: 00000001


Path: Access Control > Detail Option

ID: 5-401-240

Value: 00001000


Path: User Authentication > Printer

ID: 5-420-041

Value: 1

Authentication settings in Web Image Monitor

  1. Go to the Ricoh MFD web interface (Web Image Monitor).
  2. Log in as an administrator.
  3. Under Device Management > Configuration, change the following settings so the authentication application will be displayed:
    1. In Administrator Authentication Management, set User Administrator Authentication to On.

    2. In User Authentication Management, set User Authentication Management to Custom Authentication.

    3. In User Authentication Management, check that all functions are enabled.
  4. Restart the device. You may use Reset the Machine in WIM.

Set appropriate timers

Terminal inactivity timeout is a value for the user's automatic logout. It is defined for Cost centers and can be specified per user. This feature is currently not supported by Ricoh SOP.

The default value on MFD is automatically set to more than 3 minutes. It can be manually changed after installation.

  1. Login to WIM (Web Image Monitor) as machine administrator.

  2. Under Device Settings, navigate to Device Management > Configuration > Timer.

  3. As default set all timers higher than Terminal inactivity timeout (so for default Terminal inactivity value, set all values to more than 3 minutes). Most of the timers can be turned off if they are not needed.

Scan journal settings

For the users to always be able to scan, we recommend you setting the following scan journal deletion strategy:

  1. Log in to WIM (Web Image Monitor) as machine administrator.
  2. Go to Device Management > Configuration > Scanner > General Settings.
  3. Set Print & Delete Scanner Records to Do not Print: Delete Oldest.
  4. Alternatively, you can change this by setting SCAN_SETTINGS__PRINT_DELETE_SCANNER_JOURNAL SP option to 1.

Key Counter Management settings on the MFD

  1. Go to User Tools on MFD.
  2. Select Machine Features.
  3. Go to System Settings.
  4. Go to Administrator Tools. Use the Previous or Next buttons to locate the Key Counter Management setting.
  5. Unblock all functions.
  6. Set Document Server Feature to Off.
JavaScript errors detected

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

If this problem persists, please contact our support.