--- version: "2026.08.20" variant: "PMC" language: "en" --- # Cloud API documentation Public API is accessible on HTTPS via `/api/v1`. All functions require an X-API-Key header to be present which holds an API key. If API key header is missing, an HTTP error 403 (forbidden) is returned. All functions follow RESTful design. They can return either application/json or application/xml MIME type depending on the Accept header. By default JSON results are returned. For POST requests they are sent as request body with application/x-www-form-urlencoded type. Any special characters used to specify a resource name in an API request URL should be percent-encoded following the RFC 3986 standard. Depending on API key settings a user and/or device token might be required to be provided in the `Authorization` HTTP header when calling API endpoints. API calls expect only ASCII characters in the request URL. Non-ASCII characters should be percent-encoded. RICOH PMC contains a very broad range of API's internally to control virtually every aspect of PMC. If you're missing a capability or a function in the API, contact us, and we'll extend this public API as needed. --- version: "2026.08.20" variant: "PMC" language: "en" --- # API Functions ## Common / Security ### API key permissions Almost all API functions require **Advanced API permissions** on API key to be checked and a precise list of rights to be selected. An API call that does not require this option has a note"Does not require Advanced API permissions." Advanced API permissions allow to address the power of the API key for exact API functions. Whenever the **Advanced API permissions** option is selected, the permissions are checked within the API call, even if the API call does not require this access level. Each API function has the "Permission info" note, where the list of required permissions is mentioned. When the user token is used within the API call, the API key used for login has to match the API key used for the API call. The user token contains the user permissions that must match the **"Permission info"** note in each API call. For API calls whose descriptions do not contain a note "Does not require Advanced API permissions.", the "Advanced API permissions" of the used API key must correspond to the permissions listed in the "Permission info" note in each API call. Security We highly recommend you to use this option and select only the necessary permissions for each API key. If **Allow unauthenticated requests** option is disabled in the API key settings, all functions except **login** require a **user token** to be provided in the form of HTTP header: `Authorization: Bearer `. ## Version ### Get server version Permission info Does not require Advanced API permissions. Path: `/version` * Method: `GET` * Parameters: none * Returns: ` ServerVersionInfo ` ord print/copy/scan jobs: * Errors: 403 ## Account ### Get account information Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewAccount permission. Does not require Advanced API permissions. * Path: `/account` * Method: `GET`, `HEAD` * Parameters: `domainname: string` optional domain name. If not specified, the request address is used * Returns: `AccountInfo` for GET request, empty 200 status for HEAD request * Errors: 404 * Notes: * For `HEAD` request the X-API-Key header is not required * The returned AccountInfo includes primaryDomain --- the account's primary domain (the domainname flagged as primary, or the first domain if none is flagged; absent for a domain-less account). ### Create account Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewAccount permission together with the create permission matching the accounttype : * CreateVendorAccount - vendor * CreateAccount - customer * CreateContainer - container. * Path: `/account` * Method: `PUT` * Parameters: * `parentdomain: string` The domain name of the parent account * `accountname: string` Name of the account * `accounttype: int` Type of the account: 1 = vendor, 2 = customer, 3 = container * \[optional\] `primarydomain: string` The account's primary domain. If the value is not among the submitted domainname values, it is added to the account's domain list and flagged primary. When omitted, the first domain becomes the primary. * `domainname: string` Account domain name. This parameter can be specified more than once. The domain name can contain letters, numbers, hyphens, and periods. Any part of the domain name (separated by a period) should begin and end with a letter or number. * `applicationname: string` Account application name * \[optional\] `trustallclients: bool` Automatically trust the account value * \[optional\] `locationid: int` Id of the existing location to be assigned to the created account * Returns: `ErrorCodeInfoId` cURL example: #!/bin/sh `curl -X PUT -i -v -H "X-Api-Key:" -d "parentdomain=" -d "accountname=" -d "accounttype=" -d "primarydomain=" -d "domainname=" -d "applicationname=" -d "trustallclients=" -d "locationid=" -k "https://:7300/api/v1/account"` Replace all with real values. Example of resulting domain list and primary domain: | domainname sent | primarydomain sent | Returned domainNames | Returned primaryDomain | |-----------------|--------------------|-----------------------------|------------------------| | a.com, b.com | - | \["a.com","b.com"\] | "a.com" | | a.com, b.com | b.com | \["b.com","a.com"\] | "b.com" | | a.com, b.com | c.com | \["c.com","a.com","b.com"\] | "c.com" | | - | - | \[\] | (absent) | | - | b.com | \["b.com"\] | "b.com" | ### Update account Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewAccount permission together with the modify permission matching the accounttype : * ModifyVendorAccount - vendor * ModifyCustomerAccount - customer * ModifyAccount - container * Path: `/account` * Method: `PATCH` * Parameters: * \[optional\] `accountname: string` Name of the account * \[optional\] `primarydomain: string` The account's primary domain. If the value is not in the resulting domain list, it is added and flagged primary. When omitted, the existing primary domain is preserved. * \[optional\] `domainname: string` Account domain name. This parameter can be specified more than once A domain name can contain letters, numbers, hyphens, and periods. Any part of the domain name (separated by a period) should begin and end with a letter or number. * \[optional\] `applicationname`: `string `Account application name * \[optional\] `trustallclients: string `Automatically trust the account value * \[optional\] `locationid: string `Id of the existing location to be assigned to the created account * \[optional\] `locale: string `Account's language - expected values: "pt-BR" (Brazilian Portuguese), "zh" (Chinese), "cs" (Czech), "da" (Danish), "nl" (Dutch), "en" (English), "fr" (French), "de" (German), "id" (Indonesian), "it" (Italian), "ja" (Japanese), "ko" (Korean), "ms" (Malay), "no" (Norwegian), "pl" (Polish), "pt" (Portuguese), "sk" (Slovak), "es" (Spanish), "sv" (Swedish), "th" (Thai) * \[optional\] `defaultpapersize: string` Account's default paper size - expected values: "A3", "A4", "A5", "Letter" * \[optional\] `theme: string` Account's color theme - expected values: "blue", "orange", "purple", "red", "green", "breeze" * \[optional\] `timezone: string` Account's default timezone - expected values: IANA time zone ID (e.g. America/Halifax) or empty string to set "Default timezone". * Returns: `ErrorCodeInfoId` cURL example: curl -X PATCH "https://server_name:7300/api/v1/account" -H "X-Api-Key: key" -d "accountname=" -d "primarydomain=" -d "domainname=" -d "applicationname=" -d "trustallclients=" -d "locationid=" -d "locale=" -d "defaultpapersize=" -d "theme=" -d "timezone=" Example of resulting domain list and primary domain for an existing account: domainNames = \["a.com","b.com"\], primaryDomain = "a.com". | domainname sent | primarydomain sent | Returned domainNames | Returned primaryDomain | |-----------------|--------------------|-----------------------------|------------------------| | - | - | \["a.com","b.com"\] | "a.com" | | - | b.com | \["b.com","a.com"\] | "b.com" | | - | c.com | \["c.com","a.com","b.com"\] | "c.com" | | b.com, c.com | - | \["b.com","c.com"\] | "b.com" | | b.com, c.com | c.com | \["c.com","b.com"\] | "c.com" | | b.com, c.com | a.com | \["a.com","b.com","c.com"\] | "a.com" | ### Get containers Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewAccount permission. * Path: `/account/containers` * Method: `GET` * Parameters: None * Returns: list of `ContainerInfo` * Errors: 403 cURL example: curl -X GET -H "X-Api-Key: advanced_api_permissions_key" -k "https://server_name:7300/api/v1/account/containers" ### Update container Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewAccount and ModifyAccount permissions. * Path: `/account/container/*id*` * Method: `PUT` * Parameters: * \[optional\] `primarydomain: string` The container's primary domain. If not among the submitted domainname values, it is added and flagged primary. When omitted, the existing primary domain is preserved. * `domainname: string` Container domain name. This parameter can be specified more than once * `containername: string` Name of the container * \[optional\] `applicationname: string` Container application name * \[optional\] `locationid: int` Id of the existing location to be assigned to the container * \[optional\] `timezone: string` Container default timezone - expected values: IANA time zone ID (e.g. America/Halifax) or empty string to set "Default timezone". * Returns: `ErrorCodeInfoId` * Errors: 403, 404 cURL example: curl -X PUT -H "X-Api-Key: advanced_api_permissions_key" -k "https://server_name:7300/api/v1/account/container/CONTAINER_ID" -d primarydomain= -d domainname= -d containername= -d applicationname= -d locationid= -d timezone= Replace all `CONTAINER_ID` with real value. ### Delete container Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewAccount and DeleteAccount permissions. * Path: `/account/container/*id*` * Method: `DELETE` * Parameters: * \[optional query parameter\] `withsubnodes: boolean` true/false, whether to delete the non-empty container * Returns: `ErrorCodeInfoId` * Errors: 403, 404 cURL example: curl -X DELETE -H "X-Api-Key: advanced_api_permissions_key" -k "https://server_name:7300/api/v1/account/container/CONTAINER_ID?withsubnodes=true" Replace all `CONTAINER_ID` with real value. ## Login ### User authentication Permission info Does not require Advanced API permissions. Authorization with a device token or allowing untrusted endpoints is required . Path: `/login` * Method: `POST` * Parameters: * `authtype: integer` 0=password, 1=cardid, 2=shortid, 3=nameonly, 4=email * `userid: string` the id to authenticate * `password: string` an optional secret (required for authtype=0, optional for authtype=1, ignored for other types) * Returns: `UserInfo` * Errors: 401, 403 cURL example: #!/bin/sh curl -X POST -H "X-Api-Key: key" -d "authtype=0" -d "userid=username" -d "password=password" "https://serveraddress:7300/api/v1/login" ## Documents If the "Allow untrusted endpoints" option is disabled in the API key settings, this function requires a device token to be present in the form of an HTTP header: `Authorization: Bearer ` ### Get list of documents for user Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewJob permission. Does not require Advanced API permissions. Authorization with user token is required. Cannot call with an insecure API key. * Path: `/documents` * Method: `GET` * Parameters: * \[optional\] `status: list[int]` Status list for the documents. If not provided 0 =\> READY will be used. 0 =\> READY,1 =\> PRINTED, 2 =\> DELETED, 3 =\> EXPIRED, 4 =\> FAILED, 5 =\> RECEIVED, 6 =\> AWAITING_CONVERSION, 7 =\> CONVERTING, 8 =\> CONVERSION_FAILED, 9 =\> STORED. For more details see [Document Status Flowchart](https://docs.ricoh-pmc.com/api/latest/pmc/data-structures.md#Document-Status-Flowchart). * \[optional\] `maxRecords: int` The number of records to be retrieved. If not provided, 50 is the default value. Max value 500 * Returns: `list `of` DocumentInfo` * Errors: 403 ### Get documents' history Permission info If you provide a user token, make sure the user for whom the token was issued has ViewReport permission. Restriction info Only available for Customer account type. It is not possible to call this on Vendor or Container account types. In such case, the call returns a 400 error. Restriction info The timeout for this API endpoint is 5 minutes. This endpoint is designed to get raw document data for building custom dashboards. Since the output can potentially be very large, the endpoint is equipped with paging functionality. * Path: `/documents/history` * Method: `GET` * Parameters: * \[optional\] `maxrecords: int` Maximum number of records on the single response page. The default value is 200, maximum is 2000. * \[optional\] `pagetoken: string` If the number or records for your query exceeds `maxrecords` value, the endpoint responds with exactly `maxrecords` documents and non-empty `nextPageToken` field. Use value of `nextPageToken` as a `pagetoken` parameter to get the next page. * \[optional\] `datestart: datetime` ISO-8601 instant formatted start point for documents' creation dates range. Example: `2021-09-21T16:38:10.972Z` * \[optional\] `dateend: datetime` ISO-8601 instant formatted endpoint for documents' creation dates range. The maximum allowed timeframe is 1 week. `datestart` should be less than `dateend` , and the latter should be in the future. The default value is "last 24 hours". * \[optional\] `domainname: string` If you want to narrow the request scope to one of your accounts, you can provide its domain name. Queried account should be a sub-account related to the account you are querying. When this parameter is not provided, the query is made against the account that has domain, taken from URL and all its subdomains. * \[optional\] `username: string` The exact login name of the user for which you want data to be delivered. When not specified, no filtering takes place. * \[optional\] `portname: string` The exact name of the port where the document was printed. When not specified, no filtering takes place. * \[optional\] `status: ` `list[int]` Status list for the documents. When not specified, no filtering takes place. 0 =\> READY,1 =\> PRINTED, 2 =\> DELETED, 3 =\> EXPIRED, 4 =\> FAILED, 5 =\> RECEIVED, 6 =\> AWAITING_CONVERSION, 7 =\> CONVERTING, 8 =\> CONVERSION_FAILED, 9 =\> STORED. For more details see [Document Status Flowchart](https://docs.ricoh-pmc.com/api/latest/pmc/data-structures.md#Document-Status-Flowchart). * \[optional\] `jobtype: string Document job type (PRINT, COPY, SCAN, FAX)` Returns: * `documents`: array of `DocumentInfo` * `recordsOnPage: Integer` * `nextPageToken: String` * `dateStart: String` * `dateEnd: String` * `domainName: String` * `userName: String` * `portName: String` `DocumentInfo`: * `providerId: Int` * `uuid: String` * `documentName: String` * `documentType: Int` * `userName: String` * `totalPages: Int` * `colorPages: Int` * `duplex: Int` * `copies: Int` * `grayscale: Boolean` * `paperSize: String` * `dateTime: Long` * `storageOnline: Boolean` * `secure: Boolean` * `tags: list[TagInfo]` * `collate: Boolean` * `status: Int` Type of Status: 0 =\> READY,1 =\> PRINTED, 2 =\> DELETED, 3 =\> EXPIRED, 4 =\> FAILED, 5 =\> RECEIVED, 6 =\> AWAITING_CONVERSION, 7 =\> CONVERTING, 8 =\> CONVERSION_FAILED, 9 =\> STORED. For more details see [Document Status Flowchart](https://docs.ricoh-pmc.com/api/latest/pmc/data-structures.md#Document-Status-Flowchart). * `outputPortId: Int` * `outputPortName: String` * `jobType: String` (PRINT, COPY, SCAN, FAX) * `scanWorkflowId: Int` * `scanConnectorId: Int` `TagInfo` * `tagType: Int` Type of Tag: 0 = Department, 1 = Group * `name: String` Tag name `Errors: 400` Usage example: Example request curl --request GET 'https://yourhost:7300/api/v1/documents/history?datestart=2021-09-07T16:38:10.972Z&dateend=2021-09-10T16:38:10.972Z&domainname=testaccount1&username=admin&maxrecords=2' \ --header 'X-Api-Key: advanced_api_permissions_key' \ Example response { "documents": [ { "providerId": 65, "uuid": "1b83f9ca-a05b-44cf-8c0b-ae7b4c934f92", "documentName": "Importand document 12345", "documentType": 0, "userName": "admin", "totalPages": 0, "colorPages": 0, "duplex": 0, "copies": 1, "grayscale": false, "paperSize": "", "dateTime": 1631205678743, "storageOnline": false, "tags": [ { "tagType": 0, "name": "dev dep" }, { "tagType": 1, "name": "dev" }, { "tagType": 1, "name": "devsupport" } ], "collate": false, "status": 1, "outputPortId": 1, "outputPortName" "Test printer", "jobType": "PRINT" }, ... ], "recordsOnPage": 2, "nextPageToken": "8a63ee56-3d9e-404f-a131-86b3bf9025b8", "dateStart": "2021-09-07T16:38:10.972Z", "dateEnd": "2021-09-10T16:38:10.972Z", "domainName": "testaccount1", "userName": "admin", "portName": "" } Presence of the `nextPageToken` means that there's more data than you received on this page and you have to query next portion like the following: curl --location --request GET 'https://yourhost:7300/api/v1/documents/history?pagetoken=8a63ee56-3d9e-404f-a131-86b3bf9025b8' \ --header 'X-Api-Key: advanced_api_permissions_key' \ Repeat paging until returned `nextPageToken` becomes blank. ### Record print/copy/scan jobs: The request can be authentication either by using a device token or a user token. 1. If you want to use a user token, the user for the job record is taken from the user token. 2. If you want to use a device token, the user for the job record is taken from the required parameters "username" and "providerid". In any case, the request requires API key configured with an authenticated request or a trusted endpoint. * Path: `/documents/history` * Method: `POST` * Parameters: * \[required\] `jobtype: String ` Document job type: `PRINT, COPY, SCAN, FAX.` * \[optional\] `totalpages: String ` Total pages of the document. * \[optional\] `colorpages: String ` Color pages of the document. * \[optional\] `papersize: String ` Size of document paper. * \[optional\] `duplex: Boolean ` Types of duplex printing: If true use LONG otherwise `SHORT` . * \[optional\] `title: String ` Title of the document. * \[optional\] `serialnumber: String ` Serial number to find output port. * \[optional\] `address: String ` Address to find output port. * \[optional\] `username: String ` User name, if you use a device token. * \[optional\] `providerid: String ` Authentication provider identifier, if you use a device token. * \[optional\] `datetime: String ` Date time in format `YYYY-MM-DDTHH:mm:ss+HH:mm` to set concrete time of the record. Returns: 200 Success Errors: 400, 401, 403 Example request: curl -i -X POST -H "X-Api-Key:" -H "Authorization:" -d "jobtype=PRINT" "https://:7300/api/v1/documents/history" ### Upload document Permission info If you provide a user token, make sure the user for whom the token was issued has the AddJob permission. Does not require Advanced API permissions. * Path: `/documents` * Method: `PUT` * Parameters (**multipart/form-data** request): * \[optional\] `providerid: int` The ID of the authentication provider for the given user. If not provided or zero, the server will attempt to guess it. * `data: form-data` A multipart form parameter with **Content-Disposition: form-data; name="data"; filename="xxx"** header and content type `application/octet-stream` * `username: string` Name of the user * `portname: string` Name of the input port (queue) * `title: string` Document title * \[optional\] `copies: string` Number of copies * \[optional\] `grayscale: string` Should print grayscale true/false * \[optional\] `duplex: string` Duplex flag: 0=simplex, 1=long edge, 2=short edge * \[optional\] `outputpagesize` `: string` Output page size ("Original", "A3", "A4", "A5", "A6", "Letter", "Legal", "Ledger", "Tabloid" or custom "\x\" width and height in points - for example for A4 "595x842") * \[optional\] `pageorientation` `: string` Page orientation: 0 = portrait, 1 = landscape (Note: Some page output page sizes do not support page orientation - like Ledger or Tabloid.) * \[optional\] `scale` `: string` Scale in percent (1-100) * \[optional\] `collate: string` Should enable collation of the document true/false * Returns: `DocumentInfo` * Errors: 400, 403 cURL example: curl -X PUT -i -v -H "X-Api-Key: " -F "username=" -F "portname=" -F "title=" -F "data=@;filename=" -k https://:7300/api/v1/documents Replace all with real values. The "@" symbol in `-F "data="` is mandatory. If the extension of the 'filename' is different than pdf, please make sure that you include that extension to the 'title' parameter. For example, if the filename=file.docx, the title should be test.docx. Limitations for uploading MS Office files: * The maximum document size the user can upload is 200 MB. * Print preview of one Microsoft Excel file can contain at most 10 thousand pages. * The duration of conversion from MS Office files to PDF is limited to 5 minutes. If the user exceeds any of these limitations, it will result in conversion failure. ^Parameters outputpagesize, pageorientation, scale are supported only using the push print (when job is sent directly to the printer).^ ^With pull print (when job is downloaded on MFD and printed) these parameters are ignored.^ Uri upload is no longer supported for documents endpoint! ### Delete document Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewJob and DeleteJob permissions. Does not require Advanced API permissions for a user who owns the document. * Path: `/documents/` * Method: DELETE * Parameters: * `uuid: pathparam` Document UUID taken from the request path * Returns: `ErrorCodeInfo` * Errors: 403 ### Send document to output port Permission info If you provide a user token, make sure the user for whom the token was issued has ReleaseJob permission. Does not require Advanced API permissions for a user who owns the document. An insecure API key is not allowed for this request. * Path: `/documents//
` * Method: POST * Parameters: * `uuid: pathparam` Document UUID * `address: pathparam` Output port address * `SN`: `pathparam` Output port serial number * `copies: int` Number of copies requested * `grayscale: bool` Whether to output in grayscale (true/false) * `retain: bool` Whether to keep the document after printing (true/false), default is false * `duplex: int` Duplex flag: 0=simplex, 1=long edge, 2=short edge * Returns: `ErrorCodeInfo` * Errors: 400, 403 Content Content-type application/x-www-form-urlencoded has to be specified even when no additional parameters are specified. ### Download document Permission info If you provide a user token, make sure the user, for whom the token was issued, has ViewJob permission. Does not require Advanced API permissions for a user who owns the document. Insecure API key is not allowed for this request. * Path: `/documents/.content` * Method: GET * Parameters: * `uuid: pathparam` Document UUID * `copies: int` Number of copies requested * `grayscale: bool` Whether to output in grayscale (true/false) * `retain: bool` Whether to keep the document after printing (true/false), default is false * `duplex: int` Duplex flag: 0=simplex, 1=long edge, 2=short edge * Returns: 200 Success * Errors: 400, 403, 404, 503 ## Output Ports ### Get list of output ports for user Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewOutputPort permission. * Path: `/outputports` * Method: `GET` * Parameters: * \[optional\] `providerid: int` The ID of the authentication provider for the given user. If not provided or zero, the server will attempt to guess it. * \[optional\] `username: string` name of the user for which the ports will be retrieved * \[optional\] `enrichPorts: boolean` specify whether ports should include additional information, such as account, container and location id. Default: false * Returns: `list` * Errors: 403 ### Create output port - POST Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewOutputPort and CreateOutputPort permissions. * Path: `/outputports` * Method: `POST` * Parameters: * `domainname: string` Domain name of the parent account * `portname: string` Name of the port * `address: string` Port address * `porttype: int` Port type: 0 = dummy, 1 = printer * \[optional\] `serviceid: int` Id of the service (document output or terminal service) which this port will use. This parameter can be specified multiple times. * \[optional\] `vendor: string` Short name of the printer vendor (unknown, fujifilm, ricoh, km, sharp, hp, lexmark, xerox, kyocera, toshiba, canon, brother, epson, eop) * \[optional\] `embedded: bool` Whether this printer has embedded client (true/false) * \[optional\] `printprotocol: int` Printing protocol: 0 = tcp, 1 = ipp, 2 = spooler (CUPS) * \[optional\] `outputtype: int` Output type: 0 = raw, 1 = PDF, 3 = PCL6, 4 = Postscript level 3, 5 = Postscript level 2. The value of 2 is deprecated and should not be used. * \[optional\] `reversefinisher: bool` Whether this printer has a finisher with reversed path (true/false) * \[optional\] `printerippurl: string` Printer IPP URL * \[optional\] `modelfamily: int` printer model family: if PrinterVendor is RICOH =\> 0 = "Ricoh SDK/J" ;1 -\> "Ricoh SOP" \| if PrinterVendor is XEROX =\> 0 = "WorkCentre"; 1 = "AltaLink"; 2 = "VersaLink" * \[optional\] `monochromeprinter: bool` Monochrome printer (true/false) * \[optional\] `ipreaderaddress: string` IP Reader address * \[optional\] `embeddedconfiguration: int` Id of Embedded configuration * \[optional\] `deviceserial: string` IP Reader address * \[optional\] `matchinginputport: bool` If true, a matching input port is automatically created (true/false) * \[optional\] `description: string` Port description * \[optional\] `softwareCopyCollation:` `bool `Use software copy collation instead of internal printer copy collation (true/false) * \[optional\] `sendusername:` `bool `Jobs printed on this output port contain usernames instead of anonymous (true/false) (IPP only) * \[optional\] `deviceAdminUsername : string`Machine credentials for the specific output port (overrides credentials specified in Embedded configuration if given) * \[optional\] `deviceAdminPassword : string`Machine credentials for the specific output port (overrides credentials specified in Embedded configuration if given) * Returns: `ErrorCodeInfoId` curl example: curl -X POST -i -H "X-Api-Key:" -k "https://account-domain-name:7300/api/v1/outputports" -d domainname= -d portname= -d address= -d porttype= -d ipreaderaddress= -d deviceserial= -d reversefinisher= -d printerippurl= -d modelfamily= -d monochromeprinter= -d embeddedconfiguration= -d description= -d softwareCopyCollation= -d sendusername= Replace all with real values. ### Create output port - PUT This endpoint is being deprecated and will not be updated in future releases, please use POST create output port endpoint above. Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewOutputPort and CreateOutputPort permissions. * Path: `/outputports` * Method: `PUT` * Parameters: * `domainname: string` Domain name of the parent account * `portname: string` Name of the port * `address: string` Port address * `porttype: int` Port type: 0 = dummy, 1 = printer * \[optional\] `serviceid: int` Id of the service (document output or terminal service) which this port will use. This parameter can be specified multiple times. * \[optional\] `vendor: string` Short name of the printer vendor (unknown, fujifilm, ricoh, km, sharp, hp, lexmark, xerox, kyocera, toshiba, canon, brother, epson, eop) * \[optional\] `embedded: bool` Whether this printer has embedded client (true/false) * \[optional\] `printprotocol: int` Printing protocol: 0 = tcp, 1 = ipp, 2 = spooler (CUPS) * \[optional\] `outputtype: int` Output type: 0 = raw, 1 = PDF, 3 = PCL6, 4 = Postscript level 3, 5 = Postscript level 2. The value of 2 is deprecated and should not be used. * \[optional\] `reversefinisher: bool` Whether this printer has a finisher with reversed path (true/false) * \[optional\] `printerippurl: string` Printer IPP URL * \[optional\] `modelfamily: int` printer model family: if PrinterVendor is RICOH =\> 0 = "Ricoh SDK/J" ;1 -\> "Ricoh SOP" \| if PrinterVendor is XEROX =\> 0 = "WorkCentre"; 1 = "AltaLink"; 2 = "VersaLink" * \[optional\] `monochromeprinter: bool` Monochrome printer (true/false) * \[optional\] `ipreaderaddress: string` IP Reader address * \[optional\] `embeddedconfiguration: int` Id of Embedded configuration * \[optional\] `deviceserial: string` IP Reader address * \[optional\] `matchinginputport: bool` If true, a matching input port is automatically created (true/false) * \[optional\] `description: string` Port description * \[optional\] `softwareCopyCollation: bool` Use software copy collation instead of internal printer copy collation (true/false) * \[optional\] `deviceAdminUsername : string`Machine credentials for the specific output port (overrides credentials specified in Embedded configuration if given) * \[optional\] `deviceAdminPassword : string`Machine credentials for the specific output port (overrides credentials specified in Embedded configuration if given) * Returns: `ErrorCodeInfoId` curl example: curl -X PUT -i -H "X-Api-Key:" -k "https://account-domain-name:7300/api/v1/outputports" -d domainname= -d portname= -d address= -d porttype= -d ipreaderaddress= -d deviceserial= -d reversefinisher= -d printerippurl= -d modelfamily= -d monochromeprinter= -d embeddedconfiguration= -d description= Replace all with real values. ### Update output port - PATCH Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewOutputPort and ModifyOutputPort permissions. * Path: `/outputports/` * Method: `PATCH` * Parameters: * `outputportid: pathparam` Existing output port id * `domainname: string` Domain name of the parent account * `portname: string` Name of the port * `address: string` Port address * `porttype: int` Port type: 0 = dummy, 1 = printer * \[optional\] `serviceid: int` Id of the service (document output or terminal service) which this port will use. This parameter can be specified multiple times. * \[optional\] `vendor: string` Short name of the printer vendor (unknown, fujifilm, ricoh, km, sharp, hp, lexmark, xerox, kyocera, toshiba, canon, brother, epson, eop) * \[optional\] `embedded: bool` Whether this printer has embedded client (true/false) * \[optional\] `printprotocol: int` Printing protocol: 0 = tcp, 1 = ipp, 2 = spooler (CUPS) * \[optional\] `outputtype: int` Output type: 0 = raw, 1 = PDF, 3 = PCL6, 4 = Postscript level 3, 5 = Postscript level 2. The value of 2 is deprecated and should not be used. * \[optional\] `reversefinisher: bool` Whether this printer has a finisher with reversed path (true/false) * \[optional\] `printerippurl: string` Printer IPP URL * \[optional\] `modelfamily: int` printer model family: if PrinterVendor is RICOH =\> 0 = "Ricoh SDK/J" ;1 -\> "Ricoh SOP" \| if PrinterVendor is XEROX =\> 0 = "WorkCentre"; 1 = "AltaLink"; 2 = "VersaLink" * \[optional\] `monochromeprinter: bool` Monochrome printer (true/false) * \[optional\] `ipreaderaddress: string` IP Reader address * \[optional\] `embeddedconfiguration: int` Id of Embedded configuration * \[optional\] `deviceserial: string` IP Reader address * \[optional\] `matchinginputport: bool` If true, a matching input port is automatically created (true/false) * \[optional\] `description: string` Port description * \[optional\] `softwareCopyCollation: bool` Use software copy collation instead of internal printer copy collation (true/false) * \[optional\] `sendusername: bool `Jobs printed on this output port contain usernames instead of anonymous (true/false) (IPP only) * \[optional\] `deviceAdminUsername : string`Machine credentials for the specific output port (overrides credentials specified in Embedded configuration if given) * \[optional\] `deviceAdminPassword : string`Machine credentials for the specific output port (overrides credentials specified in Embedded configuration if given) * Returns: `ErrorCodeInfoId` curl example: curl -X PATCH -i -H "X-Api-Key:" -k "https://account-domain-name:7300/api/v1/outputports/" -d domainname= -d portname= -d address= -d porttype= -d ipreaderaddress= -d deviceserial= -d reversefinisher= -d printerippurl= -d modelfamily= -d monochromeprinter= -d embeddedconfiguration= -d description= -d softwareCopyCollation= -d sendusername= Replace all with real values. ### Update output port - PUT This endpoint is being deprecated and will not be updated in future releases, please use PATCH update output port endpoint above. Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewOutputPort and ModifyOutputPort permissions. * Path: `/outputports` * Method: `PUT` * Parameters: * `id: int` Existing output port id * same parameters as for "Create output port - PUT" * Returns: `ErrorCodeInfoId` curl example: curl -X PUT -i -H "X-Api-Key:" -k "https://account-domain-name:7300/api/v1/outputports" -d domainname= -d portname= -d address= -d porttype= -d ipreaderaddress= -d deviceserial= -d reversefinisher= -d printerippurl= -d modelfamily= -d monochromeprinter= -d embeddedconfiguration= -d description= -d id= Replace all with real values. ### Move output port Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewOutputPort and ModifyOutputPort permissions. * Path: `/outputports//move` * Method: `PUT` * Parameters: * `outputportid: pathparam` Existing output port id * `domainname: string` Domain name of the parent account * `destinationdomainname: string` Specifies the domain name of the target account or container where the output port will be moved in the tree * Returns: `ErrorCodeInfoId` curl example: curl -X PUT -i -H "X-Api-Key:" -k "https://account-domain-name:7300/api/v1/outputports//move" -d domainname= -d destinationdomainname Replace all with real values. The output port can only be moved within the same parent account and cannot be transferred outside of its current account hierarchy. ### Delete output port Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewOutputPort and DeleteOutputPort permissions. * Path: `/outputports/` * Method: DELETE * Parameters: * `outputportid: pathparam` Id of the output port to delete * Returns: `ErrorCodeInfo` * Errors: 403 ## Input Ports ### Create input port Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewInputPort and CreateInputPort permissions. * Path: `/inputports` * Method: `PUT` * Parameters: * `domainname: string` Domain name of the parent account * `portname: string` Name of the port * `porttype: int` Port type: 0 = Pull queue, 1 = Push queue * \[optional\] `outputportid: int` Id of the mapped output port for push queue types * \[optional\] `portFlags: long` flags of the input port. Each bit from the long value represents a flag. Flags: AvailableByDefault: ...000001 (long value 1) -- enabled and ...000000 (long value 0) -- disabled. * \[optional\] `locationid: id` Id of the existing location to be assigned to the created input port * Returns: `ErrorCodeInfoId` curl example: curl -X PUT -H "X-Api-Key: advanced_api_permissions_key" -k "https://server_name:7300/api/v1/inputports" -d domainname= -d portname= -d porttype= -d outputportid= -d locationid= Replace all with real values. ### Update input port Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewInputPort and ModifyInputPort permissions. * Path: `/inputports` * Method: `PUT` * Parameters: * `id: int` Existing input port id * same parameters as for "Create input port" * Returns: `ErrorCodeInfoId` curl example: curl -X PUT -H "X-Api-Key: advanced_api_permissions_key" -k "https://server_name:7300/api/v1/inputports" -d domainname= -d portname= -d porttype= -d outputportid= -d locationid= -d id= Replace all with real values. ### Get list of input ports for user Permission info If you provide a user token, make sure the user for whom the token was issued has ViewInputPort permission. Does not require Advanced API permissions. * Path: `/inputports` * Method: `GET` * Parameters: * \[optional\] `providerid: int` The ID of the authentication provider for the given user. If not provided or zero, the server will attempt to guess it. * \[optional\] `username: string` name of the user for which the ports will be retrieved * \[optional\] `locationids: int` location id. This parameter can be specified more than once. * \[optional\] `enrichPorts: boolean` specify whether ports should include additional information, such as account, container and location id. Default: false * Returns: `list` * Errors: 403 ### Delete input port Permission info If you provide a user token, make sure the user for whom the token was issued has ViewInputPort and DeleteInputPort permissions. * Path: `/inputports/` * Method: DELETE * Parameters: * `inputportid: pathparam` Id of the input port to delete * Returns: `ErrorCodeInfo` * Errors: 403 ## Users ### Get user information Permission info If you provide a user token, make sure the user for whom the token was issued has ViewUser permission. * Path: `/users` * Method: `GET` * Parameters: * `username: string` Name of the user * `providerid` `: int` Identifier of the authentication provider to which the user belongs. * Returns: `UserInfo` * Errors: 403, 404 Curl example: curl -X GET -i -H X-Api-Key: -k https://account-domain-name:7300/api/v1/users?username=john.doe&providerid=3 ### Get all users of authentication provider Permission info If you provide a user token, make sure the user for whom the token was issued has ViewUser permission. * Path: `/users/all` * Method: `GET` * Parameters: * `providerid` `: int` Identifier of the authentication provider to which the user belongs. * \[optional\] `maxrecords: int` Maximum number of records on the single response page. The default value is 50, maximum is 1000. * \[optional\] `pagetoken: string` If the number of records for your query exceeds maxrecords value, the endpoint responds with exactly maxrecords number of users and non-empty nextPageToken field. Use value of nextPageToken as a pagetoken parameter to get the next page. * Returns: `List` * Errors: 403 Curl example: curl -X GET -i -H X-Api-Key: -k https://account-domain-name:7300/api/v1/users/all?providerid=3 curl -X GET -i -H X-Api-Key: -k https://account-domain-name:7300/api/v1/users/all?providerid=3&pagetoken=50&maxrecords=100 ### Create user Permission info If you provide a user token, make sure the user for whom the token was issued has ViewUser and CreateUser permissions. * Path: `/users` * Method: `PUT` * Parameters: * `username: string` Name of the user * \[optional\] `providerid` `: int` Identifier of the authentication provider under which the user will be created. If the providerid is not specified, the user will be created under a local provider. * \[optional\] `detailtype: int` Type of the user detail to add: 0=full name, 1=email, 2=homefolder, 3=password, 4=cardid, 5=shortid, 6=pin, 7=alias, 11=department, 12=expiration, 14=externalid * \[optional\] `detaildata: string` Detail data. `detailtype` and `detaildata` can be repeated multiple times * Returns: `ErrorCodeInfo` * Errors: 403 curl example: curl -X PUT -i -H X-Api-Key: -d username=john.doe -d detailtype=3 -d detaildata=password1 -d detailtype=1 -d detaildata=john.doe@cool.com -k https://account-domain-name:7300/api/v1/users curl -X PUT -i -H X-Api-Key: -d username=john.doe -d providerid=129 -d detailtype=3 -d detaildata=password1 -d detailtype=1 -d detaildata=john.doe@cool.com -k https://account-domain-name:7300/api/v1/users ### Delete user Permission info If you provide a user token, make sure the user for whom the token was issued has ViewUser and DeleteUser permissions. * Path: `/users/` * Method: DELETE * Parameters: * `username: pathparam` Name of the user to delete * \[optional query parameter\] `providerid` `: int` Identifier of the authentication provider of the user who will be deleted. Users with the same username but different authentication providers will not be deleted. If the providerid is not specified, the user with the given username will be deleted from the local provider. * Returns: `ErrorCodeInfo` * Errors: 403 curl example: curl -X DELETE -i -H X-Api-Key: -k https://account-domain-name:7300/api/v1/users/john.doe curl -X DELETE -i -H X-Api-Key: -k https://account-domain-name:7300/api/v1/users/john.doe?providerid=129 ### Update user details Permission info If you provide a user token, make sure the user for whom the token was issued has ViewUser, ModifyUser, GenerateShortID, GenerateOTP, and CardManagement permissions. GenerateShortID, GenerateOTP, or CardManagement permissions are required only when the Short ID, One time password, or Card number is updated. If you do not change any of these values, none of these permissions is required. * Path: `/users/` * Method: POST * Parameters: * `username: pathparam` Name of the user to update * \[optional\] `providerid` `: int` Identifier of the authentication provider where the user will be searched for. If the providerid is not specified, the user will be searched for in a local provider. * `detailtype: int` Type of the user detail to update: 0=full name, 1=email, 2=homefolder, 3=password, 4=cardid, 5=shortid, 6=pin, 7=alias, 11=department, 12=expiration, 14=externalid * \[optional\] `detaildata: string` Detail data. If not specified, the given detail is deleted from the user. An alias can be specified with "#PID" suffix where PID is a provider ID, for example: "user@domain.com#1234" * Note that this API call can update only one user detail. If multiple details are provided, only the first will be updated. * Returns: `ErrorCodeInfo` * Errors: 403 curl example: curl -X POST -i -H X-Api-Key: -d detailtype=3 -d detaildata=password1 -k https://account-domain-name:7300/api/v1/users/john.doe curl -X POST -i -H X-Api-Key: -d providerid=129 -d detailtype=3 -d detaildata=password1 -k https://account-domain-name:7300/api/v1/users/john.doe ### Import users from csv Permission info If you provide a user token, make sure the user for whom the token was issued has CreateUser and ModifyUser permissions. * Path: `/users/import` * Method: `POST` * Parameters: * `data: file` Csv file in format: username;firstname;lastname;mail;usergroup * `group: string` Name of the local group where the users will be imported * `mapping: string` Fields mapping in csv file (ex: userName:0,firstName:1,lastName:2,email:3,group:4) * \[optional\] `separator: string` Field separator in file (The default value is ',') * \[optional\] `hasheader: boolean` Check if the first row is a header inside the file (The default value is false) * \[optional\] `async: string` Check if you wish to wait for the synchronization to be finished (The default value is false) * Returns: `ErrorCodeInfo` * Errors: 400 curl example: curl -X POST -i -H X-Api-Key: --form-string "separator=;" -F "mapping=userName:0,firstName:1,lastName:2,email:3,group:4" -F "hasheader=false" -F "group=" -F"data=@" -k https://account-domain-name:7300/api/v1/users/import All imported users will be added to the group available in the request (-F "group=group_name") Only users part of the group sent in the request (-F "group=group_name") will be deactivated after the synchronization. ### Register card for user Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewUser, ModifyUser, and CardManagement permissions. Does not require Advanced API permissions. * Path: `/users//cards` * Method: POST * Parameters: * `username: pathparam` Name of the user to whom the card is registered * `cardid: string `The ID of the registered card * Returns: `ErrorCodeInfo` * Errors: 400, 403 curl -X POST -H "X-Api-Key: " -H "Authorization: " -k "https://:7300/api/v1/users//cards" -d cardid= ### Get list of groups for a given local user Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewUser permission. * Path: `/users/USERNAME/groups` * Method: `GET` * Parameters: * `USERNAME: pathparam` path parameter which contains local user name; specify user name (case insensitive) between two slashes in the path, e.g. for TestUser: `/users/testuser/groups` * Returns: `list` * Errors: 400 cURL example: curl -X GET -i -H "X-Api-Key: " -k "https://:7300/api/v1/users//groups" curl -X GET -i -H 'X-Api-Key:46405b18-8e1b-4db9-b930-bedd9ae839af' -k https://SAFEQ Cloudsafeq_cloudDispatcher Paragon Clouddipa_cloudCloudStreamcloudstreampmcpmc1.test.local:7300/api/v1/users/mytestuser/groups ### Add local user to a list of provided groups Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewUser and ModifyUser permissions. * Path: `/users/USERNAME/groups` * Method: `PUT` * Parameters: * `USERNAME: pathparam` path parameter which contains local user name; specify user name (case insensitive) between two slashes in the path, e.g. for TestUser: `/users/testuser/groups` * `groupid: string` one or more group IDs to which this user must be added. Each ID can be either a group primary key or a textual group ID. * Returns: `ErrorCodeInfo` * Errors: 400 cURL example: curl -X GET -i -H "X-Api-Key: " -k "https://:7300/api/v1/users//groups" -d groupid= ### Set local user membership to a list of provided groups Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewUser and ModifyUser permissions. * Path: `/users/USERNAME/groups` * Method: `POST` * Parameters: * `USERNAME: pathparam` path parameter which contains local user name; specify user name (case insensitive) between two slashes in the path, e.g. for TestUser: `/users/testuser/groups` * `groupid: string` zero or more group IDs, which will be set as user groups. The current groups will be removed from the user. Each ID can be either a group primary key or a textual group ID. If this parameter is not provided, all groups will be cleared. * Returns: `ErrorCodeInfo` * Errors: 400 ### Delete groups from user's membership Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewUser and ModifyUser permissions. * Path: `/users/USERNAME/groups` * Method: `DELETE` * Parameters: * `USERNAME: pathparam` path parameter which contains local user name; specify user name (case insensitive) between two slashes in the path, e.g. for TestUser: `/users/testuser/groups` * `groupid: string` one or more group IDs to delete from the user's membership. Each ID can be either a group primary key or a textual group ID. * Returns: `ErrorCodeInfo` * Errors: 400 cURL example: curl -X DELETE -i -H "X-Api-Key: " -k "https://:7300/api/v1/users//groups" -d groupid= ## Authentication provider ### Get authentication provider Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewAuthenticationProviders permission. * Path: `/authproviders` * Method: GET * Parameters: * `accountid=` The ID of PMC account domain * \[optional\] none * Returns: `AuthenticationProvidersInfo` * Errors: 400 * Can be called without X-Api-Key. In this case, it will only return providers without any client/web secrets Bash script example: #!/bin/sh ACCOUNT_INFO=`curl -X GET -H "X-Api-Key:" -k https://:7300/api/v1/account` echo "$ACCOUNT_INFO" ACCOUNT_INFO_SED=$(echo "$ACCOUNT_INFO" | sed -E 's/.*"id":\s*(\S+)(,|}|\s).*/\1/g') echo "$ACCOUNT_INFO_SED" ACCOUNT_ID=$(echo "$ACCOUNT_INFO_SED" | cut -f1 -d ',') echo "$ACCOUNT_ID" LDAP_AUTH=`curl -X GET -i -H "" -k https://:7300/api/v1/authproviders?accountid="$ACCOUNT_ID"` echo "$LDAP_AUTH" Replace all with real values. ### Add authentication provider Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewAuthenticationProviders and ModifyAuthenticationProviders permissions. * Path: `/authproviders` * Method: PUT * Parameters: * `-d ` parameters include: * \[name\] -- Name of authentication provider * \[providerType\] -- 0 (local)/1 (LDAP)/2 (Microsoft Entra ID)/3 (okta) * \[typeConfiguration\] -- authentication provider configuration details. For example, for local provider, it is `{}` * \[accountID\] -- The ID of PMC account domain * \[priority\] -- default value is 0 * \[active\] -- true (authentication provider is active) / false (authentication provider is inactive) * \[domainNames\] -- list of authorization provider domains * \[id\] -- defaults as 0 * \[optional\] none * Returns: `ResponseCodeInfo` * Errors: 400 Bash script example to add an LDAP authentication provider: #!/bin/sh ACCOUNT_INFO=`curl -X GET -H "X-Api-Key:" -k https://:7300/api/v1/account` echo "$ACCOUNT_INFO" ACCOUNT_INFO_SED=$(echo "$ACCOUNT_INFO" | sed -E 's/.*"id":\s*(\S+)(,|}|\s).*/\1/g') echo "$ACCOUNT_INFO_SED" ACCOUNT_ID=$(echo "$ACCOUNT_INFO_SED" | cut -f1 -d ',') echo "$ACCOUNT_ID" LDAP_AUTH=`curl -X PUT -i -H "X-Api-Key:" -k https://:7300/api/v1/authproviders -d '{"name":"","providerType":1,"typeConfiguration":"{\"baseDN\":\"\",\"groupBaseDN\":\"\",\"address\":\"\",\"port\":389,\"ssl\":true,\"userName\":\"\",\"password\":\"\",\"active\":true,\"bindType\":0,\"searchMode\":0,\"userNameAttr\":\"\",\"fullNameAttr\":\"\",\"emailAttr\":\"\",\"cardId1Attr\":\"\",\"cardId2Attr\":\"\",\"shortIdAttr\":\"\",\"aliasAttr\":\"\",\"homeFolderAttr\":\"\",\"userAttrClass\":\"\",\"groupAttrClass\":\"\",\"nonEmptyAttrs\":[\"\",\"\",\"\",\"\",\"\",\"\",\"\",\"\"]}","accountId":'"$ACCOUNT_ID"',"priority":0,"active":true,"domainNames":["acme.com"],"id":0}'` echo "$LDAP_AUTH" Replace all with real values. ### Delete authentication provider Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewAuthenticationProviders and DeleteAuthenticationProviders permissions. * Path: `/authproviders/` * Method: DELETE * Parameters: none * \[optional\] none * Returns: `ResponseCodeInfo` * Errors: 400 bash script example: #!/bin/sh LDAP_AUTH=`curl -X DELETE -i -v -H "" -k https://:7300/api/v1/authproviders/` echo "$LDAP_AUTH" Replace all with real values. ## Access controls ### Availability on secondary/gateway servers All access controls endpoints work on primary servers only. If you call these endpoints on secondary/gateway server, you will receive status code 400 Bad Request. ### Get access control details Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewAccessControls permission. * Path: `/accesscontrols` * Method: GET * Parameters: * `accountdomain=` DNS name of account domain * \[optional\] `permissionsdomain=` DNS name of the account's parent domain. By specifying this parameter, you will get access controls for the account domain, but defined at the parent domain level. * Returns: `AccessControlsInfo` * Errors: 400 bash script example: #!/bin/sh ACCESS_INFO=`curl -X GET -i -H "X-Api-Key:" -k https://:7300/api/v1/accesscontrols?accountdomain=` echo "$ACCESS_INFO" Replace all with real values. ### Add access control Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewAccessControls and CreateAccessControls permissions. * Path: `/accesscontrols` * Method: PUT * Parameters: * `accountdomain=` DNS name of account domain * `--data ` parameters include: * \[authProviderId\] -- ID of the authentication provider for which access control is being added. * \[roleName\] -- choose one based on scope -- Administrators/Users/Reporting/Support * \[userName\] -- use this parameter if assigning access control to the user directly (see note below) * \[groupName\] -- use this parameter if assigning access control to the group directly (see note below) * \[groupDn\] -- DN configuration of group/user * \[optional\] none * Returns: `ResponseCodeInfo` * Errors: 400 Note -- Depending on whether you are assigning access control to a user or a group, use "userName" or "groupName" parameter, but not both at the same time bash script example to add access control for an LDAP group as Administrators in PMC: #!/bin/sh ACCESS_INFO=`curl -X PUT -i -H "" -k https://:7300/api/v1/accesscontrols?accountdomain= --data '{"authProviderId":,"roleName":"Administrators","groupName":"","groupDn":""}'` echo "$ACCESS_INFO" Replace all with real values. ### Delete access control by id Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewAccessControls and DeleteAccessControls permissions. * Path: `/accesscontrols/*id*` * Method: DELETE * Parameters: * `accountdomain= ` DNS name of account domain * \[optional\] none * Returns: `ResponseCodeInfo` * Errors: 400 bash script example: #!/bin/sh ACCESS_INFO=`curl -X DELETE -i -H "" -k https://:7300/api/v1/accesscontrols/ACCESS_CONTROL_ID?accountdomain=` echo "$ACCESS_INFO" Replace all with real values. Warning Delete ACL can trigger resorting of ACL IDs. Before every DELETE operation call GET operation to check what is current ACL ID. Never call two DELETE operations because ID can change after the first DELETE. operation ## Locations ### Get list of locations Permission info If you provide a user token, make sure the user for whom the token was issued has ViewLocations permission. Does not require Advanced API permissions. * Path: `/locations` * Method: `GET` * Parameters: * `locationtype: int` location type. This parameter can be specified more than once. Recognized types: 1 = gateway IPv4 address, 2 = IPv4 subnet, 3 = IPv4 range, 4 = WiFi SSID. * `locationdata: string` location search data. This parameter can be specified more than once and must correspond to the location type. The subnet is specified in the format "192.168.1.100/24", IP range is specified in the format "192.168.1.100-192.168.1.200". * Returns: `list` * Errors: 400 #!/bin/sh ACCESS_INFO=`curl -X GET -i -H "X-Api-Key:" -k "https://:7300/api/v1/locations?locationtype=1&locationdata=192.168.1.100"` echo "$ACCESS_INFO" Replace all with real values. ### Get location by id Permission info If you provide a user token, make sure the user for whom the token was issued has ViewLocations permission. Does not require Advanced API permissions. * Path: `/locations` * Method: `GET` * Parameters: * `locationId=` The location ID * Returns: `LocationInfo` * Errors: 404 #!/bin/sh ACCESS_INFO=`curl -X GET -i -H "X-Api-Key:" -k "https://:7300/api/v1/locations/"` echo "$ACCESS_INFO" Replace all with real values. ### Create location Permission info If you provide a user token, make sure the user for whom the token was issued has ViewLocations and CreateLocations permissions. * Path: `/locations` * Method: `POST` * Parameters: `LocationInfo` as JSON payload, except `id` property -- skip it * Returns: `ErrorCodeInfoId` , `id` property will contain a newly generated location identifier * Errors: 400, 403 curl -X POST -H "X-Api-Key: advanced_api_permissions_key" -k "https://serveraddress:7300/api/v1/locations" --data-binary @- << EOF { "name": "Location name", "identifiers": [ { "locationType": 1, "stringData": [ "192.168.1.100" ] } ] } EOF ### Update existing location by id Permission info If you provide a user token, make sure the user for whom the token was issued has ViewLocations and ModifyLocations permissions. * Path: `/locations/*id*` * Method: `PUT` * Parameters: `LocationInfo` as JSON payload * Returns: `LocationInfo` * Errors: 400, 403, 404 curl -X PUT -H "X-Api-Key: advanced_api_permissions_key" -k "https://serveraddress:7300/api/v1/locations/LOCATION_ID" --data-binary @- << EOF { "name": "Location name", "identifiers": [ { "locationType": 1, "stringData": [ "192.168.1.100" ] } ] } EOF Replace `LOCATION_ID` with real value. ### Delete location by id Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewLocations and DeleteLocations permissions. * Path: `/locations/*id*` * Method: `DELETE` * Parameters: None * Returns: `ErrorCodeInfoId` * Errors: 403, 404 curl -X DELETE -H "X-Api-Key: advanced_api_permissions_key" -k "https://serveraddress:7300/api/v1/locations/LOCATION_ID" Replace `LOCATION_ID` with real value. ## Card reader ### Release all jobs using the card reader Permission info Does not require Advanced API permissions. Path: `/card` * Method: `GET`, `POST` * Parameters: * `cd: string` required user card reader ID * `Mac: string` required printer IP card reader address * Returns: 200 Success * Errors: 400 * Notes: For `POST` method, the parameters must be sent as query parameters, not body parameters. cURL example: curl -X GET -i -v -H "X-Api-Key: " -k "https://:7300/api/v1/card/?cd=&amp;Mac=" ## Groups ### Get list of local groups Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewUser permission. * Path: `/groups` * Method: `GET` * Parameters: * Returns: `list` cURL example: curl -X GET -i -H "X-Api-Key: " -k "https://:7300/api/v1/groups" ### Create local user group Permission info If you provide a user token, make sure the user for whom the token was issued has ViewUser and CreateUser permissions. * Path: `/groups` * Method: `PUT` * Parameters: * `groupname: string` required local group name * `groupdn` optional group ID. If omitted, a unique group ID will be generated. * Returns: `ErrorCodeInfo` which contains a new group ID * Errors: 400 cURL example: curl -X PUT -i -H "X-Api-Key: " -k "https://:7300/api/v1/groups" -d groupname= -d groupdn= ### Delete local user group Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewUser and DeleteUser permissions. * Path: `/groups/` * Method: `DELETE` * Parameters: * `GROUPID: pathparam` path parameter which indicates either group primary key (integer) or group ID (string) * Returns: `ErrorCodeInfo` cURL example: curl -X DELETE -i -v -H "X-Api-Key: " -k "https://:7300/api/v1/groups/" ### Get info about group Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewUser permission. * Path: /groups/`GROUPID` * Method: `GET` * Parameters: * `GROUPID: pathparam` path parameter which indicates either group primary key (integer) or group ID (string) * Returns: `GroupInfo` * Errors: 404 cURL example: curl -X GET -i -H "X-Api-Key: " -k "https://:7300/api/v1/groups/GROUPID" ### Get members of a group Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewUser permissions. * Path: /groups/`GROUPID`/members * Method: `GET` * Parameters: * `GROUPID: pathparam` path parameter which indicates either group primary key (integer) or group ID (string) * Returns: `List` * Errors: 404 cURL example: curl -X GET -i -H "X-Api-Key: " -k "https://:7300/api/v1/groups/GROUPID/members" ## Terminal config ### Create terminal configuration Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewTerminalConfig and CreateTerminalConfig permissions. * Path: `/terminalconfig` * Method: `POST` * Parameters: * `domain: string` required account domain where to add the configuration * `name: string` required configuration name * `vendor: string` required printer vendor (ex: km, hp, xerox ....) * `adminuser: string` optional admin username. If omitted, empty is the default * `adminpassword: string` optional admin password. If omitted, empty is the default * `applicationtype: int` optional application type (ex: 0:Other, 1:Open_API, 2: IWS, 3: Workpath). If omitted, OTHER is the default * `devices: int` optional list of mapped output port IDs. Can be repeated multiple times * Returns: `ErrorCodeInfo` which contains the new terminal config ID * Errors: 400 cURL example: curl -X POST -i -H "X-Api-Key: " -k "https://:7300/api/v1/terminalconfig" -d domain= -d name= -d vendor= -d adminuser= -d adminpassword= -d applicationtype= -d devices= ### Get terminal configuration Permission info Does not require Advanced API permissions. Authorization with a device token or allowing untrusted endpoints is required . This feature is only available for the Ricoh Standard Embedded Terminal. * Path: `/terminalconfig` * Method: `GET` * Parameters: * `serialnumber: string` required serial number (device serial) of the printer * Returns: `TerminalConfig` * Errors: 400, 403, 404 cURL example: curl -X GET -i -H "X-Api-Key: " "https://:7300/api/v1/terminalconfig?serialnumber=" curl -X GET -i -H "X-Api-Key: " -H "Authorization: " "https://:7300/api/v1/terminalconfig?serialnumber=" ## Token Permission info Does not require Advanced API permissions. This function is deprecated and will be removed in future versions. Use the **/oauth/v1/token** endpoint to refresh both user and device tokens. See the [Refresh device or user token](https://docs.ricoh-pmc.com/api/latest/pmc/refresh-device-or-user-token.md) chapter for more information. ### Refresh user token * Path: `/token` * Method: `GET` * Parameters: * `refresh_token: string` a refresh token acquired in the login call * Returns: `TokenInfo` * Errors: 400, 403 A given refresh token can only be used once. The next call to a refresh function should be done with a new refresh token. cURL example: curl -i -H "X-Api-Key: xxx" -k "https://serveraddress:7300/api/v1/token?refresh_token=yyy" ## Scan Connectors Note This feature is currently hidden by default and may not be available for your account. ### Get scan connector Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewScanWorkflow permission. * Path: `/scan/connectors/` * Method: `GET` * Parameters: * `scanConnectorId: int` Id of the connector * Returns: `ScanConnectorInfo` * Errors: 403, 404 curl -X GET -i -H "X-Api-Key: " -k "https://:7300/api/v1/scan/connectors/" ### Get all scan connectors Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewScanWorkflow permission. * Path: `/scan/connectors` * Method: `GET` * Returns: `list` * Errors: 403, 404 curl -X GET -i -H "X-Api-Key: " -k "https://:7300/api/v1/scan/connectors" ### Update scan connector Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewScanWorkflow and ModifyScanWorkflow permissions. * Path: `/scan/connectors/` * Method: `PUT` * Parameters: * `scanConnectorId: int` Id of the connector * `scanConnector: ScanConnectorInfo` - see [Data structures](https://docs.ricoh-pmc.com/api/latest/pmc/data-structures.md). * Returns: `ScanConnectorInfo` * Errors: 403, 404 curl -X PUT -i -H "X-Api-Key: " -k "https://:7300/api/v1/scan/connectors/" --data "{\"name\":\"Connector\", \"connectorType\":\"EMAIL\"}" ### Create scan connector Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewScanWorkflow and CreateScanWorkflow permissions. * Path: `/scan/connectors` * Method: `POST` * Parameters: * `scanConnector: ScanConnectorInfo` - see [Data structures](https://docs.ricoh-pmc.com/api/latest/pmc/data-structures.md). * Returns: `ScanConnectorInfo` * Errors: 403, 404 curl -X POST -i -H "X-Api-Key: " -k "https://:7300/api/v1/scan/connectors" --data "{\"name\":\"Connector\", \"connectorType\":\"EMAIL\"}" ### Delete scan connector Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewScanWorkflow and DeleteScanWorkflow permissions. * Path: `/scan/connectors/` * Method: `DELETE` * Parameters: * `scanConnectorId: int` Id of the connector * Returns: 204 * Errors: 403, 404 curl -X DELETE -i -H "X-Api-Key: " -k "https://:7300/api/v1/scan/connectors/" ## Scan Workflows Note This feature is currently hidden by default and may not be available for your account. ### Get scan workflow Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewScanWorkflow permission. * Path: `/scan/workflows/` * Method: `GET` * Parameters: * `scanWorkflowId: int` Id of the workflow * Returns: `ScanWorkflowTemplateInfo` * Errors: 403, 404 curl -X GET -i -H "X-Api-Key: " -k "https://:7300/api/v1/scan/workflows/" ### Get all scan workflows Permission info If you provide a user token, make sure the user for whom the token was issued has ViewScanWorkflow permission. * Path: `/scan/workflows` * Method: `GET` * Returns: `list` * Errors: 403, 404 curl -X GET -i -H "X-Api-Key: " -k "https://:7300/api/v1/scan/workflows" ### Update scan workflow Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewScanWorkflow and ModifyScanWorkflow permissions. * Path: `/scan/workflows/` * Method: `PUT` * Parameters: * `scanWorkflowId: int` Id of the workflow * `scanWorkflow: ScanWorkflowTemplateInfo` - see [Data structures](https://docs.ricoh-pmc.com/api/latest/pmc/data-structures.md). * Returns: `ScanWorkflowTemplateInfo` * Errors: 403, 404 curl -X PUT -i -H "X-Api-Key: " -k "https://:7300/api/v1/scan/workflows/" --data "{\"name\":\"Workflow\", \"connectorId\":}" ### Create scan workflows Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewScanWorkflow and CreateScanWorkflow permissions. * Path: `/scan/workflows` * Method: `POST` * Parameters: * `scanWorkflow: ScanWorkflowTemplateInfo` - see [Data structures](https://docs.ricoh-pmc.com/api/latest/pmc/data-structures.md). * Returns: `ScanWorkflowTemplateInfo` * Errors: 403, 404 curl -X POST -i -H "X-Api-Key: " -k "https://:7300/api/v1/scan/workflows" --data "{\"name\":\"Workflow\", \"connectorId\":}" ### Delete scan workflow Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewScanWorkflow and DeleteScanWorkflow permissions. * Path: `/scan/workflows/` * Method: `DELETE` * Parameters: * `scanWorkflowId: int` Id of the workflow * Returns: 204 * Errors: 403, 404 curl -X DELETE -i -H "X-Api-Key: " -k "https://:7300/api/v1/scan/workflows/" ## Scan Workflow Access Note This feature is currently hidden by default and may not be available for your account. ### Get scan workflow access Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewScanWorkflowAccessRule permission. * Path: `/scan/access/` * Method: `GET` * Parameters: * `accessId: int` Id of the workflow access * Returns: `ScanWorkflowAccessInfo` * Errors: 403, 404 curl -X GET -i -H "X-Api-Key: " -k "https://:7300/api/v1/scan/access/" ### Get all scan workflow accesses Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewScanWorkflowAccessRule permission. * Path: `/scan/access` * Method: `GET` * Returns: `list` * Errors: 403, 404 curl -X GET -i -H "X-Api-Key: " -k "https://:7300/api/v1/scan/access" ### Update scan workflow access Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewScanWorkflowAccessRule and ModifyScanWorkflowAccessRule permissions. * Path: `/scan/access/` * Method: `PUT` * Parameters: * `accessId: int` Id of the workflow access * `accessInfo: ScanWorkflowAccessInfo` - see [Data structures](https://docs.ricoh-pmc.com/api/latest/pmc/data-structures.md). * Returns: `ScanWorkflowAccessInfo` * Errors: 403, 404 curl -X PUT -i -H "X-Api-Key: " -k "https://:7300/api/v1/scan/access/" --data "{\"workflowId\":100, \"identityId\":2, \"identityType\":\"Group\"}" ### Create scan workflow access Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewScanWorkflowAccessRule and CreateScanWorkflowAccessRule permissions. * Path: `/scan/access` * Method: `POST` * Parameters: * `accessInfo: ScanWorkflowAccessInfo` - see [Data structures](https://docs.ricoh-pmc.com/api/latest/pmc/data-structures.md). * Returns: `ScanWorkflowAccessInfo` * Errors: 403, 404 curl -X POST -i -H "X-Api-Key: " -k "https://:7300/api/v1/scan/access" --data "{\"workflowId\":1, \"identityId\":2, \"identityType\":\"User\"}" ### Delete scan workflow access Permission info If you provide a user token, make sure the user for whom the token was issued has the ViewScanWorkflowAccessRule and DeleteScanWorkflowAccessRule permissions. * Path: `/scan/access/` * Method: `DELETE` * Parameters: * `accessId: int` Id of the workflow access * Returns: 204 * Errors: 403, 404 curl -X DELETE -i -H "X-Api-Key: " -k "https://:7300/api/v1/scan/access/" ## Certificates This API is not available on gateways. ### Import a CA certificate A ModifyCertificatepermission is needed for this operation. * Path: `/certificate/ca` * Method: `POST` * Body: "application/octet-stream" of PEM/DER file * Returns: 200 and CertificateInfo structure which contains * `alias` * `serial` * `subject` * `issuer` * `notBefore` * `notAfter` * `body `(public part of the certificate) * Errors: 400 curl -X POST -k -i -H X-Api-Key:$API_KEY -H Content-Type:application/octet-stream --data-binary "@cacert.pem" https://:7300/api/v1/certificate/ca ### Import private certificate chain A ModifyCertificatepermission is needed for this operation. * Path: `/certificate/chain` * Method: `POST` * Body: "multipart/form-data" with two parts: * "`password`" part, which contains a keystore password (string) * "`data`" part, which contains binary stream of P12/PFX file * Returns: 200 and list of `CertificateInfo `structure which contains * `alias` * `serial` * `subject` * `issuer` * `notBefore` * `notAfter` * `body `(public part of the certificate) * Errors: 400 curl -X POST -k -i -H X-Api-Key:$API_KEY -F data="@chain.p12" -F password=changeit https://:7300/api/v1/certificate/chain ### Get a CA certificate A ViewCertificatepermission is needed for this operation. * Path: `/certificate/ca` * Method: `GET` * Optional query parameters (you can combine them): * `subject `(could be a substring) * `serial `(bigint) * `alias `(string) * `issuer `(string) * `expiresin `(int - number of days) * Returns: 200 and list of `CertificateInfo `structure which contains * `alias` * `serial` * `subject` * `issuer` * `notBefore` * `notAfter` * `body `(public part of the certificate) * Errors: 400 curl -k -i -H X-Api-Key:$API_KEY https://:7300/api/v1/certificate/ca?serial=828286999265050717 ### Get private certificate chain A ViewCertificatepermission is needed for this operation. * Path: `/certificate/chain` * Method: `GET` * Optional query parameters (you can combine them): * `subject `(could be a substring) * `serial `(bigint) * `alias `(string) * `issuer `(string) * `expiresin `(int - number of days) * Returns: 200 and list of `CertificateInfo `structure which contains * `alias` * `serial` * `subject` * `issuer` * `notBefore` * `notAfter` * `body `(public part of the certificate) * Errors: 400 curl -k -i -H X-Api-Key:$API_KEY https://:7300/api/v1/certificate/chain?subject=CA ### Delete a CA certificate A DeleteCertificatepermission is needed for this operation. * Path: `/certificate/ca/` * Method: `DELETE` * Mandatory path parameter: * `alias` * Returns: 200 * Error codes: 1130, 1134 curl -X DELETE -k -i -H X-Api-Key:$API_KEY https://:7300/api/v1/certificate/ca/imported-aeba53f2-78cf-4fad-b134-d61c5e940cdc ### Delete private certificate chain A DeleteCertificatepermission is needed for this operation. * Path: `/certificate/chain/` * Method: `DELETE` * Mandatory path parameter: * `alias` * Returns: 200 * Error codes: 1131, 1135 curl -X DELETE -k -i -H X-Api-Key:$API_KEY https://:7300/api/v1/certificate/chain/7c9c05e5-2622-4c9d-9f76-2c11a6d24846 ### Get root authorities This endpoint returns root authorities only for self-signed certificates that were created using the "Create..." (Private certificate chains) button. Custom (external) chains that were imported will be ignored. The signing certificates are also ignored. * Path: `/certificate/root` * Method: `GET` * Returns: 200 and list of `CertificateInfo `structure which contains * `alias` * `serial` * `subject` * `issuer` * `notBefore` * `notAfter` * `body `(public part of the certificate encoded as base64 DER) curl -k -i -H X-Api-Key:$API_KEY https://:7300/api/v1/certificate/root ## Audit logs ### Get audit logs A ViewLogpermission is needed for this operation. * Path: `/logs/auditlogs` * Method: `GET` * Parameters: * `datefrom: datetime` ISO-8601 instant formatted start point for Audit logs range. Example: 2025-12-05T16:38:10.972Z * `dateto: datetime` ISO-8601 instant formatted endpoint for Audit logs range. Example: 2026-01-05T10:25:12.834Z * \[optional\] `maxRecords: int` The number of records to be retrieved. If not provided, 1000 is the default value. Value must be between 1 and 10000, inclusive. * \[optional\] `filter: string` Audit logs text filter. For more details see Audit logs documentation. * Returns: `List` * Error Codes: 403, 400 curl -X GET -i -k -H "Content-Type: application/json" -H "X-Api-Key: API_KEY_VALUE" "https://:7300/api/v1/logs/auditlogs?datefrom=2025-06-25T06%3A15%3A00.000Z&dateto=2026-01-10T08%3A30%3A00.000Z&maxrecords=5000&filter=api" ## Endpoints ### Get endpoint by Id A ViewEndpoint permission is needed for this operation. * Path: `/endpoints/` * Method: `GET` * Method path parameter: * `endpointId` * Returns: `EndpointInfo` * Error: 403, 400 curl -X GET -i -H "X-Api-Key: API_KEY_VALUE" -H "Content-Type: application/json" "https://serveraddress:7300/api/v1/endpoints/ENDPOINT_ID" ### Get all endpoints A ViewEndpoint permission is needed for this operation. * Path: `/endpoints` * Method: `GET` * Method query parameters: * `withVersion` - if set to `true`, returns only endpoints with associated version number, such as gateways and PC clients in local storage mode. * \[optional\] `maxrecords: int` Maximum number of records on the single response page. The default value is 50, maximum is 2000. * \[optional\] `pagetoken: string` If the number or records for your query exceeds `maxrecords` value, the endpoint responds with exactly `maxrecords` and non-empty `nextPageToken` field. Use value of `nextPageToken` as a `pagetoken` parameter to get the next page. * Returns: `PagedResult` with the following fields: * `nextPageToken` - non-empty if there are more items available than returned * `recordsOnPage` - number of records returned for the page * `items` - list of `EndpointInfo` objects * Error: 403, 400 curl -X GET -i -H "X-Api-Key: API_KEY_VALUE" -H "Content-Type: application/json" "https://serveraddress:7300/api/v1/endpoints?withVersion=true" ## Balance ### Get balance configuration A ViewUserBalance permission is needed for this operation. * Path: `/balance/config` * Method: `GET` * Returns: `BalanceConfigInfo` (the per-account enable switch and the price list) * Errors: 403, 405 curl -X GET -i -H "X-Api-Key: " -k "https://:7300/api/v1/balance/config" ### Update balance configuration A ModifyBalancePricing permission is needed for this operation. * Path: `/balance/config` * Method: `PUT` * Body (JSON): `BalanceConfigData` --- all fields required, prices must be zero or greater * Returns: the updated `BalanceConfigInfo` * Errors: 400, 403, 405 curl -X PUT -i -H "X-Api-Key: " -k "https://:7300/api/v1/balance/config" --data "{\"enabled\":true, \"bwNormalPage\":1, \"bwLargePage\":2, \"colorNormalPage\":3, \"colorLargePage\":6}" ### Get user balance A ViewUserBalance permission is needed for this operation. * Path: `/balance` * Method: `GET` * Parameters: * `username: string` Name of the user * `providerid: int` Identifier of the authentication provider where the user belongs. * Returns: `UserBalanceInfo` (users without a balance record report zero balances) * Errors: 403, 404, 405 curl -X GET -i -H "X-Api-Key: " -k "https://:7300/api/v1/balance?username=&providerid=" ### Get user balance transactions A ViewUserBalance permission is needed for this operation. * Path: `/balance/transactions` * Method: `GET` * Parameters: * `username: string` Name of the user * `providerid: int` Identifier of the authentication provider where the user belongs. * \[optional\] `maxrecords: int` Maximum number of transactions per page, between 1 and 1000. Default 50. * \[optional\] `pagetoken: string` Token of the page to fetch, taken from `nextPageToken` of the previous page. * \[optional\] `datefrom: string` Only include transactions at or after this timestamp (ISO-8601 with offset, e.g. `2026-07-01T00:00:00Z`). * \[optional\] `dateto: string` Only include transactions at or before this timestamp (ISO-8601 with offset). * Returns: `PagedResult`, most recent transactions first * Errors: 400, 403, 404, 405 curl -X GET -i -H "X-Api-Key: " -k "https://:7300/api/v1/balance/transactions?username=&providerid=&maxrecords=50" ### Create balance transaction (add / remove / set) A ModifyUserBalance permission is needed for this operation. * Path: `/balance/transactions` * Method: `POST` * Body (JSON): `BalanceTransactionData` --- `add` adds the amount to the selected balance; `remove` subtracts it (the balance never goes below zero, an uncovered removal fails with 400); `set` sets the quota balance to the given target value unconditionally (wallet is not supported for `set`) and is independent of the policy-driven scheduled resets * Returns: the created `BalanceTransactionInfo`, including the balances after the operation * Errors: 400, 403, 404, 405 curl -X POST -i -H "X-Api-Key: " -k "https://:7300/api/v1/balance/transactions" --data "{\"userName\":\"\", \"providerId\":1, \"operation\":\"add\", \"balanceType\":\"quota\", \"amount\":10}" ### Check user balance for a document * Path: `/balance/check` * Method: `POST` * Body (JSON): `BalanceCheckData` * Returns: `BalanceCheckInfo` * Errors: 403 curl -X POST -i -H "X-Api-Key: " -k "https://:7300/api/v1/balance/check" --data "{\"uuid\":\"\", \"userName\":\"\", \"providerId\":1, \"totalPages\":10, \"colorPages\":2, \"paperSize\":\"A4\", \"copies\":1}" ### Get balance policies A ViewUserBalance permission is needed for this operation. * Path: `/balance/policies` * Method: `GET` * Returns: `list` ordered by priority with the default policy pinned last. When no default policy has been persisted yet, a virtual default (`id = 0`, type `free`) is included. Each policy carries its reset `schedule` when one exists. * Errors: 403, 405 curl -X GET -i -H "X-Api-Key: " -k "https://:7300/api/v1/balance/policies" ### Get balance policy A ViewUserBalance permission is needed for this operation. * Path: `/balance/policies/` * Method: `GET` * Returns: `BalancePolicyInfo` * Errors: 403, 404, 405 curl -X GET -i -H "X-Api-Key: " -k "https://:7300/api/v1/balance/policies/" ### Get default balance policy A ViewUserBalance permission is needed for this operation. * Path: `/balance/policies/default` * Method: `GET` * Returns: `BalancePolicyInfo` (the virtual default when not persisted yet) * Errors: 403, 405 curl -X GET -i -H "X-Api-Key: " -k "https://:7300/api/v1/balance/policies/default" ### Create balance policy A ModifyUserBalance permission is needed for this operation. * Path: `/balance/policies` * Method: `POST` * Body (JSON): `BalancePolicyData` --- the priority is assigned automatically (after all existing non-default policies). An enabled `schedule` block creates the policy's reset schedule as well. * Returns: the created `BalancePolicyInfo` * Errors: 400, 403, 405 curl -X POST -i -H "X-Api-Key: " -k "https://:7300/api/v1/balance/policies" --data "{\"policyName\":\"Policy\", \"balanceType\":\"quota\", \"initialBalance\":100, \"groupIds\":[1,2]}" ### Update balance policy A ModifyUserBalance permission is needed for this operation. * Path: `/balance/policies/` * Method: `PUT` * Body (JSON): `BalancePolicyData` --- priority is preserved; when the target is the default policy, `groupIds` must be empty (400 otherwise). The `schedule` block: absent = leave the reset schedule unchanged, `enabled = false` = remove it, `enabled = true` = create or replace it. * Returns: the updated `BalancePolicyInfo` * Errors: 400, 403, 404, 405 curl -X PUT -i -H "X-Api-Key: " -k "https://:7300/api/v1/balance/policies/" --data "{\"policyName\":\"Policy\", \"balanceType\":\"quota\", \"initialBalance\":100, \"groupIds\":[1,2]}" ### Update default balance policy A ModifyUserBalance permission is needed for this operation. * Path: `/balance/policies/default` * Method: `PUT` * Body (JSON): `BalancePolicyData` --- `groupIds` must be empty (the default applies to all users). The first update persists the virtual default. The `schedule` block behaves as in "Update balance policy". * Returns: the updated `BalancePolicyInfo` * Errors: 400, 403, 405 curl -X PUT -i -H "X-Api-Key: " -k "https://:7300/api/v1/balance/policies/default" --data "{\"policyName\":\"Default\", \"balanceType\":\"free\", \"initialBalance\":0, \"groupIds\":[]}" ### Delete balance policy A ModifyUserBalance permission is needed for this operation. The default balance policy cannot be deleted. * Path: `/balance/policies/` * Method: `DELETE` * Returns: 204 No Content * Errors: 400 (default policy), 403, 404, 405 curl -X DELETE -i -H "X-Api-Key: " -k "https://:7300/api/v1/balance/policies/" ### Reorder balance policies A ModifyUserBalance permission is needed for this operation. * Path: `/balance/policies/order` * Method: `PUT` * Body (JSON): `BalancePolicyOrderData` --- must contain exactly all non-default policy ids; priorities are reassigned 1..n in list order (lower number = higher precedence) * Returns: `list` in the new order * Errors: 400, 403, 405 curl -X PUT -i -H "X-Api-Key: " -k "https://:7300/api/v1/balance/policies/order" --data "{\"orderedPolicyIds\":[3,1,2]}" --- version: "2026.08.20" variant: "PMC" language: "en" --- # Authorization code flow This feature is supported on primary servers only. The authorization code flow is a method by which an OAuth client obtains access and refresh tokens. The access token allows access to resources based on the user's permissions, while the refresh token enables an application to maintain a valid session without requiring user action. This implementation utilizes the default API key. The implementation adheres to the specifications outlined in [The OAuth 2.1 Authorization Framework](https://datatracker.ietf.org/doc/html/draft-ietf-oauth-v2-1-09). The well-known configuration is, by default, available on port 7400. The path is `/oauth/v1/.well-known/openid-configuration`. Error responses from the OAuth 2.1 specification are expanded with the **x_error_code** field, which includes an implementation-specific error code: { "error": "error_code", "error_description": "textual error description" "x_error_code": "more detailed error_code, specific to this OAuth implementation" } --- version: "2026.08.20" variant: "PMC" language: "en" --- # Data structures ## ServerVersionInfo version: string buildDate: string buildTimeStamp: long ### ErrorCodeInfo errorCode: integer current codes: 0 OK 1000 not implemented 1001 output document error 1002 delete document error 1003 create user error 1004 delete user error 1005 enroll card error 1006 account not found 1007 object tree error 1008 create account error 1009 create output port error 1010 create trigger error 1011 delete trigger error 1012 run automation error 1013 update user error 1014 register server error 1015 create input port error 1016 delete input port error 1017 delete output port error 1030 delete authentication provider error 1031 save authentication provider error 1032 no services for authentication provider error 1040 save access control error 1041 delete access control error 1042 output not ready error 1043 create group error 1044 delete group error 1050 license count exceeded 1051 license expired 1060 import users error 1070 create terminal configuration error 1080 delete account error 1090 update account error 10000 unknown error ### ErrorCodeInfoId errorCode: integer id: integer current codes: same as for ErrorCodeInfo ### UserInfo id: int providerId: int accountId: int userName: string fullName: string email: string department: string shortId: string cards: list of strings createdDate: string // in ISO-8601 format token: TokenInfo // optional, may be null isExpired: boolean // optional, may be null, this field is filled only for users belonging to authentication providers of type Client. groupIds: list of int ### TokenInfo access_token: string refresh_token: string expires_in: int ### DocumentInfo uuid: string documentName: string documentType: int userName: string totalPages: int colorPages: int duplex: int copies: int grayscale: boolean paperSize: string dateTime: long storageOnline: boolean secure: boolean tags: list of TagInfo collate: boolean status: int (0 => READY,1 => PRINTED, 2 => DELETED, 3 => EXPIRED, 4 => FAILED, 5 => RECEIVED, 6 => AWAITING_CONVERSION, 7 => CONVERTING, 8 => CONVERSION_FAILED, 9 => STORED) outputPortId: int outputPortName: string jobType: string (PRINT, COPY, SCAN, FAX) ### Document Status Flowchart ![DocumentStatusFlowchart.svg](https://docs.ricoh-pmc.com/__attachments/a_173221a5ccc6d5d2abf7c8bb35246391d1debc7920a064e50d21a219833acc6f/DocumentStatusFlowchart.svg?cb=b0bd5ec6424b4fe5c75eadec22ac91c6) ### OutputPortInfo id: int name: string address: string portType: int vendor: string logoutTimeout: int autoRelease: boolean embedded: boolean monochrome: boolean trimCardId: boolean description: string embeddedConfigurationId: int printProtocol: int modelFamily: int outputType: int services: { string: [int, int, ...], ... } deviceSerial: string properties: { string: string, ... } containerName: string, accountId: int, parentAccountOrContainerId: int, decimalFormatForCardIds: boolean, isReverseFinisher: boolean, printerIppUrl: string, ipReaderAddress: string, softwareCopyCollation: boolean, sendUsername: boolean, registrationSource: string, // "manual", "autodiscovery" terminalInfo: { deployStatus (optional, may be null): { stage: int (0 => NOT_INSTALLED, 1 => INSTALLED, 2 => INSTALLING, 3 => UNINSTALLING, 4 => CONFIGURING, 5 => CONFIGURED, 6 => FAILED, 7 => CLOUD_UNKNOWN, 8 => CLOUD_CONFIGURED), message: string, lastDate: string }, terminalStatus (optional, may be null): { terminalVersion: string, installationSource: int (0 => UNKNOWN, 1 => MANUAL, 2 => KM_MARKETPLACE, 3 => RICOH_APPLICATION_SITE, 4 => HP_COMMAND_CENTER), cardReaderData: string, modelName: string, additionalModelInfo: string, firmwareVersion: string, status: int (0 => UNKNOWN, 1 => OK, 2 => WARNING, 3 => ERROR), statusMessage: string, errorData: string, modifiedDate: string } } ### InputPortInfo id: int name: string portType: int outputPort: string (optional, may be null) locationId: int (optional, may be null) containerName: string (optional, may be null) ### AccountInfo id: int name: string accountType: int (1=vendor, 2=customer, 3=container) domainNames: list of strings uuid: string timezone: string (optional, may be null) ### ContainerInfo id: int name: string domainNames: list of strings timezone: string (optional, may be null) ### LocationInfo id: int name: string sortOrder: int identifiers: list of LocationIdentifierSearch ### LocationIdentifierSearch locationType: LocationType (GATEWAY_IP, SUBNET, IP_RANGE, WIFI_SSID) searchValue: string ### GroupInfo id: int groupName: string groupDN: string ### TerminalConfig "services": { "scanToMe": { "serviceId": "SCANTOMAIL", "enabled": boolean, "instanceIndex": 1, "smtp": { "server": string, "port": int, "security": { "mode": string, ("none", "tls", "start_tls") "disableCertificateCheck": boolean }, "user": string, "password": string, "senderEmail": string, "disableUserAuthentication": boolean } }, "print": { "serviceId": "PRINT", "enabled": boolean, "instanceIndex": 1 }, "printShortcut": { "serviceId": "SHPMCPRINT", "enabled": boolean }, "sho365Shortcut": { "serviceId": "SHO365", "enabled": boolean, "tenant": { "tenantId": string, "clientId": string } }, "copyShortcut": { "serviceId": "STANDARDCOPY", "enabled": boolean }, "standardScanShortcut": { "serviceId": "STANDARDSCAN", "enabled": boolean }, "standardFaxShortcut": { "serviceId": "STANDARDFAX", "enabled": boolean } }, "authentication-way": { "oneTimePasswordEnrollment": boolean, "cardOnlyAuthentication": boolean, "shortIdAuthentication": boolean, "developerLogEnabled": boolean } ### ScanConnectorInfo "id": int, "name": string, // max length 100 "description": string, // optional, max length 300 "connectorType": string, // EMAIL, ONEDRIVE_BUSINESS_OAUTH2, SHAREPOINT_ONLINE_OAUTH2, GOOGLE_DRIVE_OAUTH2 (only in preview), GENERIC_HTTPS (currently hidden by default), SCAN_TO_DOWNLOAD "smtpConnectorParameters": { // optional, used only if connectorType is EMAIL "messagingConfigId": int // optional, System default messaging config used when not provided }, "sharePointConnectorParameters": { // optional, used only if connectorType is SHAREPOINT_ONLINE_OAUTH2 "siteName": string // optional, will be empty if not specified }, "genericHttpsConnectorParameters": { // optional, used only if connectorType is GENERIC_HTTPS "endpointUrl": string, // required, has to be valid HTTPS URL "properties": { // optional, additional properties (key-value pairs) to be passed with the request (for example for custom authentication) "auth_username": string, // the key has to be an unique string "auth_password": string } }, "scanToDownloadConnectorParameters": { // optional, used only if connectorType is SCAN_TO_DOWNLOAD "notificationEnabled": boolean, // optional, false by default "messagingConfigId": int, // required if notificationEnabled is true "templateConfigId": int // required if notificationEnabled is true }, "retryAttemptsCount": int, // optional, default 0, range 0-99999 "retryAttemptsTimeout": int, // optional, number of seconds, default 3, range 0-120 "deliveryRestrictions": { // optional, may be null "enabled": boolean, // optional, default false "maxScanJobSize": int // required if enabled is 'true', otherwise not used, maximum scan job size in megabytes, range 1-999999 } ### ScanWorkflowTemplateInfo "id": int, "name": string, // max length 100 "description": string, // optional, max length 300 "connectorId": int, "scanOptions": { // optional, may be null "resolution": string, // optional, LOW, NORMAL, FINE, HIGH, HIGHEST "colorMode": string, // optional, AUTO, BLACK_AND_WHITE, FULL_COLOR, ONE_COLOR, TWO_COLOR, GRAY_SCALE "pageSides": string, // optional, SIMPLEX, DUPLEX "mergingOriginals": string, // optional, DISABLED, ENABLED "resolutionEditableByUser": boolean, // optional, default false "colorModeEditableByUser": boolean, // optional, default false "pageSidesEditableByUser": boolean, // optional, default false "mergingOriginalsEditableByUser": boolean // optional, default false }, "ocrOptions": OcrProcessingStep, // optional, may be null "barcodeOptions": BarcodeOptions, // optional, may be null "documentSeparationOptions": DocumentSeparationOptions // optional, may be null "highlightRedactionOptions": HighlightRedactionOptions // optional, may be null "smtpConnector": { // optional, used only if connectorType is EMAIL "mailTo": string, "mailSubject": string, "mailBody": string, }, "sharePointConnector": { // optional, used only if connectorType is SHAREPOINT_ONLINE_OAUTH2 "rootPath": string, "relativeTargetPath": string, "overwriteBehavior": string, // KEEP_BOTH, REPLACE_ORIGINAL, APPEND_TO_PDF, PREPEND_TO_PDF "columns": list, }, "oneDriveConnector": { // optional, used only if connectorType is ONEDRIVE_BUSINESS_OAUTH2 "relativeTargetPath": string, "overwriteBehavior": string, // KEEP_BOTH, REPLACE_ORIGINAL, APPEND_TO_PDF, PREPEND_TO_PDF }, "googleDriveConnector": { // optional, used only if connectorType is GOOGLE_DRIVE_OAUTH2 "relativeTargetPath": string, "overwriteBehavior": string, // KEEP_BOTH, REPLACE_ORIGINAL, APPEND_TO_PDF, PREPEND_TO_PDF }, "fileName": string, // optional, may be null "fileType": string, // PDF, TIFF, JPEG "sortOrder": string, // optional, default is last (e.g. 3 if this is 3rd workflow created) "active": boolean, // optional, default true "userInputs": list, // optional, may be null, "fileTypeEditableByUser": boolean // optional, default false, when OcrProcessingStep is enabled this is always false ### ScanWorkflowAccessInfo "id": int, "workflowId": int, // optional, id of ScanWorkflowTemplateInfo "workflowName": string, // optional, name of ScanWorkflowTemplateInfo "identityId": int, // optional "identityName": string // optional "identityType": String, // optional, User or Group "allowAccess": boolean // optional, default true ### DocumentSeparationOptions enabled": boolean, // Note: In a PUT request, if this field is set to false, the entire existing DocumentSeparationOptions is removed "separationType": string, // BARCODE_TYPE, SEPARATION_SHEET, PAGE_COUNT "separationBarcodeType": string, // only used when separationType is BARCODE_TYPE, values: UPC_A, UPC_E, EAN_8, EAN_13, CODE_39, CODE_93, CODE_128, CODABAR, ITF, RSS_14, RSS_EXPANDED, ALL_1D, AZTEC, DATA_MATRIX, MAXICODE, PDF_417, QR_CODE "dropSeparator": boolean, // only used when separationType is BARCODE_TYPE or SEPARATION_SHEET, optional, may be null, BARCODE_TYPE default value false, SEPARATION_SHEET default value true "pageSplitSize": string // only used when separationType is PAGE_COUNT, variable or a positive whole number ### OcrProcessingStep "enabled": boolean, // Note: In a PUT request, if this field is set to false, the entire existing OcrProcessingStep is removed "blankPages": boolean, "dualPages": boolean, "pageOrientation": boolean, "despeckle": boolean, "languages": list, "outputFormatParameters": { "pdfaCompliance": string, // PDF_A_1A, PDF_A_1B, PDF_A_2A, PDF_A_2U, PDF_A_3A, PDF_A_3U "modifyMetadata": boolean, "metaTitle": string, "metaAuthor": string, "metaSubject": string, "metaKeywords": string, "metaOverwriteUponChange": boolean, "mrcCompression": boolean, "encryptPdf": boolean, "encryptionStrength": string, // RC40BIT, RC128BIT, AES128BIT "encryptionPasswordType": string, // GeneratePassword, ManualPassword "encryptionPassword": string, // only used when encryptionPasswordType is ManualPassword "sendEmail": boolean, "emailRecipients": string, "emailSubject": string, "emailBody": string } ### BarcodeOptions "enabled": boolean, // Note: In a PUT request, if this field is set to false, the entire existing BarcodeOptions is removed "barcodeType": string, // UPC_A, UPC_E, EAN_8, EAN_13, CODE_39, CODE_93, CODE_128, CODABAR, ITF, RSS_14, RSS_EXPANDED, ALL_1D, AZTEC, DATA_MATRIX, MAXICODE, PDF_417, QR_CODE ### HighlightRedactionOptions "enabled": boolean, // Note: In a PUT request, if this field is set to false, the entire existing HighlightRedactionOptions is removed "highlightColor": string, // GREEN, RED "redactionType": string, // WHOLE_DOCUMENT, RANGE "rangeFrom": string, // optional, may be null. Only used in RANGE redaction type "rangeTo": string, // optional, may be null. Only used in RANGE redaction type ### SharePointColumnsData string: string // first string is column name, second is column value ### UserInputInfo name: string, label: string, defaultValue: string, // optional, may be null required: boolean, // optional, may be null userInputType: string, // LIST BROWSE TEXT NUMBER EMAIL values: List // optional, may be null. Only used for LIST type ### ListUserInputValueInfo value: string label: string ### AuditLogInfo category: string type: string, eventContext: { serverId: string traceId: string source: string requestDateTime: string, // in ISO-8601 format request: { AuthenticatedRequest: { executingUser: { user: { // optional, may be null name: string, id: int, accountId: int, providerId: int } } } }, sourceSocket: { // optional, may be null address: string, port: int }, destinationSocket: { // optional, may be null address: string, port: int }, requestingDomain: string, // optional, may be null auditLogCustomOpName: string, // optional, may be null accountAccessReason: { // optional, may be null issue: string, reason: string }, accountId: int }, timestamp: string // in ISO-8601 format id: int // optional, may be null intent: object, // optional, may be null intentResult: object, // optional, may be null result: object, // optional, may be null customOp: object, // optional, may be null updatedType: string // optional, may be null objectType: string, // optional, may be null entityType: string, // optional, may be null oldEntity: object, // optional, may be null toAddEntity: object, // optional, may be null previousEntity: object, // optional, may be null toDeleteEntity: object, // optional, may be null updatedChildren: object, // optional, may be null access: object, // optional, may be null addedAccess: object, // optional, may be null removedAccess: object, // optional, may be null parent: object // optional, may be null error: object // optional, may be null ### EndpointInfo "endpointId": string, "description": string, "endpointType": string, //Server, Printer, PC Client, Browser extension, Mobile device "authorized": boolean ### BalanceConfigInfo accountId: int // the account this configuration belongs to enabled: boolean // per-account balance/quota enable switch bwNormalPage: decimal bwLargePage: decimal colorNormalPage: decimal colorLargePage: decimal ### BalanceConfigData enabled: boolean // required bwNormalPage: decimal // required, zero or greater bwLargePage: decimal // required, zero or greater colorNormalPage: decimal // required, zero or greater colorLargePage: decimal // required, zero or greater ### BalanceCheckData uuid: string // UUID of the document to check userName: string providerId: int totalPages: int colorPages: int paperSize: string copies: int ### BalanceCheckInfo balanceEnabled: boolean // whether balance/quota is enabled for the account sufficientBalance: boolean // whether the current balance covers the calculated cost currentBalance: decimal calculatedCost: decimal // cost computed for the document from the price list ### UserBalanceInfo userName: string providerId: int quotaBalance: decimal walletBalance: decimal totalBalance: decimal lastUpdated: Option // in ISO-8601 format ### BalanceTransactionInfo id: int userId: int // the user the transaction belongs to userName: string providerId: int accountId: int quotaAmount: decimal // negative for deductions/withdrawals walletAmount: decimal transactionType: string // TOP_UP, DEDUCTION, ADJUSTMENT, RESERVATION, RESERVATION_RELEASE, INITIAL, WITHDRAW, RENEW quotaBalanceAfter: Option walletBalanceAfter: Option documentUuid: Option description: string adminUserId: Option timestamp: Option // in ISO-8601 format ### BalanceTransactionData userName: string providerId: int operation: string // "add", "remove" or "set" balanceType: string // "quota" or "wallet"; "set" supports only "quota" amount: decimal // add/remove: positive amount; set: target value (zero or greater) description: string // optional, default "" ### PagedResult\ items: list recordsOnPage: int nextPageToken: Option // absent on the last page ### BalancePolicyInfo id: int // 0 for the virtual (not yet persisted) default policy accountId: int // the account this policy belongs to policyName: string balanceType: string // free, quota, wallet, quota_wallet priority: int // 0 = default policy; lower number = higher precedence isDefault: boolean initialBalance: decimal groupIds: list // always empty for the default policy schedule: Option // present when the policy has a reset schedule lastUpdated: Option // in ISO-8601 format ### BalancePolicyScheduleInfo enabled: boolean // whether the schedule is active frequency: string // weekly, monthly, quarterly, yearly scheduledTime: string // first run, ISO-8601 offset date-time normalized to UTC targetAmount: decimal // amount the policy's users are reset to on each run ### BalancePolicyData policyName: string // required, max 256 characters balanceType: string // required: free, quota, wallet, quota_wallet initialBalance: decimal // optional, default 0, must be zero or greater groupIds: list // optional, default empty; must belong to the account schedule: BalancePolicyScheduleData // optional; absent = leave the reset schedule unchanged ### BalancePolicyScheduleData enabled: boolean // optional, default true; false removes the schedule frequency: string // weekly, monthly, quarterly, yearly; required when enabled scheduledTime: string // first run, ISO-8601 offset date-time; required when enabled targetAmount: decimal // optional, default 0, must be zero or greater ### BalancePolicyOrderData orderedPolicyIds: list // exactly all non-default policy ids in the desired order --- version: "2026.08.20" variant: "PMC" language: "en" --- # OAuth error codes The following implementation-specific error codes are currently defined. They are part of the error_description. * not_implemented -- request not implemented * access_denied -- access denied * missing_signature -- missing request signature header * invalid_signature -- invalid request signature * invalid_parameters -- invalid parameters * invalid_client_secret -- wrong API key * token_refresh_error -- error occurred while refreshing a token * token_create_error -- error occurred while creating a token * invalid_device_code -- invalid or expired device code * invalid_client_id -- invalid client id * authorization_pending -- authorization pending, keep polling * invalid_response_type -- invalid response type parameter * invalid_key_type -- invalid key type parameter * invalid_endpoint -- client not found in the database * endpoint_not_authorized_for_device_token_refresh -- endpoint is not authorized for the token refresh operation * invalid_client_for_signature_verification -- cannot verify signature for client * invalid_grant -- the given grant type is not supported * duplicate_client_id -- the device is attempting to register using a client_id that is already associated with another device. Please contact the administrator. * error_saving_endpoint -- there was en error when saving the endpoint * token_create_error -- error occurred while issuing a token * authorization_pending -- authorization pending * expired_device_code -- the provided device code has expired --- version: "2026.08.20" variant: "PMC" language: "en" --- # Obtain device token Use this endpoint to acquire a device token. Endpoint is available at `/token` relative path. Parameters: * `client_id`: unique client ID * `client_secret`: API key * `grant_type`: device_code * `device_code`: the device code acquired via registration call Return value: The `Error` object if error occurred, otherwise `Token` JSON object which has the following structure: { "token_type": "Bearer", "expires_in": NNN, "access_token": "xxx", "refresh_token": "yyy" } * token_type -- Always "Bearer". * expires_in -- Access token expiration time in seconds. * access_token -- An access token that you must provide in the call to the public API login function. * refresh_token -- The token used to refresh the device token. If `authorization_pending` error is returned, the client should keep polling the endpoint until the token is acquired or some other error is returned. --- version: "2026.08.20" variant: "PMC" language: "en" --- # Refresh device or user token Use this endpoint to refresh device token or user token acquired from the public API /login call. Endpoint is available at `/token` relative path. Parameters: * `client_id`: unique client ID. Use "api" value for user token acquired from the public API * `client_secret`: API key * `grant_type`: refresh_token * `refresh_token`: the refresh token Return value: The `Error` object if error occurred, otherwise `Token` JSON object with the following structure: { "token_type": "Bearer", "expires_in": NNN, "access_token": "xxx", "refresh_token": "yyy" } * token_type -- Always "Bearer". * expires_in -- Access token expiration time in seconds. * access_token -- A device access token. * refresh_token -- The new refresh token. --- version: "2026.08.20" variant: "PMC" language: "en" --- # Register device Register device function is used to perform initial device registration which must be then approved by the administrator, or to perform device re-registration using the known public key. It is available at `/register` endpoint. Required parameters: * `client_id`: unique device ID * `client_secret`: PMC API key * `client_type`: one of: printer,chrome_extension,desktop_client,mobile_device,server * `response_type`: must be device_code Optional parameters: * `client_description`: client description * `state`: a nonce value * `public_key`: base64-encoded public key * `key_type`: public key type, one of: rsa,x509,ed25519 `public_key` and `key_type `parameters, combined with `HCP-Request-Signature` header provide a means how a known, authorized device may automatically re-register itself automatically and securely, even after extended periods of time. This functionality is optional, but if desired, then both parameters must be filled in. Public keys must be wrapped into base64 encoding. Public keys must be encoded in accordance with X.509 encoding standard. The difference between `rsa` and `x509` is that the provided `x509` structure contains also certificate fields in addition to the public key, so a certificate can be passed as a public key. ED25519 key can be provided in both X.509 encoding and in plain encoding (32-byte key). If `HCP-Request-Signature` header is present in the request the device re-registration is assumed and registration approval is not required (provided that the signature is correct). If signature header is missing a new device registration is performed. Return value: `Error` object if error occurred, `DeviceCode` object if registration succeeded. `DeviceCode` is a JSON object with the following structure: { "device_code": "xxx", "state": "xxx", "expires_in": nnn } Where device_code is a device code which must be used when calling the `/token` endpoint, state is the nonce passed as a parameter, expires_in indicates the device_code expiration time in seconds. After registration call is made the client should poll the `/token` endpoint to exchange the obtained device_code for the device token. --- version: "2026.08.20" variant: "PMC" language: "en" --- # Request example The following examples are using `curl` command to send OAuth requests to PMC server. Public and private keys shown here should not be used in production and are only provided as an example. We will use a pair of random ED25519 keys: Private key: `pP20r1Hmqf5NTO8Rd7Truipu5f8aR+Em47cTvWleTc8dRS2cJ20bXH2iJIjg4O28gSYj+qnuUWSey7WWlWTxPw==` Public key: `HUUtnCdtG1x9oiSI4ODtvIEmI/qp7lFknsu1lpVk8T8=` The following web site can be used to generate test keys or signatures: [https://ed25519.herokuapp.com](https://cyphr.me/ed25519_tool/ed.html) ## Register a device All parameters must be url-encoded, in particular the public key. curl https://accountdomain:7400/oauth/v1/register -k -i -X POST -d "client_id=0966a26c-a5fc-4276-9c6b-587d02aceb91" -d "client_secret=mykey" -d "client_type=printer" -d "public_key=HUUtnCdtG1x9oiSI4ODtvIEmI%2Fqp7lFknsu1lpVk8T8%3D" -d "key_type=ed25519" -d "response_type=device_code" Response: `{"device_code":"wVgzOcLwemGJPfY_d01E3PA8H3k","expires_in":259200}` ## Create request signature Generate a signature using any tool or online site above. Query string: `client_id=0966a26c-a5fc-4276-9c6b-587d02aceb91&client_secret=mykey&grant_type=device_code&device_code=wVgzOcLwemGJPfY_d01E3PA8H3k` Signature: `MKS1dCmgp4rLbZ2oaQeFb9pultWjI0zU7si5lb3oLCJWH8t8jgps4LLz/isPSa5OWfQAtFB3NAu04axirmF9CA==` ## Obtain device token curl https://accountdomain:7400/oauth/v1/token -k -i -X POST -H "hcp-request-signature:MKS1dCmgp4rLbZ2oaQeFb9pultWjI0zU7si5lb3oLCJWH8t8jgps4LLz/isPSa5OWfQAtFB3NAu04axirmF9CA==" -d "client_id=0966a26c-a5fc-4276-9c6b-587d02aceb91" -d "client_secret=mykey" -d "grant_type=device_code" -d "device_code=wVgzOcLwemGJPfY_d01E3PA8H3k" Response: `{"error":"authorization_pending","error_description":"Authorization pending"}` --- version: "2026.08.20" variant: "PMC" language: "en" --- # Trusted device registration Trusted devices are PMC clients which are required to be authorized by PMC administrator before they can perform certain API calls. The API key setting `Allow untrusted endpoints` controls whether client using this API key is required to be in a trust relationship with PMC server. If this option is disabled (which is the default) the client must obtain a device token before calling authentication functions of the public API. This device token must be then provided to the `/login` API call as `Authorization: Bearer ` header. Trusted connection ensures for example that password-less authentication (card ID or short ID) can only be used from the trusted devices. Trusted devices functions are available at `/oauth/v1` base endpoint on HTTPS port **7400 (** gateway) or**443 (** cloud server). All requests must be sent as HTTP POST with parameters encoded as **application/x-www-form-urlencoded** . All responses are JSON objects. In case of an error the `Error` JSON object is returned which has the following structure: { "error": "error_code", "error_description": "textual error description" } Some functions may use the **HCP-Request-Signature** header which holds a signature of the parameter string. For POST requests, that is the signature of the request body. Signature algorithm depends on the `key_type` parameter provided to the `/register` call. Signature must be wrapped into base64 encoding. --- version: "2026.08.20" variant: "PMC" language: "en" --- # User and device tokens PMC server allows a fine-grained control over the public API access on user level or device (client) level. For that purpose there is a concept of user token and device token: * **User token**: this is a token acquired after calling a login function of the public API. It should be provided to all other functions * **Device token**: this is a token acquired after calling the PMC OAuth service and establishing a trust relation between the client and the server. Device token should be provided when calling a login function of the public API. Access tokens have a short expiration time (typically one hour). They can be renewed using a refresh token (which is returned as a part of TokenInfo structure) to maintain a login state longer than 1 hour. Refresh tokens are usually valid for 3 months, after that the user must re-authenticate (or device re-registered). Token validity times can be configured in the account settings in PMC server administration UI. API key has two parameters which control the security of the public API endpoints: * `Allow unauthenticated requests`: allows to call API functions without the user token or to authenticate with insecure credentials (card ID, short ID, user name only, email address). If this option is disabled (default) the client is required to call the `/login` endpoint first and provide the returned access token to all other API requests as a `Authorization: Bearer ` HTTP header. Failure to provide a token will result in error 403 for all requests. * `Allow untrusted endpoints`: if enabled this option allows to authenticate from any client without obtaining a trusted device token first. If disabled (default) the client is required to be in a trusted relation with PMC server and provide a device token when calling the `/login` endpoint, in a form of `Authorization: Bearer ` header. --- version: "2026.08.20" variant: "PMC" language: "en" --- # Version History The following contains a list of notable changes in RICOH PMC API Legend: + Added feature x Improved/changed feature - Bug fixed ## Build 2025.03.20 x /api/v1/inputports and /api/v1/outputports now by default does not return extended port info, new boolean flag enrichPorts was introduced to specify if additional information should be included (default: false) ### Build 2025.02.06 No changes from the previous release. ### Build 2025.01.23 No changes from the previous release. ### Build 2025.01.09 No changes from the previous release. ### Build 2024.11.28 No changes from the previous release. ### Build 2024.11.14 + new API available to list of all users (only local and those actually using the solution) /api/v1/users/all ### Build 2024.10.31 No changes from the previous release. ### Build 2024.10.17 No changes from the previous release. ### Build 2024.10.03 No changes from the previous release. ### Build 3.49 \[2024-09-19\] + Account API was extended with new fields for page size, language, and color. The update option now contains the name and domain name. API responses were improved. x Print queues created by API are now enabled by default. ### Build 3.48 \[2024-08-22\] No changes from the previous release. ### Build 3.47 \[2024-07-25\] - Uploading a print job to a non-existing input port via API no longer returns 200 instead of an error. ### Build 3.46 \[2024-06-27\] - The API no longer allows deletion of the Local authentication provider. ### Build 3.45 \[2024-06-11\] - If the request does not contain the "Content-Type: form-data" header, the response status is no longer 500. ### Build 3.44 \[2024-05-09\] No changes from the previous release. ### Build 3.43 \[2024-04-04\] x Administrators can now create multiple values per API Access Key, thus streamlining the administration. x GetAccount API now includes Account UUID. ### Build 3.42 \[2024-03-07\] No changes from the previous release. ### Build 3.41 \[2024-02-08\] + Added a get user by username endpoint. + Page orientation now respects the request specified in the API request. ### Build 3.40 \[2024-01-11\] - The Document history endpoint now returns the jobtype property. - The use of full API access keys is now discouraged in order to enhance security. - Whenever the API returns a 403 error due to missing permissions, it also returns the list of the missing permissions. ### Build 3.39 \[2023-11-02\] No changes from the previous release. ### Build 3.38 \[2023-10-05\] x Added the ability to manage access rights. x Improved security of document history API by adding role-based access. x Increased security by only displaying API keys once when generated. The ability to view existing API keys is removed. ### Build 3.37 \[2023-09-07\] x Updated backend API key security. x Added AUD (audience) claim to API access tokens for improved security. - Adding authentication providers using API (/authproviders) now works correctly. ### Build 3.36 \[2023-08-10\] x Added public API for Scan Workflows. (The Scan Workflow feature is currently hidden by default and may not be available for your account.) ### Build 3.35 \[2023-07-13\] No changes from the previous release. ### Build 3.34 \[2023-06-26\] No changes from the previous release. ### Build 3.33 \[2023-05-18\] x Added printer information to Documents History API. - Fixed issue with Access Control List (ACL) inheritance properties when updating ACL via API. ### Build 3.32 \[2023-04-25\] + {ShortProductName} API endpoint date/time matches the actual job release date/time. - Documents/history API endpoint is filtering for the "PRINTED" status. ### Build 3.31 \[2023-03-31\] + Customer can get information on users' group membership via Public API. ### Build 3.30 \[2023-02-24\] - In document history, documents are recorded under the correct device when the jobs are sent with the "serialnumber" parameter. ### Build 3.29 \[2023-02-03\] + Added public API for pulling the embedded terminal configuration. + Added public API endpoint to record print/copy/scan jobs. ### Build 3.28 \[2022-12-15\] x Device code workflow requests changed from GET to POST. x Device code workflow: the public/private keys are optional now. ### Build 3.19 \[2022-02-03\] + Add admin functions to create/delete/update locations in the LocationsRequest endpoint + Extend InputPortsRequest endpoint and add an additional optional locationId parameter to the creation function + Add optional description field to the output port creation in OutputPortsRequest + Extend OutputPortInfo with the following fields: description, embedded config, protocol, model family, output type, serviceId, serial number ### Build 3.16 \[2021-10-13\] + Added Documents History API --- version: "2026.08.20" variant: "PMC" language: "en" --- # Cloud documentation ## About this document ### Styles To make the reading of this guide easier, different styles and fonts are used. **Bold** style is used to mark elements from the GUI, e.g. "Click **OK**." *Italic* style is used to refer to a specific section of the guide, e.g. "...see section *Terms and definitions."* `Monospace` style is used for paths, keyboard inputs, and code quotations. ### Infoboxes Tip -- a piece of information that you might find helpful. Info -- additional information which can help you to understand the product or the context better but which isn't necessary to perform the given procedure. Note -- a piece of information that shouldn't escape your attention, such as important settings or limitations. Warning -- warning about a critical situation, such as a security threat risk or a risk of data loss. ## Terms and Definitions | Term | Description | |---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | PMC | A cloud-based print management service. | | Gateway/Edge device | A local device, such as Y Soft OMNI Bridge, installed at the customer site. This device provides site services and serves as a bridge between local users, devices, and PMC. | | YSoft OMNI Bridge | YSoft OMNI Bridge is a piece of hardware manufactured by Y Soft. | | Pure Cloud printing | A service with architecture (printing method) based on MFDs that support pure cloud terminals. This scenario does not require edge devices. | | Edge printing | A service with architecture (printing method) based on MFDs using standard embedded terminal technology which can connect to a local Edge device (providing site services). Suitable for situations where Pure Cloud printing is unavailable or not wanted (for example, if customers want to keep print job data local to their network, or they have a wider portfolio of devices than is supported by PMC pure cloud terminals). | | MFD | Multi-function device - a device that can print, scan, copy, and optionally fax. | | SFD | Single-function device (a printer). | | PMC Web UI | A web interface used by partner admins to create customers (tenants) in PMC and by customer administrators to manage their tenants centrally. | ## Personas and roles | Persona | Description | |--------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Managed Service Provider (MSP) | The role with the highest set of privileges in the PMC service, responsible for service availability and maintenance. Has access to all customer settings. Is responsible for PMC web UI maintenance, monitoring, deployment of updates etc. | | Partner | A partner of MSP. It can also be a reseller (a partner of a partner). | | Customer | The customer of a partner and, at the same time, a representation of the customer in PMC Web UI. This representation is sometimes called Tenant. Each Customer has its own admin. This can be the partner admin or the customer admin. | | Partner admin | An administrator in the PMC Web UI who can (if agreed with the customer) manage settings in PMC Web UI on customer's behalf. | | Customer admin | An administrator on the customer side with rights to manage settings in PMC Web UI. | | End user | A persona within a Customer's PMC instance that is permitted to print/copy/scan. | --- version: "2026.08.20" variant: "PMC" language: "en" --- # 2018 The following contains a list of notable changes in RICOH PMC. Legend: + Added feature x Improved/changed feature - Bug fixed ## 2.4.1 \[2018-11-07\] + Added "Monochrome printer" option in the output port settings + Add support for keyboard emulation wedge readers on Konica Minolta - Fixed issue where KM embedded could set incorrect settings on device if another auth already set ## 2.4.0 \[2018-11-05\] + OKTA authentication support + Added new Canon embedded terminal + Add support for Ricoh SLNX Share embedded terminal in PMC + Expanded caching for improved login experience on embedded clients on poor connections + Ability to have containers + Ability to move an account/vendor/printer/service/server from one place in the tree to somewhere else + UI for API Access Key management + Extend unattended install option with service bootstrapping + Increasing security registering a secondary server + API function to create input ports + Add language selection to account settings (for future use) + Ability to configure separate JVM and thread counts for services + Support for Canon Postscript universal printing + Ability to remain logged in with Custom Login in PC client + Popup notification if custom login and user has not signed in to PC client + Local users (such as guests) are now part of a local group called \[Local users\] x Hide Download buttons in Log view x Hide options to modify print output settings on KM embedded client x Adding a new access control will now copy the inherited permissions if new access is first one x Modify OKTA authentication to allow for username attribute specification x Set PMC universal driver to BW as default x Automatically set default print queue in PC client to pull print or first push queue x Enhanced authentication caching for quicker MFD login x Added official support for Sharp - Fixed Sharp Embedded with missing part in the display - Fixed issue with password in clear text on display in Sharp Embedded - Fixed issue where secondary gateway on version earlier than 2.3.1 appeared offline in UI with newer primary - Fixed issue with passwords containing special characters in PC-Client ## 2.3.3 \[2018-09-17\] - Fixed issue with deploying to Ricoh MFD's not configured for TLS1.2 - Fixed issue authenticating against IBM Domino LDAP ## 2.3.2 \[2018-09-05\] - Fixed issue with conversion service causing delays in some configurations - Fixed issue with printing multiple copies on HP printers and pull print release - Changed output of account details outputted in log file ## 2.3.0 \[2018-08-30\] + Ability to easily configure high availability clusters for primary servers + Ability to use Equitrac embedded release terminals with PMC + Ability to run service on multiple servers + Unattended installation of PMC server + Extend Users UI to also show and edit non-local users + Ability to restrict user access to input ports based on user/group permissions + Change PMC secondary gateways to not use direct DB connection + Ability to deliver print job data via IPP and IPPS in document output service + Added Strict domain validation feature + Ability to delete Pending jobs + Allow split of LDAP user and group lookup into different search DN's x Increase security in configuration files x Restrict Web TLS security to 1.2 x Add view log permission x Expand installer connection port check for all required ports for primary x Changed handling of mobile print jobs if an unknown page size is detected x Improved loading of left navigation tree x Changed default permissions for roles Reporting and Users - Changed starting of secondary servers if restarted in offline cache mode - Fixed issue where no email address supplied to MFD's for scan to email - Fixed issue where adding private key chain to the root vendor broke relay document transfer - Fixed PC Client wrong paper size - Fixed issue where some jobs could stays in Windows spooler on client - Fixed Ricoh printing issue with universal printer driver - Fixed issue where Local auth provider on secondary server configured with primary auth service causes authentication delays - Various UI improvements when editing printers or viewing print history - Various UI improvements to installer for more helpful error messages - Fixed issue where color print job released as BW was counted as color - Fixed issue when deleting an account ## 2.2.2 \[2018-06-05\] - Fixed issue deleting an account, causing broken deletion of triggers - Fixed issue with card enrollment failing for certain scenarios of LDAP users ## 2.2.1 \[2018-06-04\] - Sending certain PS jobs registered as PDF ## 2.2.0 \[2018-05-29\] + New PC client for Windows and MacOS for automatic creation and deletion of PMC universal driver and print queues on PC workstations + Triggers and Automations engine for rule based workflows and automated tasks + Improve installer checks for common pitfalls; missing dependencies, firewall ports and similar + Ability to set SNMP community names for Xerox embedded configuration + Implement job deletion based on retention time (32 hours by default) + Added support for Mobile Print from Apple iOS and Android Apps + Added support for native Apple iOS AirPrint with Wide Area Mobile Print feature + Added ability to optionally specify UserID, username, authentication provider ID and account domain name in IPP URL + Added QR code generation for printers + Display server version in Server Settings x Expand API for creating and deleting triggers and automations x Added option to enable/disable scan application for HP embedded (scan app not relevant for FS4 models) x Added loading indicator on Access Controls search x Expand the input and output port Pending Jobs and History with additional data x Extend public API to accept an extra header as an account domain name x Preset default HP card reader values in UI to simply HP setup x Extend API with ability to register cards to existing users and create users with cards x Enhanced HP client for better compatibility with FS4 generation HP firmware x Improved error handling for KM embedded deployment when KM device is locked, in use, in error or similar x Enhanced KM embedded to support strict TLS 1.2 x Many minor Web UI improvements x Enhancements for future proofing primary servers for backwards version compatibility with old secondaries x Make email optional when creating user via API x Enhanced page counting of jobs of certain types - Fixed issue with document name and number of pages incorrect while printing from the Edge browser directly - Fixed UI issues with LDAP and OU configuration - Fixed issue where user in specific cases could create two of same services pointing to the same server - Fixed issue with duplex printing as simplex if set from HP embedded - Fixed issue with Scan app on HP gives error on FS4 models - Fixed issue with Sharp embedded giving no relevant error if wrong login with card registration - Fixed issue with KM Embedded where clicking Logout in the embedded terminal did not log the user out ## 2.1.0 \[2018-02-19\] + PMC Reporting 1.0 + Azure Active Directory Authentication + Ability to delete accounts, servers + Major improvements to future backwards compatibility + Major performance improvements + Added permission to control if users can modify logos on accounts + Interface for modifying USB card reader vendor and product ID's for HP MFD's x Disable Web UI on secondary gateway servers x Expand public API with output port and account creation calls ## 2.0.1 \[2018-01-24\] + Added Lexmark embedded support + Added Sharp embedded support (BETA) + Added region support for KM client (EU vs US) x Improved secondary server performance when using embedded clients - Bugfix for secondary server deployment when server hostname was not in /etc/hosts file - Fixes and improvements for certain LDAP configurations --- version: "2026.08.20" variant: "PMC" language: "en" --- # 2019 The following contains a list of notable changes in RICOH PMC. Legend: + Added feature x Improved/changed feature - Bug fixed ## 3.1.2 \[2019-12-13\] x Improved SAMLv2 support for AD-FS On-Premise x By default restrict access to Windows PMC PC Client PMCclientcore folder to PMC service account only x Enforce SSL validation option for PC Client IPPS printing x Changed MacOS PC client to not share queues on network by default x Added support for Ysoft, Omnikey and Elatec TWN3 card readers in IP card reader bridge x Updated curl library used by PMC PC Client installer x Improve user authentication when doing OTP authentication - Fixed miscellaneous issues in KM IWS application - Fixed issue with PC Client for Mac and server connection failing on macOS Catalina - Fixed issue with triggers not applied when printing with PC Client in Local Storage mode ## 3.1.1 \[2019-12-03\] - Fixed issue with releasing of jobs stored on PC client didn't work in some configurations when document output service was on the secondary server - Fixed issue with collation and staple multi-copy printing on HP ## 3.1.0 \[2019-11-19\] + HP Workpath (formerly Link platform) embedded app + Ricoh SOP Android embedded client + Konica Minolta IWS embedded App + PC Client 3.0 for Mac + SAML v2 single sign on + New Windows PMC print driver + Support Microsoft SQL Server/SQL Azure for backend database + Ability to have local users as part of groups + System to self-register swipe cards for users without password + Support scan and copy reporting from Ricoh SLNX Share in PMC + One-time password feature for users without password or multi-factor configurations + Support SecurityEngineering IP card reader + Support RFIDeas 241 IP card reader + Support CentOS 8 + PMC Driver UI improvements + End-user interface to manage Short ID + Expand PMC driver with additional trays up to 6 + New My Profile end-user Web UI screen + Automatically generate a Short ID or One-time password based on trigger x Many improvements to print driver performance and print job rendering x Improved validation of Short ID and card ID being unique for an account x Improvements to primary cluster communication and performance x Added HP native keyboard as workaround for missing symbols on HP OXP embedded keyboard x Improved support for very hardened Linux OS distributions used in high security environments x Disabled copy and scan accounting for Xerox embedded application on some models - Fixed issue with multiple jobs wouldn't release when user selects all and deselects few of the jobs - Fixed print issues on Xerox AltaLink with Letter and A3 - Fixed new added private certificate chain not loaded properly for mobile print service - Fix issue with print queue creation on some macOS configurations - Fixed issue where after upgrade from PMC 2.5.x to 3.x, all documents printed before upgrade could appear as printable - Fixed Lexmark tray selection problem - Fixed issue with certificate handling with some HP firmware versions which could result in "Server or network problems" error on device ## 3.0.3 \[2019-10-07\] + Added new setting to control MDM single-sign-on feature enablement in Mobile Print settings x Changed PC Client to show popup on sync error only once per interruption x Changed Mac PC Client from "PMC Client" to "PMCclient" for plist settings x Updated Mac PC Client installer for recent macOS versions x Change utility in PC Client to avoid false positive flag by some antivirus engines x Updated PMC client core for Windows 7 compatibility x Changed lookup of printers on input port configuration, for configuration of push print queues with printers outside container x Changed OKTA integration to retrieve user email attribute in more configuration scenarios - Fixed issue with some Sharp printers hanging after booklet printing - Fixed PC Client Incorrect output bin selection for Ricoh printers ## 3.0.2 \[2019-09-20\] + Added support for RedHat Enterprise Linux/CentOS 8 x Changed PC Clients list view to not show version for quicker listings x Major network stability and performance improvement for PC Clients and Secondary Gateway servers x Improvements to UI behavior when running larger primary cluster configurations x Major Web UI performance improvements for very large account trees x Changed print all from embedded clients to not print jobs in random order - Fixed issue with log rotation, not creating new log files - Fixed issue where print jobs stored on PC Client sent to release during PC sleep, could be released when waking up - Fixed issue with trigger Set document attribute to B/W or Color not working. - Minor UI issues fixed, such as Access control page not refreshing after Local rights are given to a user - Fixed authentication failing if auth service running on 2 secondary servers and one is unauthorized ## 3.0.1 \[2019-07-01\] + Added caching of keystores for greatly improved secondary server service performance x Optimizations for Web UI session cache for cluster configurations ## 3.0.0 \[2019-06-29\] + New PMC PC Client 3.0 with local storage and delivery option for serverless deployments + Location aware printers + Encryption of document data at rest + Reporting on scan and copy from embedded clients + Ability to restrict and pre-authorize PC clients or secondary servers based on customer PKI + Added high performance caching system for major performance improvements throughout PMC + Ability to specify API key for secondary servers and PC clients + Release all option on embedded card authentication + Support network connected card readers via API + Ability to specify an API key during silent unattended installation of primary server + Support for OKTA LDAP authentication + Add extra authentication option for PC client: User Principal Name + Make UI embedded configuration setting for Konica Minolta native card reading + Enable the ability to delete and edit the default API key + PMC Web UI in French + Possibility to configure duplex/color via the unattended installer options + Add Local providers and Local Users group with Users role by default on new accounts + Ability to authenticate in PMC using UserPrincipalName with AD/LDAP + Support Debian 9 Stable versions + Ability to set new PC client/server trust via API + Possibility to select paper sizes A5 and A6 in PMC single driver + Ability to force resync of printers on PC Client update + Option to have desktop icons for PC Client Login and Logout created + Expand LDAP configuration to include object class for persons and object class for groups x Major performance improvements for large distributed data transfer x Improved embedded pull print release performance x Major performance and quality improvements for PMC MacOS Universal printer driver x Numerous Web UI usability improvements x Disable HTTP trace and track method x Changed print jobs displayed and printed in reverse order x Restrict old default API key usability x Generic branding in Xerox and HP embedded clients x Added Input Ports option for Containers x Changed HP embedded to allow locking of everything and unlocking of 3rd party apps x Improved image quality when printing high graphical jobs to Konica Minolta MFD's - Fixed issue releasing PMC print jobs on Equitrac embedded clients when job contain double byte chars - Fixed issue on Sharp embedded where change to "Copy" when printing would stop print jobs - Fixed error when deploying HP embedded application on some HP firmware configurations - Sharp -- Copy fails with Limit error in display if copying is interrupted - Fixed issue with deletion of nested container and input ports - Improved performance for secondary servers connecting to vendor primaries - print job with document multi-up settings goes in error - Fixed issue with Test all auth providers not showing result in UI - Fixed Universal driver: HD photo images (WDP files) produced by Windows Photo Viewer are not printed correctly - Fixed issue printing certain PDF documents accurately on Ricoh MFD's - Fixed Internal error shown when accessing Access Controls after auth provider has been removed - Fixed issue on some Ricoh MFD's email address of user not showing up in native scan-to-email app - Fixed issue with Sharp booklet printing + folding + stapling - Fixed issue printing on Windows 10 in some high security configurations resulting in I/O error - Fixed issue in PC client and print from Internet Explorer 11 - Fixed issue with printing certain Excel sheets in landscape mode not printing correctly - Fixed Job count incremented by 2 in the Dashboard sometime when user tries to print very large files - Fixed macOS PMC PC client -- only 1 copy printed for the job sent with multiple copies - Fixed macOS PMC PC client -- multicopy print + staple from macOS not printing correctly - Fixed issue with only one copy getting printed when user tries to give a Pull Job with any number of copies - Fixed Mobile QR code release: An error occurred, code: 6 - Resolve port conflict for IPM and DSP API terminal services - User not able to add Access control second time after deleting it once - Fixed print jobs getting cancelled when user logs out automatically from KM device - PDF Reports extracting reports of Totals by device even if user is in Totals by user window - Fixed print jobs getting cancelled when user logs out on a Sharp device - Fixed KM embedded deployment error when pushing embedded with Scan-to-email feature enabled in US region ## 2.5.9 \[2019-05-28\] x Enhanced performance for releasing multiple pull print jobs from embedded clients x Modified permission control on HP embedded, to support single-sign-on with third party apps - Fixed issue deploying HP embedded clients in some network configurations - Fixed issue printing landscape on Konica Minolta MFD's 2.5.8 \[2019-05-09\] + Ability to authenticate in PMC using UserPrincipalName with AD/LDAP + Added support for OKTA LDAP authentication - Fixed issue loading certificates on secondaries under a primary vendor ## 2.5.7 \[2019-04-10\] - Authentication error doing scan if users email has changed recently in external auth provider - Fixed issue with custom Postscript print jobs in some cases being converted causing errors on HP ## 2.5.6 \[2019-03-29\] - Fixed email address of user not showing up in native scan-to-email Ricoh app - Fixed error sending email in Scan to My Email in some configurations ## 2.5.5 \[2019-03-13\] x Improvements to SSL keystore handling on primary servers ## 2.5.4 \[2019-02-28\] x Improved Ricoh embedded deployment support ## 2.5.3 \[2019-02-25\] - Fix for keystore loading for non-root vendor ## 2.5.2 \[2019-02-25\] x Added input and output port cache x Improved loading of keystores for services which run on primary vendor server - Fix for setting PS3 output type when using API on secondary ## 2.5.1 \[2019-02-24\] + Ability to specify group name attribute for LDAP authentication - Fixed issue for users with IE11 not able to view all printers in My Printers Web UI - Fixed issue with printers fail to sync for Azure group membership - Fixed issue when more than 10 authentication providers, only last 10 are shown - Optimized performance for servers with single cores ## 2.5.0 \[2019-02-13\] + Scan to My Email MFD embedded application + Ability to add/list/modify/delete access controls on accounts and containers via the API + Ability to delete input and output ports via API + Ability to import a certificate during installation to establish secure connection to API and for use with internal secure channel + Ability to configure Authentication Providers from API + Ability for a user to self-service choose which input ports to install on their PC + MDM AirPrint Azure Intune support + New Message Service for delivering SMTP email + Public API to get list of printed documents for user + Major print job rendering performance improvements with new Postscript Level 3 + New security feature to require PKI certificate for secondary server installs + Add new rendering backend to remove dependency on CUPS on Linux + Deploy PC Client and printers to Windows workstations with Microsoft Intune + Support Ubuntu LTS Linux distributions + Documented disaster recovery procedure for primary server(s) + Add "Available by default" option for input ports + Ability to select multiple groups/users when adding access controls + Driver and PC client in French and Danish + Ability to release both UniPrint and custom driver on same output port + Performance enhancements for user authentication + Ability to control locked features for HP embedded x Improved load balancing for many servers with offline secondaries x Change primary cluster node cloning logic x Documented process for PC Client deployment on Windows 7 x Documented Azure PostgreSQL configuration x Changed PC Client to not remove printers during sync if no network connection to gateway available x Added support for authenticating against Microfocus IDM via LDAP - Fixed issue with duplicate files in history if offline cache is enabled and both servers are up - Fixed issue with Azure authentication stops working after some time - Expanded Canon embedded client device support - Fixed issue with Wide Area Mobile print failing with mobile service on secondary server - Fixed issue where .local used in domain name is snipped - Fixed 4 hole punching option when printing to certain Sharp models - Fixed issue where unable to send print job when logged in with UPN for Azure AD on PC client - Fixed error "Unable to find output port" when printing from mobile using QR code scanning - Fixed number of copies and collation not working for IPP print protocol - Fixed issue with Sharp client throwing "Terminal Not Found" error when accessed using a DNS --- version: "2026.08.20" variant: "PMC" language: "en" --- # 2020 The following contains a list of notable changes in RICOH PMC. Legend: + Added feature x Improved/changed feature - Bug fixed ## 3.10.0 \[2020-11-27\] + Added Search feature + Added Google as an authentication provider + End of support announcement for PC Client on Windows 7 + Add option in UI to limit API key functionality (admin vs non-admin API keys) + Add ability to restrict API access based on IP address filtering x Updated Sharp embedded client x Updated Sharp client to support OSA 5.5 x Update Sharp embedded to support DNS x Updated Sharp embedded to automatically redirect legacy configuration URLs to new URLs x Updated Ricoh SDK/J embedded client x Updated finishing options for HP devices x Updated finishing options for KM devices x Enhanced XSS protection in Web UI - Fixed translations in Sharp embedded - Fixed issues with Run in Separate JVM - Fixed timeout issue for printing large documents - Fixed cosmetic issue with PC Client for Mac ## 3.9.0 \[2020-10-13\] + Added Remote Update feature for Secondary Gateways + Added ModifyPersonalInformation permission x Updated SAML SSO configuration to include SPID/Issuer x Updated LDAP-S bind use SASL with SSL/TLS-protected connection x Updated Konica Minolta OpenAPI embedded client x Updated HP OXPd embedded client x Updated Java 11 with option to conntrol max heap size - Fixed HP OXPd embedded colour print issue - Fixed HP OXPd scaling issue for small displays - Fixed KM OpenAPI Short ID issue - Fixed KM OpenAPI booklet margins issue - Fixed reporting issue for PC Client jobs in local storage mode for multiple copies - Fixed UpdateUserDetails API issue ## 3.8.0 \[2020-09-09\] + Added Server view for status of Secondary Gateways + Added Integrity Check feature for identifying configuration issues + Added Kyocera embedded client support x Updated Sharp embedded client x Updated Lexmark embedded client x Updated HP OXPd embedded client x Updated Printer configuration for serial number entry in printer details x Updated Client-based authentication with increased maximum token header size x Updated PC Client for dynamic loading of WLAN dll for virtual environments x Update Java version to Java 11 x Updated Transport Layer Security to support TLS 1.3 - Fixed Lexmark embedded Short-ID error - Fixed UI issue with authorise/unauthorise server UI update - Fixed issue in MacOS PC Client for jobs outputting with incorrect settings when offline - Fixed reporting issue for PC Client jobs in local storage mode for multiple copies ## 3.7.0 \[2020-08-06\] + Added Group synchronisation for Client-based authentication x Updated Ricoh SOP embedded client x Updated Konica Minolta OpenAPI embedded client x Updated Konica Minolta IWS embedded client x Updated MDM option to be able to run on PMC Primary servers (on-premise) x Updated PC Client DLLs for Windows 7 (32-bit) x Updated HP Workpath and KM IWS Reporting to include Department x Updated PMC zLinux version for backwards compatibility with RHEL7 x Updated Web UI with server view, tabs and path - Fixed login timeout for Ricoh embedded - Fixed KM OpenAPI embedded for usernames longer than 39 characters - Fixed KM IWS scan issue on IT6 devices for paths containing "\\.." - Fixed authentication error on Sharp embedded - Fixed login error for Ricoh SLNX when password includes "%" - Fixed PMC logs for Ricoh SLNX password issue - Fixed "Color" attribute error in PMC triggers ## 3.6.0 \[2020-07-07\] x Updated Mobile gateway API to retrieve copy, scan and print reporting for downloaded jobs x Improved caching for tree and keystores for improved server start-up time x Implemented database cache pre-loading for all entities x Added keystore initialisation before server start to improve start-up performance x Updated Java8 to latest x Added support for Microsoft Graph API for Azure authentication x Default value for "Use Separate JVM" updated to "off" for unattended install x Updated Lexmark embedded client x Updated HP OXPD client x Added SNMP community name setting for HP OXPD embedded configuration - Fixed overlapping keyboard issue in HP OXPD client - Updated refo file import script with department attribute - Fixed Oracle DB column issue for refo file import ## 3.5.0 \[2020-06-09\] + Added Audit Log to capture user and system actions + Option to create embedded configuration during printer configuration + Card management permission created to specifically enable deletion of Card IDs + Added configuration option for KM IWS embedded UI buttons + Added access to native functions and other apps fo KM IWS embedded x Disabled ability to delete authnetication service from Primary server x Optimised dashboard loading in PMC Web UI for imporved performance x Improved keystore loading logic x Updated API for local user import actions x Inhibit end user offline/online notifications for PC Client - Fixed error message for expired licence - Fixed job auto-deletion issue in cluster environments - Fixed "Unknown Publisher" error message on PC Client install ## 3.4.0 \[2020-04-20\] + Add or remove multiple services on Secondary Gateway + Option to create required ports during printer configuration + Option to add required services during port creation + Added option to disable "Store ad deliver via gateway" option in PC Client + Added "Media Type" option in PMC unidriver x Pre-optimization of print data for improved print speed and quality x Updated PC Client to enhance hostname validation for trusted configurations x Enhanced PC Client certificate selection options x Added retry logic for improved job handling in PC Client (local storage mode) x Added installer option for Oracle DB to skip configuration x Updated permissions for rights on certificate creation and deletion x Changed default value for PC Client Online Certificate Status Protocol to disabled x Updated Jetty to v9.4.27 x Updated CURL to v7.6.8 x Updated PostgreSQL to v9.6.17 - Updated HP Workpath app (v3.3.1) to fix card reader issue - Fixed job auto-deletion issue in cluster environments ## 3.3.0 \[2020-03-10\] + Client-based authentication for Azure and ADFS + MFA authentication from PC Client if using Azure or ADFS + Added disk space check to installer prior to running + Added the option to limit number of cards registered to users + Added description field for printers + Added option for choosing between PDF and PS-\>PDF on MacOS PC Client x Changed management of card ID registration for deleted or amended usernames x Updated embedded API with finishing options x Improved logging for triggers and automations x Added enforcement of output port permission to prevent logging on to MFD x Updated PDF conversion engine x Updated HP Workpath to fix card authentication issue x Updated driver with PDFA conversion option x Updated paper format specification for PC Client configuration x Updated driver for KM for print quality enhancements - Fixed A3 scan to email on HP - Fixed booklet printing formatting on Konica Minolta - Fixed Account ID changing in cluster environments - Fixed error message for Scan to Email failure for KM IWS embedded - Fixed short-edge duplex issue for KM IWS embedded - Fixed conversion for PDF file on PC Client for Mac - Fixed paper format issue for Ricoh Postscript2 ## 3.2.0 \[2020-02-07\] + Oracle database support + Department/group reporting x HP Workpath 3.2 embedded app updated for FutureSmart Bundle 4.10 x Added Print\&Hold feature for HP Workpath app x Updated UI for HP Workpath app x Additional Role to view One-time password x Configurable log level via UI x Many improvements to print driver performance and print job rendering x Migrated logic from PMC Server to PC Client x Added Postscript 2 option x Enhanced security around passwords displayed in Web UI x Added device family support for Xerox printers x Improved performance on log retrieval from Secondary Server - Fixed wrong version of PC client being shown Web UI - Fixed My profile page not shown correctly for users with disabled \`ViewUserInputPorts\` permission - Fixed API token field still has a value when edited - Fixed SLNX Share Embedded reporting issue when using card login - Fixed issue with margins being cut off - Fixed issue with lost print jobs if gateway not available - Fixed card authentication issue for HP Workpath - Fixed scan to email issues for HP Workpath - Fixed KM IWS scan to email issue - Fixed KM IWS number of copies not being inherited - Fixed KM IWS auto-logout issue - Fixed missing characters on print from Ricoh devices - Fixed collation issue with Ricoh IMC devices - Fixed booklet print issue with Xerox device - Fixed reporting issue with PC Client for Mac - Fixed changes in DocOut service not propagating to output port entity caches --- version: "2026.08.20" variant: "PMC" language: "en" --- # 2021 The following contains a list of notable changes in RICOH PMC. Legend: + Added feature x Improved/changed feature - Bug fixed ## 3.18.4 \[2021-12-21\] Core x Log4j upgraded to version 2.17 ## 3.18.3 \[2021-12-16\] Core x Log4j upgraded to version 2.16 KM IWS Embedded - Fixed card reader login errors with card readers being removed \& not being detected + Update to allow OpenAPI \& IWS devices to read card numbers in the same way ## 3.18.2 \[2021-12-11\] Authentication - GSuite Connection Fix - Fixed authentication errors on UK Clusters - Addressed password issue on Canon devices Core + Debian 11 Support x Backported OneQ terminal configuration library x Log4j critical vulnerability fixed HP OXPd Embedded x Update HP OXPd client to the latest libraries, build tools \& IDE - Fixed screen resolution detect error Kyocera Embedded - Fixed Simplex printing Ricoh SOP Embedded x Updated error messages x Updated Spanish translation on Device UI - Fixed Unknown Terminal error post configuration - Fixed issue with Custom Certificates PC Client + HP "Print from USB" Performance x Update Java JRE to latest Java 11 x Cache improvements UI + Ping/Azure Group Sync Prompt x Primary EU search updated to allow searching from the root account x Search, Delete \& Sort options added to Endpoints page on Web UI x Updated French translations on Web UI x Updated German translations on Web UI ## 3.17.2 \[2021-11-19\] x Updated keystore request handling ## 3.17.1 \[2021-11-11\] x Updated thread pool allocation for AutomationTask - Fixed issue with Azure permissions for SSO - Fixed issue for LDAP user with group access control gets "Invalid credentials" error when logging into printer ## 3.17 \[2021-11-04\] Licence x Updated logic for applying licence for Azure user not yet created in PMC Core + Added data model for Named User Profiles Sharp x Updated Sharp embedded client for improved scaling on different screen sizes Search + Added Search by Account ID + Added Search by servers + Added Search by domain PC Client + Added command line switch for Offline Printing for remote installation x Updated PC Client for installation of MacOS version 10.14 and earlier x Updated French translations errors in PC Client - Fixed issue with locking PC Client to local storage mode Performance x Updated thread pool creation for Automations UI x Updated French translations in WebUI Endpoints x Updated French translations in WebUI Reporting - Fixed issue that allowed addition of blank customer to vendor ## 3.16 \[2021-10-13\] API + Extended API with Documents History x Extended logging with API Request Rate metric x Added filtering for URI parameter in /gateway/endpoint for imporved security x Updated DSP API Authentication + Added Ping authenticaiton to available PMC Authentication providers x Updated logic to expire unauthenticated sessions faster x Improved logging for card authentication using client authentication for expired users x Updated internal messaging despatcher settings to improve performance - Fixed issue with blank page displaying after successful authentication with Azure AD HP Workpath Embedded (pending upload to HP Command Centre) x Improved printing speed for complex jobs stored in cloud on HP Workpath - Fixed stapling finishing option when using cloud storage for HP Workpath KM IWS Embedded + Added option to remove Copy button from IWS Embedded for SFP devices support x Enhanced logging for application errors x Implemented fallback to English translation if language pack not installed x Updated Swedish translation x Enhanced user feedback when printing is complete - Fixed issue with scan error if filename contains special characters Ricoh SOP Embedded + Added mandatory flag for device username and password in Ricoh embedded configuration x Updated logic for reading card IDs for case sensitivity x Removed Ricoh branding from Ricoh SOP embedded client x Updated German translations - Fixed issue with incorrect branding being displayed if configuration cannot be loaded - Fixed intermittent 403 error while deploying Ricoh SOP - Fixed mismatch error with version number in Extended Info feature on printer Xerox Embedded x Updated VendorName to prevent installation errors on some Xerox devices Installer x Updated installer logic for Linux version detection Messaging x Updated TLS version for emails sent using triggers Mobile - Fixed ouput options override issue for output release from Mobile app on Android PC Client + Added support for Apple Silicon (ARM) M1 processor devices + Added Offline Push-Print option for PC Client in local storage mode + Added client-based authentication with Google + Added client-based authentication with Ping + Added German language x Updated PC Client front-end technology x Improved PC Client synchronisation when network status changes x Updated icons for PC Client x Updated client-based authentication to use OpenID connect x Improved Terminal Services/Remote desktop notifications x Improved logging for network-related issues UI + Added active/expired state of users with client based authentication x Updated customer user expiration field with input validation x Increased timeout for UI relay for long-running request x Deprecated ADFS client identity type in PMC provider settings x Updated to sort printers for Push ports in alphabetical order - Fixed UI issues with newly created items not always displaying immediately - Fixed incorrect version number in server view after upgrade - Fixed cache issue with Access Controls - Fixed intermittent issue with PMC Portal Internal error when downloading logs ## 3.15.5 \[2021-09-23\] - Fixed issues in UI where newly created/updated/deleted items may be displayed inconsistently ## 3.15.4 \[2021-09-09\] - Fixed cache issue where adding Access Controls on a Vendor could make child items disappear temporarily - Account without language/locale set fails to load ## 3.15.0 \[2021-09-03\] + Added support for Brother embedded devices + Added search by card ID for users + Added Dutch language + Added German language + Added Spanish language + Added integrity check for service used by offline Secondary Gateway + Added integrity check for Access Control + Added integrity check for domains within multiple authentication providers + Enabled DOS filter by default + Added source request IP address in URI filter to Debug log + Added input validation for SSO XML Metadata URL field + Added Ricoh branding for installers x Enhanced performance for dashboard loading x Added paging to retrieve more than 200 groups for Google Authentication group sync x Updated UI to retain selected language as default x Updated Terminal Service API to be compatible with custom certificates x Updated logging to include server metrics x Updated HW ID for PMC printers in Windows x Updated workflow for "Download\&Print" for local storage mode x Updated logic for PC Client connection/disconnection events - Fixed PC Client version mismatch in UI HP Workpath + Added Spanish language support x Updated Workpath to SDK v1.5.0 x Updated Android to SDK v29 for compatibility with SDK v1.5.0 x Updated manifest files x Updated application with check for valid server host before getting configuration x Updated application with check for cached printer configuration x Updated logic to load configuration screen if cache is empty x Simplified card reader service start x Updated error handling for logout workflow x Minor UI improvments x Updated logging information - Fixed issue with card authentication after reboot - Fixed issue with "Failed print job" message when job printed correctly - Fixed issue with Scan to My Email button being displayed when disabled in configuration - Fixed issue with "Loading configuration" message remaining on display - Fixed issue with card swipe failure requiring multiple swipes or device reboot - Fixed error when new card is swiped - Fixed issue with "B\&W" trigger not being actioned with PC Client in Gateway mode - Fixed issue with Workpath app intermittent failure on FW 5.1.0.1 HP OXPd - HP OXPD: 'Install and configure' issue is fixed - HP OXPD: colour print issue after the client installation no longer appears - HP OXPD: application is no longer getting stuck after log in KM IWS + Added Polish language + Added Swedish language + Added Norwegian language + Added Compact Scan option to IWS embedded x Improved pull print mechanism to execute jobs in background and check and display status x Added multi-part data transfer for scan jobs - Fixed Duplex copy issue - Fixed Script Access Error for Copy when paper tray empty - Fixed tray selection issue for copy job - Updated French language translation errors - Fixed Incorrect duplex parameter from IWS record job - Fixed memory issues when printing - Fixed issue when user is automatically logged out during multiple print jobs and printing stops - IWS -- Download and Print -- fixed issue with "Preparing job" displayed until printer enters sleep mode - Fixed issue in print processing view when IWS server is not reachable (Note: "Server not reachable" error message relates to IWS server and not PMC -- error message should be updated to reflect) - IWS -- Month in the default scan file name is wrong - Fixed scan job runs out of memory errors - Fixed Scan failed and after MFD reboot all docs are sent to the last logged in user issue - Fixed issue with display showing "STOPPED" until printer enters sleep mode when paper jamis forced in document feeder - Fixed UI issue when user has a longer username - Fixed stapling issue not being applied when printing in the gateway mode KM OpenAPI + KM Open API: Added APACH region support ## 3.14.0 \[2021-05-17\] + Case-insensitivity for usernames added to PMC PC Client + Added option to trim control characters from card # on PMC OXPd + Several process pop-ups and user feedback added to Ricoh SOP Embedded UX + Added Automatic SP Mode configuration on device for Ricoh SOP Embedded installation + OSS licensing information added in Server and PC Client + Added German language to the driver x Improved error messages on Chrome Extension x Improvements to backend reporting x Improved Load balanced service handling when filtering for distinct service/server combinations x Logic and behavior of the refresh button on Ricoh SOP has been improved x Improved French and Dutch language fixes in Ricoh SOP Embedded x Card enrollment logic on Sharp Embedded has been updated x Improved Swedish translations in Sharp Embedded x User handling for users with same username in different authentication providers has been updated x Improved rendering for PDF's with signature x Minor Improvements for PMC Web UI x Performance enhancements made for PMC Web UI - Fixed issue with login and sync of printers in Chromebook - Fixed issue with cluster membership of gateways or PC clients after irregular connection loss - 'Unknown Terminal' Bug in Ricoh SOP Embedded fixed (Please see updated Manual) - Issue with Scan to Portable USB Storage on Ricoh SOP Embedded is fixed (Please see updated Manual) - Cosmetic issues on Ricoh SOP Embedded has been fixed - Issue with Logo image quality on Sharp Embedded has been fixed - Fixed issue with movable UI on Sharp Embedded - Issues with generating QR code is fixed - Fixed issue with ignored provider ID when retrieving a list of documents for a specific user ## 3.13.0 \[2021-04-08\] + Display "Offline" status in job list on embedded for offline jobs + Added IPP authentication option and validation to account settings + Added support for Ubuntu 20 LTS + Added ability to load XML Metadata from a file in non-default conf location + Added support for HTTP strict transport security x Improvements to intercluster communication x Improved account-servers view for ease of use x Optimized PMC Web UI response and performance x Changed logo upload size to max 200kb x Improved error messaging for location adding and editing locations x Added input validation for allowed IP's in API access key x Added httponly flag for cookies x Updated x-frame options for protection against Cross-frame scripting (XFS) attacks x URI upload is no longer supported for documents end point x HTTP TRACE / TRACK Methods disabled x Security improvement preventing concurrent sessions by same user in PMC x Improved performance on user import x Enhanced WorkspaceeONE/AirWatch compatibility for Ricoh Mobile APP x Optimized logic for HP Workpath Embedded for enhanced card reader experience x Discontinue use of port 7310 (Only relevant for PMC 2.x server version) x Updated content security header (CSP) x Updated x-content-type-Options - Fixed UI timeout issue for high volume group sync with Microsoft Azure OAuth2 authentication - Fixed issued with landscape mode from bypass tray on Konica Minolta - Fixed issue with staple logic for landscape documents - Fixed issue with triggers for manual tray selection - Issue with French language in Xerox Embedded fixed - Updated Ricoh SLNX Share API to to display job properties correctly - Fixed Ricoh SLNX Share API mapping for short-ID authentication - Fixed issue with private cloud update for primary and secondary server types assignment - Fixed issue with embedded UI to show documents as "Offline" when document storage is not available - Fixed issue with Chrome Extension user authentication token expiration - Fixed issue with Chromebook extension rejecting certain symbols in the password - Chromebook extension issue where print queues did not automatically synchronize at login fixed ## 3.12.0 \[2021-03-11\] + Added password policy option for local users + Added API key expiration options + Added support of POST on public API /login x Optimized authentication lookup process for card authentication x Optimized port/service preloading x Updated required rights for Azure Authentication provider x Updated Default Permissions for User \& Reporting - Updated PMCUpdater component directory usage for remote install on Private Cloud - Fixed issue with User token acquisition - Fixed XSS prevention in My Printers screen PC Client: + Added connection check prior to submitting print jobs x Added signature for uninstaller x Optimised channel disconnection protocol when PC goes into standby mode - Fixed Unattended installation problem with macOS PC Client on Big Sur - Fixed reinstall issue macOS PC Client on Big Sur - Fixed issue with trigger generating Short ID when not set Chrome Extension: + Enhanced Chrome Extension with user_token security + Option to bypass login in Chrome extension - Chromebook extension test connection error message updated Canon Embedded: + Support for new canon devices + Added support for DNS configuration HP OXPd Embedded: x Update HP OXPd to FutureSmart 5 SDK 1.8.2 x Updated Scan to my email OXPd for 'Ballpark device' compatibility x Updated OXPd UI to fit "Ballparks devices" - Updated OXPd to use legacy UI for devices not able to render the updated UI - Failed history purge bug fixed - Queue fails to remove document name from queue after printing in offline mode - Optimized authentication response timing - HP OXPd Refresh button optimized Konica Minolta IWS embedded: + Add language options for French, Danish and Dutch language Konica Minolta Open API: x Updated Dutch language translations Lexmark Embedded: x Updated French language translations - Pull Print icon not showing up on Lexmark printer after embedded installation on new devices Sharp embedded: - Fixed card-enrollment issues for wrong username Xerox Embedded: + Added TLS v. 1.2 for Xerox devices that can use TLS 1.2 x Modify Dutch text in the Xerox embedded x Embedded French Translation on Xerox Embedded enhanced - Pullprint app did not show after pushing embedded on Xerox AltaLink C8055 - Xerox Altalink C8170 configuration issues fixed ## 3.11.0 \[2021-02-06\] + Added option to sign SAML requests with private certificate chain + Added option to import xml metadata for SAML SSO + Extended API with token-based authentication for additional security + Extended permissions for API keys + Added option for API key to utilise unauthenticated requests + Added option for API to allow untrusted endpoints + Added option for API keys to automatically trust endpoints + Added option for API keys to be restricted to allowed IP ranges and subnets + Added new Endpoints view and Endpoint data model + Added ability to change filename to KM IWS scan + Added user token security to KM IWS embedded + Added permission for hiding "propogate to child node/reset child nodes" x PC Client for Mac signature updated x PC Client updated to allow installation without active connection to PMC x Updated PC Client silent installation configuraton with certificate selection by issuer x Added check for duplicate short ID on user creation x Updated UI to indicate when job storage is not available on embedded job list - Update dropdown width scaling issue for Chrome browsers - Fixed UI issue for IWS Scan to Email view - Fixed SAML redirect issue --- version: "2026.08.20" variant: "PMC" language: "en" --- # 2022 The following contains a list of notable changes in RICOH PMC. Legend: + Added feature x Improved/changed feature - Bug fixed ## 3.28 \[2022-12-15\] API x Device code workflow requests changed from GET to POST. x Device code workflow: the public/private keys are optional now. x Simplified registration of new endpoints (printers, gateways, software clients, etc), usage of client-side keys is now optional. PC Client + Added ability to install PC Client in local storage mode while being offline. x PC Client is now compatible with cloned Windows images. x Implemented offline mode registration in the core service. x Added offline mode selection in the installer. x The default paper size for printers is set based on the user-selected locale. x Temporary files are now written in the service data directory instead of the Windows temp directory. x Added client UUID display in the about dialog. x Added authentication type in the service setup dialog. - Fixed trigger execution when custom capture variables are used. - Fixed PC client Windows installer UI on HiDPI displays. - Fixed compatibility with IWS cloud print. Lexmark + Added Lexmark eSF7 device compatibility. x Implemented alternative Login method. x Home screen displayed after authentication on Lexmark. + Added Refresh Button for Lexmark Job List. ## 3.27.3 \[2022-10-08\] Core - Fixed a problem with PC client and gateway communication when they reconnected to the same cluster node ## 3.27 \[2022-10-06\] API x Prevent locations being created/updated using wrong values Brother + Added uninstallation option for Brother application + Advanced scanning options added + Automation of IP Setup configuration x Removed IP address from Scan2Email subject x Improved UI for copy \& scan options x Improved error message on login fail x Improved reporting for scanning Core x Enhanced security for channel messaging on secondary servers Licensing - Resolved crashing of license counter update PC Client x Prevent users from printing once logged out x Reinstated ability to switch to PDFA setting Security x Prevent login of unauthorised users to Primary Gateways via URLs UI + Addition of confirmation window when entering non-unique printer address UniDriver + New Paper Size: 170mm (width) x 210mm (length) ## 3.26.1 \[2022-09-30\] Core - Resolved connectivity issue between PC Client \& Gateways ## 3.26 \[2022-09-08\] API + Add Owning Container ID for Input Ports \& Outputs Ports Authentication x Improved token refresh for multi domain Azure authentication providers - Resolved Ricoh SLNX card enrolment error using OTP Core x Correct routing of print jobs to device where it shares an IP address with another device Installer + PMC ARMv7 Support to accommodate future integration with YSoft hardware devices KM OpenAPI x Code cleanup to improve maintenance \& scalability x Replaced legacy API EasyTools with CoreAPI x Removal of old login screens from being displayed x Prevention of app crash when delete/refresh/print buttons are pressed multiple times PC Client x Resolved unnecessary sync events due to PC network changes Sharp + Upgrade to Sharp OSA 6 + Auto population of installation forms on deployment + Pop-up for credential validation on card authentication + Display "Logging in" message on submission of authentication + Add button to release multiple PullPrint copies x Display home screen on login if no pending jobs exist for the user x Prevent button press whilst Print Job List is being refreshed - Prevent multiple logins on authentication ## 3.25 \[2022-08-04\] Authentication + Deletion of Azure/LDAP user records via PMC Web UI Lexmark x Use of PMC CA generated certificates - Resolved device crash upon card enrolment PC Client x Improved authentication token refresh following extended offline periods Reporting + Group \& Department information available in Job History Reports API API + Display Domain ID for listing Containers, Input Ports \& Output Ports + Display Location for listing Containers Authentication + Multi domain support for authentication providers + Use refresh tokens for service accounts for Azure Authentication + SSO support for Strict Domain Validation ## 3.24.1 \[2022-07-22\] Security - Reinstate TLS ciphers removed in 3.24 to support PC Clients run on older versions of Windows (8.1 \& 12) ## 3.24 \[2022-07-12\] API + Display Domain ID for listing Containers, Input Ports \& Output Ports + Display Location for listing Containers Authentication + Multi domain support for authentication providers + Use refresh tokens for service accounts for Azure Authentication + SSO support for Strict Domain Validation KM IWS + Italian Language Support + Audio feedback on button press + Duplex \& Stapling options for Copy function + Support for Develop devices x Removal of Zoom option from Copy function x Improved error message for incorrect copy options x Increased timeout for printing to accommodate large print jobs - Resolved Chrome Extension printing issues KM OpenAPI + Removal of file names on URLs when accessing files on application x Cookie-based tokens updated to use "http-only" Kyocera x Support for smaller screen devices - Resolved 500 error when switching customers on the same vendor - Resolved 404 error on device restart Rendering Engine + Booklet printing for Ricoh Devices Security + TLS 1.3 Support x Disabled TLS 1.0 \& 1.1 on port 9444 + Update of TLS ciphers to address reported TLS vulnerabilities UniDriver + Support for paper size 180mm (width) x 210mm (length) ## 3.23.1 \[2022-06-16\] PC Client x Remove the requirement for case sensitive domain names for PC Clients in local storage mode ## 3.23 \[2022-06-08\] Authentication x Prevent multiple authentication attempts for incorrect credentials - Resolved OTP login locking Azure account on multi node environments Core x Upgraded handshake protocol between Primary \& Secondary Gateways PC Client x Update handshake protocol with gateways for local storage mode x Prevention of printing for accounts with expired licenses Xerox -Resolved configuration error when deploying to Xerox Altalink devices ## 3.22.1 \[2022-05-20\] Sharp - Resolved critical error with application not being operable ## 3.22 \[2022-05-12\] API x Update of Input \& Output Ports via Public API now possible with id field - Resolved issue with deletion of accounts \& containers in Public API Authentication x Replaced MS Azure ADAL with MS Azure MSAL Brother + Duplex \& Color copy options + Advanced options for Duplex, Color \& number of copies for print \& copy jobs + Print job list is refreshed each time it is accessed + Copy statistics available in PMC Web UI Reports x Configuration lookup now performed under address 127.0.0.1 - Resolved issue with card enrolment with Azure Oauth2 - Resolved issue with username \& OTP authentication with Azure logins - Resolved an issue with the copy function instability Core x Updated logic for gateway certificate expiration check x Additional logging added for time out events Embedded Clients - Resolved issue with Install \& Configure not working as expected HP OXPd x Print jobs are no longer displayed on the print job once complete Kyocera - Resolved issue with 500 error displaying after authentication Lexmark - Resolved issue with slow authentication \& print jobs - Resolved local user being deleted after embedded application installation PC Client + 1-click download of PC Client logs \& configuration x Updated installer screens to have consistent language for fields required - Resolved scaling issue on Installation Configuration window - Resolved token expiration notification not displaying Sharp x Configuration lookup now performed under address 127.0.0.1 x Card enrolment timeout increased to 120 seconds UI + Reset Child Permissions option for Account Control added UniDriver - Resolved renderer failure error Xerox x Updated Java Spring library to latest version - Resolved issue with IPP printing ## 3.21 \[2022-04-05\] Authentication - Resolved issue with LDAP not working over SSL for containers Brother x Display the PullPrint application even if there are no jobs pending x Display of username on application for local users x Ensure all print jobs are removed from the job list once complete x User is automatically logged out if the device is powered off - Resolved an issue with the copy function not loading - Resolved an issue with "print or delete queued jobs" button disappearing Chrome Extension + Checking for internet connection before attempting to connect to PMC server + Warning message if there is no connection + Windows style notifications from Chrome Extension for desktop x Allow authentication by either PC Client or GSuite credentials x Improved messaging if invalid credentials are input on login HP OXPd - Resolved a 500 error appearing on pressing delete multiple times KM OpenAPI - Resolved card enrolment not working with username \& password/OTP Performance x Update to performance of job retrieval function for Ricoh SLNX, HP Workpath, KM IWS \& mobile apps Ricoh SOP x Allow Ricoh SOP to be installed with either short id or username/password authentication option x Automatic login following card enrolment with username \& OTP x Increased stability following log out after printing a document x Increased stability when swiping on the job list screen x Improved document name on the job list for longer document names x UI update for alignment of headers on job list x Printing continues following logout if jobs are still in the queue x Ricoh RXOP module updated to version 3.8.7 - Resolved an issue with duplicate printing on job release via card swipe - Resolved an issue with the wrong date \& time displayed on the print queue - Removed "Please wait" message on login when no jobs are in progress Sharp x Reduction of memory consumption on gateways to increase stability UI x Improved handling of closing windows \& pop-ups to remove JavaScript errors x On deletion of accounts, users are asked to enter the account name, replacing the previous checkbox ## 3.20 HP Workpath Release Only \[2022-03-17\] HP Workpath + French Language Support + Italian Language Support x Resolved app crashing issues related to HP 5.3 Firmware (Note: device must be upgraded to HP 5.4 firmware) x Improved printing performance for download \& print of large documents x Resolved stapling issues with gateway mode for PC Client ## 3.20 \[2022-03-08\] API + Additional functions for Public API (See API documentation for additional details) x Check for duplicate domains when creating an account Brother x French Language updates Core x Migrate document conversion library to Mako SDK PC Client + Italian Language Support + Dutch Language Support - Fixed issue with short ID/OTP not being sent via Office 365 on local storage mode Performance + Additional database indexes added x Refactoring of caching for improved performance x Updated thread pool for channel messaging - Fixed caching issues for propagating/resetting child permission UI + Italian Language Support + Dutch Language Support x Prevent deletion of own root account x Separate domain names onto new lines x The dashboard will display a message rather than a loading icon to allow you to access other areas of the account whilst the dashboard is loading. - Display correct timezone for Australian print jobs - Display correct days on Print Activity dashboard Xerox + "Authentication UI Language" configuration option added in PMC UI x French Language Updates x Prevent duplicate sign in on Versalink/Altalink x Updated server address configuration to always use localhost - Fixed card enrolment issues - Fixed issue with being able to login following an uninstall - Fixed issue with WebClientNG not locking/unlocking on Versalink ## 3.19.1 \[2022-02-11\] Core x Additional logging to identify performance issues ## 3.19 \[2022-02-04\] API + Additional functions for Public API (See API documentation for additional details) + OTP connection type for Ricoh SLNX Authentication - Reduce auto logout occurrence for Azure Oauth2 Core x Auto reconnect for secondary gateway after connection reinstated x Deletion of jobs from spooler folder on job expiry x Disable triggers failed with incorrect exit condition x Log \`BootstrapCompleted\` event with INFO level x Upgraded protobuf library - Fixed fwutil application missing after updating PMC Gateway HP OXPd + Exit button added to device UI x 127.0.0.1 now used for configuration lookup - Correction of Duplex \& Mono behaviour when selected - Fixed Card enrolment/login issues KM IWS - Removal of APAC region for Embedded Configuration Mobile - Android Mobile layout fix for Job \& History list screens PC Client x Passwords with characters å ä ö now accepted x Added additional retries for setting default printer for offline direct printing - Fixed printing issues following gateway mode change - Fixed issue with no location available and local storage printing - Fixed Event 1000 windows crash error - Fixed issue with PC client not disconnecting following unauthorisation of user Performance x Additional database caching Security x Log4j upgraded to version 2.17.1 x Security update for DEBUG logging to remove sensitive information UI x API Keys masked by default x Asterisks displayed for mandatory fields on all forms - Fixed "my printers" view responsiveness on EU Prod UniDriver x Updated PMC Driver for use with Accessibility Tools Xerox Embedded x Updated French Translations on device UI - Fixed configuration issues for Xerox 7545 --- version: "2026.08.20" variant: "PMC" language: "en" --- # 2023 The following contains a list of notable changes in RICOH PMC. Legend: + Added feature x Improved/changed feature - Bug fixed ## Build 3.39.7 \[2023-12-01\] **Primary Server** - Added authentication performance enhancements. - Fixed PDF print over IPP affecting bespoke configurations. ## Build 3.39.5 \[2023-11-27\] **Primary Server** - Introduced caching to address slow requests for selected secondary server deployments with LDAP authentication enabled. ## Build 3.39.3 \[2023-11-24\] **Primary Server** - Optimized User Authentication Caching. - Optimized document retry tasks for improved performance. - Optimized automation tasks. - Added additional metrics logging. ## Build 3.39 \[2023-11-02\] **Web UI** x Improved user experience of the Print queues menu. x Moved PMC Client download to My profile screen so that the end users can access the pre-configured PMC Client. x The Server information tab for a Secondary Gateway was redesigned for easier administration and configuration. - When clicking a server in the left navigation menu, the server details are now displayed correctly. **PC Client** x The PMC Client now performs printer synchronization less often. - Silent install sets all parameters correctly when color, duplex, or paper size is specified. - The PMC Client is updated with Ghostscript 10.02 to resolve the CVE-2023-38545 and CVE-2023-38546 vulnerabilities. **Authentication** x Added the ability to track how long authentication takes for specific authentication providers if a user is authenticated by multiple of them. x OIDC is now compliant with RFC 8414. - For customers with multiple authentication providers, the amount of PMC Client failed authentications has been decreased. - Azure AD authentication provider now handles custom extension attributes correctly. **Scanning** - When disabled, the OCR Output parameters are not saved in the workflow settings in the PMC Web UI. - The Reorder button is now visible only to users with ModifyScanWorkflow permission. **Performance** x To further reduce the load on DB, calls to UserFacade are cached (especially the findByName method that is used in hot queries). - NullPointerException no longer occurs in the document facade when the document is linked to a non-existent printer or provider ID. **Ricoh Cloud Terminal (Gen2)** + Users can select one or multiple jobs for deletion. + User can manually refresh the job list while at the MFD. + The Job list shows job attributes (Colour/B\&W, Number of pages, Number of copies). + The terminal deployment via Secondary Gateway has been improved. + The terminal can be deployed via the Ricoh App Store (Pending availability on the Ricoh App Store). + The terminal can be manually configured at the MFD by an admin as the admin now can enter the Domain and the API key manually. + The terminal installation status is shown in the PMC Web UI. x A meaningful error message is shown when job retrieval fails. x The Registration and Authorization messages are now brand-neutral. x Admin gets proper feedback when entering wrong credentials during uninstallation on G2 devices. x The automatic user logout now works correctly when the MFD goes into sleep mode. x Users without rights to print can no longer open the print application on G2 devices. x Admin users can now log in using the native login button as this button redirects them to the authentication screen. x During terminal uninstallation, the User Authentication Management is set back to OFF. x If entering credentials during card activation times out (takes over 60 seconds), the user is returned to the login screen instead of being shown the error message "You have placed unknown or damaged card." x The RXOP library is updated to version 3.8.8. - Fixed issue with jobs taking too long to print if PJL headers are not present. - Fixed issue with jobs being released from Secondary Gateway storage showing error Status code 404. - The terminal no longer crashes during manual installation. - SP option SCAN_SETTINGS__PRINT_DELETE_SCANNER_JOURNAL is correctly set on installation so that scanning is not blocked when the device scan journal is full. - G2 devices no longer require a manual reboot after terminal installation. **HP OxPD Terminal** - The page count is correct when printing multiple copies of a print job sent via IPP Pull Print to an HP MFD with OxPD terminal. - When a document is not printed within the maximum expected wait time after a user taps Print, the document's release is canceled. **Konica Minolta IWS Cloud Terminal** x Scan jobs can be merged when the Merging originals option is enabled in the scan workflow settings. x Added the support for booklets. - The terminal respects stapling when using pull print. **Konica Minolta OpenAPI Terminal** - When using the KM PCL6 Universal Print driver, the page count is displayed correctly. **FujiFilm BI Cloud Terminal** x The users can now use basic workflow settings at the MFD. ## Build 3.38 \[2023-10-05\] **Printing** - Fixed issue on secondary servers causing documents to be rejected when using offline caching. - Delegated print jobs can now be released at Pure Cloud Terminals. + Added the ability to set the default page size per print queue. **Scanning** - Removed SMTP configuration from Embedded client configuration for Pure Cloud terminals, as this setting is unnecessary. - Added exception information to WPS logs for failed scan processing jobs. - Added validation for SharePoint connector where Target SharePoint online library is a required field. x Added the ability to download failed scan jobs. **Web UI** - When clicking on the documentation link, the admin is directed to documentation branded for their variant of the product. x The theme of the login screen is now modifiable, and the navigation in the tree structure is improved. **Chrome Extension** - Chrome extension no longer removes printers and configuration when clicking test or when a blank api field is used. **Mobile apps** - Removed dependency on external barcode scanning app by embedding its functions in the Android app. - Print jobs submitted via the Mobile apps can now be released on KM Cloud Terminal even if they originally did not contain PJL headers. **Fujifilm BI Cloud Terminal** - Scanned documents are correctly accounted for even if the user uses the native copy application. x Added the ability to print booklets. x Added ability to account for scanned documents. **Canon Embedded Terminal** - The login screen no longer freezes after attempting to log in with invalid credentials. **Sharp Embedded Terminal** - The terminal can now display more than ten print jobs. **Xerox Embedded Terminal** x Login at Xerox Embedded Terminal no longer fails when secondary servers are configured with multiple CPUs. **Konica Minolta IWS Cloud Terminal** x Direct print jobs no longer create duplicate entries in the printed documents list. **API** x Added the ability to manage access rights. x Improved security of document history API by adding role-based access. x Increased security by only displaying API keys once when generated. The ability to view existing API keys is removed. ## Build 3.37 \[2023-09-07\] **Ricoh PMC Advanced Embedded Terminal** - Fixed issue with blocked ports which prevented successful installation of the Ricoh PMC terminal using YSoft OMNI Bridge. **Scanning** + PMC Web UI updated so that administrators can see that they can use workflow variables in workflow fields. x Scan files that failed during workflow processing are stored for 7 days and can be downloaded from My Documents in the PMC Web UI. x Improved notifications for administrators when a scan job fails. - A user who has not yet submitted any print jobs can see My Authorisations in the PMC Web UI and can authorize connections to Microsft365 applications. **Konica Minolta IWS Cloud Terminal** + New Konica Minolta Terminal for Konica Minolta IWS devices. + Cloud printing with no requirement for a Secondary Gateway. + Users can log in to the MFD via username and password (or OTP), PIN, or card. + Users can register their card at the Cloud Terminal terminal. + Users can access Print and Scan workflows in Quick Actions upon login. + Users can select and print one or multiple jobs with finishing options applied at job output. + Print jobs can be released from any configured storage location (PMC Client, Cloud, or Secondary Gateway storage) and will be routed to the MFD in the most efficient way. + Users get feedback on print job status (e.g., Waiting, Printing, Downloading, Downloaded and Printing). + New scan workflows are available in the Cloud Terminal UI. + Users can scan to email, Microsoft OneDrive, and Microsoft Sharepoint. + Users can access Quick Copy from My quick actions screen. + Administrators have instructions for deployment in the Embedded configuration section of the PMC Web UI. + Administrators can set configuration options for the terminal. + Administrators can register the cloud terminals in PMC. + Administrators can install the Cloud Terminal from Konica Minolta Marketplace + Administrators can pre-configure multiple MFDs for installation from Konica Minolta Marketplace. + Logs are stored on the MFD and can be retrieved remotely via Konica Minolta Marketplace. **Ricoh Cloud Terminal** + Ricoh Gen2 terminal can be deployed from the Secondary Gateway. **Fujifilm BI Cloud Terminal** + Users can delete print jobs at the terminal. + Copy and scan jobs are accounted for and can be viewed in the PMC Web UI in Reports. **Sharp OSA Terminal** - The Print button is no longer hidden behind print jobs when there are multiple jobs in the list. **HP OXpD Terminal** - A new option was added to PMC Web UI to enable driver (sotware) copy collation so that printing multiple copies works correctly. **Public API** - Adding authentication providers using API (/authproviders) now works correctly. **Authentication** - Azure AD client now handles the AAD on-premise extension attributes in a special way so that administrators can store card numbers stored in Custom Attributes (e.g., extension attributes such as extensionAttribute1). **PMC** **Web UI** x The action buttons in the top menu bar are now grouped. x Workflows now open in edit mode by default, reducing the number of steps required to create or update configuration items. - Certificate expiration dates are now displayed correctly. **OMNI Bridge** x Landing page from the device's QR code is used to enroll the device in PMC. **PMC Client** + Administrators can download the PMC Client from the Print queues section of PMC Web UI. x The PMC Client icon now has neutral branding. **Server** - Fixed intermittent authentication issues in EU due to connecting clients overloading the cluster after restart. **Localization** - Updated incorrect French translations for ID in Users. - Updated incorrect Dutch translation of About in PMC Client. **Security** x Updated backend API key security. x Added AUD (audience) claim to API access tokens for improved security. x Updated JRE version to Version 11.0.20 ## Build 3.36 \[2023-08-10\] **Ricoh PMC Advanced Embedded Terminal** - Fixed issue resulting in error when deploying Ricoh PMC Advanced Embedded Terminal from Secondary Server.**Scanning** + Documentation link added to the navigation bar. x User and admin are notified if workflow processing fails to start. - OCR improvements for large jobs. - In scan workflows, it is now possible to change the *From* address. **Web User Interface** x Alerts moved to Overview. x Admins can see the status of the gateways in the Web UI. x Cloud Terminal Installation status is displayed in the Web UI. - Corrected French translations. **PMC Client** + Added text with the Client's status next to the Client's icon. x Simplified the installation and configuration of the Mac Client. **Konica Minolta IWS Embedded Terminal** (This feature is in testing, not general production) + The terminal now has the scanning functionality. x Print jobs are delivered more effectively. **Terminal Deployment Tool** - The password parameter is now always visible in the command. **HP Workpath Cloud Terminal (Gen2)** - The terminal now supports Y Soft Card Readers. ## Build 3.35.2 \[2023-07-25\] **Core** - Fixed issue related to automation tasks resulting in reduced server performance. ## Build 3.35.1 \[2023-07-19\] **Ricoh Cloud Terminal (Gen2)** - Fixed issue during card enrollment for new cards displaying the unknown or damaged card error message. ## Build 3.35 \[2023-07-13\] **Ricoh PMC** + Added additional capability to set print job status via API. - Fixed issue when refreshing user token via secondary server. **Printing** + PMC Client now has the ability to send a username to the MFD when the print protocol is IPP. - Improved speed of print job display for embedded terminals connected to YSoft OMNI Bridge - Cloud Terminals can now print correctly when the selected paper size is Ledger. **Scanning** + Administrators can add scan metadata to Sharepoint Scan workflows. + Administrators can configure file overwrite behavior for OneDrive and Sharepoint Scan workflows. **PMC** **Web UI** x Improved user experience of creating new Partner or Customer accounts. x Improved user experience of creating new Printers and Print Queues. - Fixed issue when all advanced OCR features are enabled simultaneously. **PMC Client** x Added auto-configuration for the OIDC authentication provider when installing the PMC Client. - The PMC Client for macOS now includes the user's domain name when using the Store and deliver via gateway option. **Ricoh Cloud Terminal (Gen2)** - Uninstallation of the terminal does not freeze when the admin enters an incorrect device password. - After uninstallation of the terminal, the User Authentication and Administrator Authentication options are set back to "Off" on the MFD. **HP Workpath Cloud Terminal (Gen2)** x Improved status messages when releasing print jobs at the MFD. **Konica Minolta Embedded terminal** - Fixed deployment of KM Open API for devices located in the US region. - Fixed KM IWS card login issue when Enforce API Token access is enabled. **Sharp Embedded terminal** - Scrolling through the print job list is no longer slow. ## Build 3.34 \[2023-06-26\] **Ricoh Cloud Terminal** + New Ricoh Cloud Terminal for Ricoh SOP devices + Cloud printing with no requirement for Secondary Gateway + Users can select one or multiple jobs for printing + Users get feedback on print job status (e.g., Waiting, Printing, Downloading, Downloaded and Printing) + Print jobs can be released from any configured storage location (PMC Client, Cloud, or Secondary Gateway storage) and will be routed to the MFD in the most efficient way + Users can view recently printed jobs in the Cloud Terminal user interface + New scan workflows available in the Cloud Terminal user interface + User can scan to email, Microsoft OneDrive, and Microsoft Sharepoint + Users can merge multiple documents into a single scan job + Users can log in to the device using username and password (or OTP), PIN, or card + Users can access scan and print workflows from a single interface + Users can register their card at the Cloud Terminal terminal **HP Workpath Cloud Terminal** + New HP Workpath Cloud Terminal for HP Workpath devices + Cloud printing with no requirement for Secondary Gateway + Users can select one or multiple jobs for printing + Users get feedback on print job status (e.g., Printing, Downloading and Printing) + Print jobs can be released from any configured storage location (PMC Client, Cloud, or Secondary Gateway storage) and will be routed to the MFD in the most efficient way + Users can view recently printed jobs in the Cloud Terminal user interface + Users can delete print jobs from the Cloud Terminal user interface + New scan workflows available in the Cloud Terminal user interface + User can scan to email, Microsoft OneDrive, and Microsoft Sharepoint + Users can merge multiple documents into a single scan job + Users can log in to the device using username and password (or OTP), PIN, or card + Users can access scan and print workflows from a single interface + Users can register their card at the Cloud Terminal terminal **Fujifilm BI Cloud Terminal** x Updated Fujifilm BI Cloud terminal + Cloud printing with no requirement for Secondary Gateway + Users can select one or multiple jobs for printing + Users get feedback on print job status (e.g., Waiting, Printing, Downloading) + Print jobs can be released from any configured storage location (PMC Client, Cloud or Secondary Gateway storage) and will be routed to the device in the most efficient way + Users can view recently printed jobs in the Cloud Terminal user interface + Users can delete print jobs from the Cloud Terminal user interface + New scan workflows available in the Cloud Terminal user interface + User can scan to email, Microsoft OneDrive, and Microsoft SharePoint + Users can merge multiple documents into a single scan job + Users can log in to the device using username and password (or OTP), PIN, or card + Users can access scan and print workflows from a single interface + Users can register their card at the Cloud Terminal x Support added for additional devices (ApeosPort VII gen2 devices) -- see the Compatibility List for full details **HP OXPd Embedded terminal** x Improved user interface for HP OXPd embedded terminal x Streamlined card enrolment workflow by removing pop-up after card swipe x User login screen reconfigured for ease of use x Text formatting updated for improved readability - Fixed login/card enrolment UI for better usability on devices with small screens + Baltech card readers can be used with HP devices **Sharp Embedded terminal** - Users can now authenticate after Secondary Gateway was restarted. The MFD must be rebooted after the server update for the fix to be applied. - Fixed potential vulnerability **Scan Workflows** **NOTE:** The Scan workflows feature (scan to email, SharePoint, and OneDrive) is available only in the Y Soft-hosted cloud environment and only with pure cloud terminals (FUJIFILM BI, Ricoh, HP Workpath). + New scan workflows can be configured for Scan to Email + New scan workflows can be configured for Scan to OneDrive + New scan workflows can be configured for SharePoint + Users can authorize access to their Microsoft 365 storage services (OneDrive \& Sharepoint) + OCR can be configured for scan workflows + The available output formats for scan jobs are: PDF, JPEG, TIFF, Multipage TIFF, Compact PDF, Searchable PDF, docx, xlsx, xls, pptx, txt, rtf, PDF/a-1a, PDF/a-1b, PDF/a-2a, PDF/a-2u, PDF/a-3a, PDF/a-3u + PDF MRC Compression can be set for scanned files + PDF encryption can be set (automatic or manual password generation) + Image optimization can be applied (Dual page splitting, Blank page removal, Detect page orientation, Despeckle pages) + Merging originals can be enabled/disabled + Document preferences can be applied by workflow (Resolution, simplex/duplex, colour/B\&W) + Static or variable metadata can be set by workflow for subject, body, and filename **Authentication Providers** + Auth0 added as a new authentication provider + Users can authenticate at PMC Client with Auth0 credentials using OIDC + Auth0 groups can be synchronized and used for Access Control **External Card Repository** + External card repository option is available in Authentication providers so that customers can use the custom external card repositories integration with PMC **Secondary Gateway** + PMC Gateway can be deployed to YSoft OMNI Bridge (an edge device) from Endpoints in PMC Web UI + Admin Authorisation workflow and automated download and installation of Secondary Gateway can be initiated from Endpoints **PMC Client** x A5 page size can be set as the default paper size in unattended installations of the PMC Client in addition to A4 and US Letter **Print Driver** x PMC job renderer updated to include support for Epson PCL6 and PS devices correctly applying finishing options **User Interface** - Feedback and error handling improved when the admin does not fill out all required fields in PMC Web UI configuration screens ## Build 3.33 \[2023-05-18\] **FujiFilm BI Embedded** + Updated UI with simplified installation steps for deploying embedded terminal. x Added ability to set up FujiFilm BI terminal for push print with Output Type "PDF" (no requirement for Postscript to be installed on MFD). x Added ability to deliver print jobs in the most efficient way from any configured storage (e.g. jobs will be routed directly from PC Client to the MFD if available, otherwise they will be routed via the cloud). x Card plugin and card service will always be installed. - Job list order fixed in the terminal UI so that the most recent jobs are at the top of the list. - Finishing options (Punch \& Staple) are now working when using push print with FujiFilm BI devices. **Mobile Apps** + Enhanced iOS and Android apps and HP Workpath terminal with user_token security. **API** x Added printer information to Documents History API. - Fixed issue with Access Control List (ACL) inheritance properties when updating ACL via API. **PC Client** - Fixed issue with user being logged out from PC Client for Mac when the client is offline when refreshing OIDC token. **Single Driver** - Fixed issue with landscape documents in non-standard formats (e.g. envelope, ledger, check, etc.) being incorrectly rotated when staple or punch is applied. **Authentication** - Fixed issue with users being unable to authenticate when duplicate group names exist in Google Workspace authentication providers. **Web UI** - Fixed issue with Date/Time picker text being obscured by the cursor when hovering in Reports UI. ## Build 3.32 \[2023-04-25\] **PMC Advanced Embedded** + User can log into PC Client with his 4NEO identity using OIDC. **Ricoh SDK/J Legacy Embedded** - Ricoh legacy embedded terminal works again after removal of an expired Ubiquitech certificate from the truststore. **FujiFilm BI Cloud Embedded** + Advanced finishing options defined by user when submitting the print job via {ShortProductName} PC client are respected when the user releases the job at the FUJIFILM BI Cloud terminal. + Added Quick scan workflows. + Scanning added to Quick action screen. + Unified Embedded UI. + FujiFilm BI Cloud Terminal UI is unified with other Cloud Terminals. + Added card activation at Cloud Terminal. - Card activation at the Cloud Terminal is now possible. - Simplex push print is now working. - Visual bug removed from the UI. - With a long Fullname, the Logout button is displayed correctly. **Lexmark Embedded** - Card self-registration is now possible for Local users at Lexmark MFDs with YSoft card reader. **Public API** + {ShortProductName} API endpoint date/time matches the actual job release date/time. - Documents/history API endpoint is filtering for the "PRINTED" status. **Authentication** - Authenticated users are now prevented from printing jobs of other users via job ID tampering. **Web Client** - The text in the middle panel retains a proper color. **Chromebook extension** - Removed fallback to email authentication when "disableAuthentication" is enabled. Users can only authenticate via token ID. **FMV-Specific Development** - Canceling pending documents is working as expected. ## Build 3.31 \[2023-03-25\] **PMC Advanced Embedded** + 4NEO gets notifications when users perform print/scan/copy. + Public API incorporates tokens from external IDP during card registration. + The type of *Device.deviceCreated* is set to *RicohDateTime* . + Ricoh CloudStream service status is displayed in service details. + Devices are synchronized from a real ClouStream service. **FujiFilm BI Embedded** + Added the possibility to refresh pending jobs. + Added ability to receive simple scan jobs via SwA in PMC. + Fujifilm BI terminal can now release print jobs directly from the cloud. + Streamlined installation of the embedded terminal. **Xerox Embedded** - After registering a card with OTP, an "Authentication failed" message is displayed, and users must log in again. **HP OXPD Embedded** + Enhanced UI **Public API** + Customer can get information on users' group membership via Public API. **Card Registration** + Enhanced Refo script allows inactive user cards to be used again. **Admin** + Improved UX for a better admin experience. + Improved Dashboard in web UI. - In PMC web UI, the colors in the middle of the panel are not turning gray. **PMC** **Android App** - Ricoh App does not overwrite the setting from duplex to simplex. **Web Client** - KM Web Client session at MFD can not be hijacked by other users from a web browser. - Sharp Web Client session at MFD can not be hijacked by other users from a web browser. **PC Client** - PC Client 3.27 is not randomly logging users out. - Chrome extension does now sync with Email auth and GSuite. **Message service** - The number of characters in messaging template was increased. ## Build 3.30 \[2023-03-01\] **PMC Advance Embedded** + Updated Ricoh PMC Advanced Embedded (3.0.11) and Scan to O365 (1.5.0.19) apps . + CloudStream gets notified about handled notifications and the requests are tenant-specific. **Fujifilm BI Embedded** x Added support for Fujifilm BI embedded terminal. **HP WorkPath Embedded** + Updated HP Workpath Embedded to version 3.29 (check the documentation for update requirements). - Enhanced HP WorkPath with user_token security (check the documentation for update requirements). - Added print options button. - Fixed changing subject and filename when scanning to show updates while typing. - French UI update. - Correction in French localization. **KM IWS Embedded** + Updated KM IWS terminal to version 3.30. - Fixed Card swipe becomes irresponsive after the "Back" button is pressed during card registration. **KM OpenAPI Embedded** - Added Security enhancement against XSS attack. **Xerox Embedded** - Fixed error during login for Xerox Altalink devices. - Jobs are correctly displayed in print queue. **Authentication** - Fixed error message when logging in at printer with card ID imported from common Azure AD attribute. - Fixed "400 Bad Request" Azure Graph API call error when utilizing custom fields for card ID mapping. **Public API** - In document history, documents are recorded under correct device when the jobs are sent with the "serialnumber" parameter. **PC Client** + Added option for PC Client to enable custom port monitor instead of IPP. - Wrong copyright year display in windows client. **PMC** **Server** - Fixed correct sorting of job list if requested through "jobs" endpoint. + Updated logic so that administrators can't enable WPS on Secondary Server. ## Build 3.29 \[2023-02-03\] **PC Client** x Added Czech, Slovak, and Polish language support. - PC Client 3.27 no longer logs the user out when switching to offline mode during token refresh. - Fixed the certificate-related connectivity issues when upgrading from versions older than 3.15. - Fixed memory error on shutdown related to Windows network events handler incorrectly deregistered upon application termination. **Server** x Added Czech, Slovak, and Polish language support. - Workflow Processing system (WPS) service is now hidden behind a feature flag. **Driver** x Added Czech, Slovak, Portuguese, Polish, and Swedish language support. **KM Open API** x Added Czech, Slovak, Portuguese, Polish, and Swedish language support. - Fixed the issue with "Internal server error" displayed when the device can't print. **KM IWS** - Card swipe now stays responsive after the "Back" button is pressed during card registration. - Password containing the "\&" character no longer causes failure during card registration. - Jobs with empty names no longer trigger error messages. **Sharp OSA** x Added Czech, Slovak, Portuguese, Polish, and Swedish language support. - The users are no longer redirected back to the login screen after logging in. - Punch function is now working for 4 holes on Sharp. **Ricoh SOP** - Print jobs containing both A4 and A3 pages are printed correctly using their respective formats. **HP OXPd** x Added Czech, Slovak, Portuguese, Polish, and Swedish language support. ## Build 3.28.2 \[2023-01-16\] **API** x Enhanced internal API token access control security. **HP OXPd Embedded** - Enhance escaping of invalid characters from document titles. - Fixed issue with installation failing in specific model configurations with a non-derived FaultException. - Fixed issue where in some configurations card reader PID/VID issue would occur after sending configuration to device. --- version: "2026.08.20" variant: "PMC" language: "en" --- # 2024 ## Build 2024.11.28 **Legend:** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Added feature** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Improved/changed feature** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Bug fixed** **PC Client** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) An administrator can centrally manage PC Client options: (HCP-7738) * Allow local configuration * Log level * Paper Size * Duplex/simplex * Color/grayscale ![image-2024-11-29_12-3-34.png](https://docs.ricoh-pmc.com/__attachments/a_ba123903404d2f2a8d313080b2e861b47d843749933978c7ab74a4f8d8c38afe/image-2024-11-29_12-3-34.png?cb=9b2d7a0aa07b3f44438566381a430c59) ![image-2024-11-29_12-3-49.png](https://docs.ricoh-pmc.com/__attachments/a_578255635e99147f7b07d719e5c49d4b886013ff21663b1516d818e52f1d7760/image-2024-11-29_12-3-49.png?cb=45ec0fbb2616369faf5e1c7dfb79fc3a) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) PC client in hybrid mode is correctly registered when the "Automatically trust new clients/servers" is enabled. (HBT-4910) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) PC client contains correct Ghostscript binaries. (HBT-5016) **Sharp Gen 2 Cloud Terminal (Public BETA 4)** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) An administrator can set the custom logo on the terminal (HCP-13845) ![image-2024-11-29_12-12-9.png](https://docs.ricoh-pmc.com/__attachments/a_2a87986ec8e8d6709d8f4f63c09850e5ef57cdda7a840c3db4db5a07db66c603/image-2024-11-29_12-12-9.png?cb=a74c886a709c5e081a7c00d9239d1e6f) **UI improvements** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Admin Web UI menu has a new structure to simplify the navigation (HCP-13722) ![Screenshot 2024-11-29 at 12.12.58.png](https://docs.ricoh-pmc.com/__attachments/a_86347443fdd980412ae4a8dc8d48f12e08c08ac41186c55e5d269af31ab5aaf7/Screenshot%202024-11-29%20at%2012.12.58.png?cb=cea0f5ebdb3bd4bac7635e05bbf6d06d) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) More printers with the same IP address (e.g. in different subnets) now work correctly with embedded configuration. (HBT-4920) **KM IWS Gen2 Cloud Terminal** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Deployment documentation improvements (HBT-4994) **Various performance and security enhancements** (HBT-4835, HBT-4938) ## Build 2024.11.14 **Legend:** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Added feature** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Improved/changed feature** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Bug fixed** **PC Client** * ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) PC Client security is improved by using an intermediate, customer-specific Certificate Authority for self-signed certificates. PC Client security is improved by using an intermediate, customer-specific Certificate Authority for self-signed certificates, with no impact on currently deployed clients. For new installations or reconfigurations, the specified account domain must be resolvable and signed by a globally trusted CA root (visibility to the cloud server is required). If no self-signed certificates are configured, the PC Client will only trust global CA roots. These changes only affect PC Clients where the server address differs from the account domain **Sharp Gen 2 Cloud Terminal (v2024.11.01 Public BETA 3)** * ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) User is able to enter metadata during scanning. * ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) User can change the terminal language. * ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Push print jobs are tracked on the terminal and account printed page counts **KM IWS Gen2 Cloud Terminal (v2024.11.01)** * ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) User knows that the color job will be printed in B\&W on their monochrome MFD. * ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) The terminal now respects permissions on color print restrictions. **HP Gen 2 Cloud terminal (version?)** * ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) HP now correctly applies finishing options for print jobs produced by native driver. **Xerox Gen 2 Cloud terminal** * ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Improved speed of printing multiple documents on Xerox cloud terminal. **API Changes** * ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) new API available to list of all users (only local and those actually using the solution) /api/v1/users/all **Various performance and security enhancements** * ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Gateway module for Omnibridge is upgraded to the latest OS version. * ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) There is now a warning for administrators on the Web UI when they are attempting to delete a token signing certificate which is in use. ## Build 2024.10.31 **Legend:** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Added feature** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Improved/changed feature** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Bug fixed** **Notifications and scanning** * ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) New customers have email server for notifications and scan workflows configured right out of the box using default email service (HCP-11739) * Default mail server is Amazon SES for all public AWS datacenters and OTC SMTP server for European sovereign datacenter * Vendors and Customers can still use their own/preferred email service * Default email service is also available for existing customers * ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) All existing customers with an invalid email server configuration will be updated to the default service **PMC Client** * ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) [](https://ysoft.atlassian.net/browse/HCP-13689)Users with PC client installed can now see to which gateway is their PC client connected. When connected directly to the cloud, no information is shown. This is available when they right-click the tray icon. (HCP-13689) * ![image-2024-11-1_13-27-12.png](https://docs.ricoh-pmc.com/__attachments/a_9e74410d0281918b0bc9c03463f286b721271b8a24b47d60b2e456b12ad73f01/image-2024-11-1_13-27-12.png?cb=e5b806fb0f5e85f8291a11a69bf02daa) * ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) When the PC Client is manually registered to a service multiple times it no longer returns an error "Client registration failed!". (HBT-4872) **Sharp Gen 2 Cloud Terminal (Public BETA)** (HCP-12826) 1. ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) [Documentation](https://docs.ysoft.cloud/docs/using-sharp-gen-2-cloud-terminal) is available for Sharp Cloud Terminal beta v2 release (HCP-13683) 2. ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Reporting of printed pages on Sharp Cloud terminal now includes actual printed pages (not just pages submitted) (HCP-13705) **SafeQ Mobile app** 1. ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) User can select a print queue before submitting a job (HCP-13451, HCP-13450). The default selection is the "secure" roaming print queue. If there is a direct / push print queue available for the user and properly configured to release the documents (using gateway), the documents will be directly released on that printer. ![image-2024-11-1_13-48-33.png](https://docs.ricoh-pmc.com/__attachments/a_44a9346fcdb6052efb5de26c0894ef109a19e9dc8c5d95f35445fec6201d0cc2/image-2024-11-1_13-48-33.png?cb=74ce91c7601f62208949c5cc8385fcbc) 2. ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Fixed issue with print job list refresh caused by expiring tokens (HBT-4877) **Ricoh Cloud Terminal 3.0.4** 1. ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Application name on the Ricoh MFD is now CloudStream PS (was Ricoh CloudStream PrintScan Embedded) (HCP-13461) 2. ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Ricoh Cloud Terminal now respects all finishing options from the PC client (stapling, punching,...). (HBT-4777) 1. *Note: booklet option is missing and will be added in coming versions.* 3. ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Documents are now released in the order in which they were sent (HBT-4880) 4. ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Reporting of scanned pages now reflects department assignment of a user scanning with Ricoh Cloud Terminal G2.5 and G3 devices (HBT-4547) 5. ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) All MPF settings are now reverted to default after uninstallation of Ricoh Cloud Terminal (HBT-4796) 6. ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Fixed scenario when Ricoh Cloud Terminal Gen 2 fails to connect to the server via installation using Terminal Deployment Tool (HBT-4659) 7. ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Fixed error "Printer with the same endpoint ID already exists on the server" on Ricoh IM350 after authorizing the endpoint (HBT-4524) 8. ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Fixed error when status of the Cloud Terminal is not updated if the previous status is Failed (HBT-4606) 9. ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Various performance and security improvements (HCP-13462, HBT-4451,HBT-4023,HBT-4300) **Various performance and security enhancements** 1. ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) PC Clients now properly work with custom-created API key (HBT-4918,HBT-4754) 2. ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Improved mechanism for handling self signed certificates used for gateways, and clients (HCP-13712) 1. Self-signed certificates are automatically renewed with a new mechanism of intermediate certificate generated for each account. 2. Intermediate cert is valid for 10 years 3. Entity certificate is signed by intermediate 4. Self-signed certificates does not work with primary servers ## Build 2024.10.17 **Web UI** + Self-registered users and guests can now reset a forgotten password via the Forgot password button on the login page. **The Mobile app** + The app now supports communication over the 443 port. **Sharp Gen 2 Cloud Terminal (Beta)** + Users can now cancel scanning via the Cancel scan button. **Various performance and security enhancements** - Updated 3rd party components to mitigate vulnerabilities ## Build 2024.10.03 A note regarding PMC Client for MacOS Sequoia 15: Due to the changed MacOS 15 security model, the PMC Client autoupdate functionality from previous versions doesn't work, and the users must update to version 2024.10.03 manually. After re-installation, the update mechanism will be supported again. The print functionality of the existing version(s) is not impacted **General improvements** + The Messaging service now allows modern authentication with Microsoft (and Google, as soon as verified) allowing email messages and scan workflows to use OAuth2 instead of basic authentication. + Forward proxy support for the PMC Client. **PMC Client** x Improved UI in the auto-update table, notifications, and reporting. - UPN no longer logs out the user and no longer shows a notification after each re-login when the user's PC goes to sleep. - After uninstallation, the HCP Port Monitor is now properly deleted. **Web UI** + The vendor and customer dashboard now shows the Customer Contract ID (MA) and SLA. + You can now delete the logo or background image from customer settings. + Secondary Gateway OVA (Rocky Linux) download links are now available in the Installation files library x Printer configuration form improvements: The new printer form is well structured and leads the admin towards the printer creation in a logical and easy way. x Redesigned UI for the assignment of Access Rights Permissions for user roles and API keys. x When editing the logged-in user in Users, the newly added values are reflected in the current user session and are visible on the My Profile page. x The PMC Client auto-update page now displays correct counts of PMC Clients connected in the last 90 days **The Mobile app** + Admins can now configure the Mobile app via MDM. **Sharp Gen 2 Cloud Terminal (Beta)** + Users can now modify simple workflow settings on the terminal. + Users can now modify scan settings on the terminal. + Admins can now set the complexity of logging on the terminal. **Various performance and security enhancements** x Updated 3rd party components to mitigate vulnerabilities ## Build 3.49 \[2024-09-19\] **PMC Client** x PMC Client auto-update improvements - newly created customers can also use the rollback option. x You can now connect the PMC Client in cloud storage mode to the secondary gateway with the "Enable secure login for session authentication types" option. - PMC Client no longer reports auto-update as failed in the configured "delay" update window. * Severity: C (no user impact) * Root cause: Unforeseen impact of the change. * Bug recurrence defense: n/a - PMC Client can now be reinstalled in unattended mode. The "/S /UPGRADE=false" option no longer keeps the existing configuration file and correctly creates a new one. * Severity: C (no user impact, viable workaround) * Root cause: A different change caused this. * Bug recurrence defense: Added to standard test scenarios. **Web UI** + A new trigger is now available which forces all print to black \& white. This trigger is disabled by default and ready for customers to simply enable or modify. This is available for all new customer accounts. + Improved Web UI for vendors * Vendors have a new quick orientation page with direct links to various information sources. * Vendors now see the list of their customers, including license and expiration directly on the main dashboard * Vendors now see new "Installation files" link where they can access the downloadable components (without the need to go to Ricoh PMC Support Site). Note that the files library will grow in upcoming releases. * After creating a new customer tenant, vendors are offered an email template with customer tenant access. + Guest user support * Users can now self-register in the Web UI. * Guests can self-register for a temporary user account in the Web UI. x The page with triggers is now organized for better usability. x The page with Access control is now organized for better usability. x Changing the name of a print queue with pending print jobs in it no longer causes those jobs to disappear. x PMC Client auto-update tab now uses a more readable font. - The account health section now correctly links to the PMC Client section. * Severity: C (administrator impact with a viable workaround) * Root cause: Missing tests when the section was moved. * Bug recurrence defense: Tests were added. - Administrators are now able to authenticate again at a container level when using the container domain. (HBT-4751) * Severity: C (administrator impact with a viable workaround) * Root cause: Database changes in version 3.45 * Bug recurrence defense: Added tests to the standard test suite **The Mobile app** + New mobile app design + User-friendly interface + Easy to set and connect to your PMC account **Sharp Gen 2 Cloud Terminal (Beta)** + The new Sharp terminal is now available for beta testing + Basic print and scan functions **Xerox Gen 2 Cloud Terminal** + Users no longer need to manually deploy card plugin and card service for Versalink devices. This capability was added to the Terminal Deployment Tool. x Stapling, folding, and punching are now supported. **HP Workpath Gen 2 Cloud Terminal** - Print jobs with booklet and center stapling finishing option when using cloud storage can now be released correctly. * Severity: B (medium user impact) * Root cause: Missing vendor-specific requirements * Bug recurrence defense: Deeper external cooperation **Printing** x EveryonePrint HCP Extension is now branded as SAFEQ Cloud Chrome Extension. - PDF documents that were uploaded via API and have an internal /Rotate command are now printed correctly. * Severity: B (medium user impact) * Root cause: Unexpected PDF configuration * Bug recurrence defense: n/a - When scanning multiple pages with the Page separation processing step, the resulting pages now respect the requested resolution and are no longer significantly bigger. * Severity: C (some user impact) * Root cause: There was an unnecessary conversion as a middle step which was removed. * Bug recurrence defense: n/a **Installation** + Rocky Linux 9 Software Appliance is now available on Ricoh PMC Support Site. Note: this will be also available in the Installations Files library in upcoming releases. **API** x Print queues created by API are now enabled by default. + Account API was extended with new fields for page size, language, and color. The update option now contains the name and domain name. API responses were improved. **Various performance and security enhancements** x Updated 3rd party components to mitigate vulnerabilities. x Various performance updates. ## Build 3.48 \[2024-08-22\] **Communication via port 443, no additional Internet ports** This is a staged rollout and we will announce the availability per data center via our status page. + All PMC components (all cloud terminals, PMC Client, and gateways) now support communication via port 443 (HTTPS). Therefore, you don't need to open any additional ports to the Internet. The only exception is the FUJIFILM BI Cloud Terminal, which will be supported later. (blue-star) Customers with EntraID OAuth or SAML SSO configured should review this [KB article](https://www.ysoft.com/knowledge/potential-entraid-authentication-failure-with-the-v3.48-port-443-introduction) to ensure uninterrupted service. + PMC Web UI is available without the additional 8443 port number in the URL. + All cloud terminals, PMC Client, and gateways on the latest version support communication via proxy servers. **PMC Client** + PMC Client will automatically update to the latest version. This is enabled for new customers. The existing ones can set it up in the PMC Web UI in Configuration \> PC Client. **Xerox Gen 2 Cloud Terminal** + Xerox Gen 2 Cloud Terminal is now available to all customers. (blue-star) There are two known limitations, that will be resolved soon: * The card reader is not recognized frequently after the device is waken up, and the auth screen falls to the default auth method (PIN, username/password). * Pull print basic finishing options, simplex short edge print changed to long edge print is printed as simplex. **Web UI** + For all new customers, a default pull queue is created during the deployment to speed up the initial setup. The queue name is localized. x Entra ID OIDC authentication now works with single-tenant configuration and no longer requires multi-tenant configuration. x The Web UI favicon was improved. x If no signing certificate in PKI and Encryption settings is selected, the users cannot log in to PMC Client via the manual login method. You are now alerted to such situation in the Account health section. x You can now hide download links and the news banner. There are two new permissions to allow this: ViewNewReleaseNotification and ViewClientAndMobileDownload. x The texts and the layout of the document upload section in My documents have been improved. - The cloud terminal deployment documentation link on the Web UI now correctly opens a page with instructions. * Severity: C (intuitive workaround) * Root cause: the documentation page was split per vendor in the documentation which was not reflected in the links on Web UI. * Bug recurrence defense: adopt a new documentation tool and process. - Accented letters (ěščřžýáíéů) are now shown in consistent font with the rest of the letters. * Severity: C (no user impact) * Root cause: automated tests did not catch the visual difference. * Bug recurrence defense: no action taken. **Printing** x A3 paper size can be now fetched in job detail from the API reporting endpoint. **Konica Minolta OpenAPI Terminal** x Konica Minolta OpenAPI Terminal can now be used in environments with a load balancer as long as there is X-Forwarded-For header where the origin IP address of the client is stored. **Installation** x Rocky Linux 9.4 is used with image (OVA) for the NUC HW appliance. **Various performance and security enhancements** x Documents sent via API converting to print for over 5 minutes will not be accepted. They are now marked as failed and shown with the respective status in the Web UI. This also applies to MS Office documents over 200MB or Excel files with over 10,000 pages. x The PMC Client was updated to use the latest and most secure version of GhostScript 10.03.1. ## Build 3.47 \[2024-07-25\] **PMC Client** + You can now set PMC Client with local storage to send pull queue print jobs to cloud storage. + The PMC Client now contains a link to My profile in PMC Web UI. - Added info to documentation that if you delete an account of a user who logged in to the PMC Client and didn't log out, the user may still be able to perform user actions, such as print for up to 1 hour, due to caching on servers. - The Client installer now writes JSON-compliant values to the json file, no longer causing parsing issues. **Web UI** + You can now set triggers to rotate a document by 90 degrees clockwise or counterclockwise. + Users can now upload documents to be printed in the Web UI. This feature is no longer in the Early Access Program but available to all customers. x The table with PMC Client versions that facilitates the auto-update process is now improved. x The button colors have been changed across the whole Web UI. x The Authentication provider name has been added to the Access tab in Scan Workflows. x OIDC-only authentication is not supported with SAML without Service account authentication. - Fixed an issue that prevented creation of customer account with custom logo, resulting in an error and missing license. - Localization to German has been improved. - In Security \> Certificates, the action icons stay grouped together even if you zoom the page. - Fixed the slow loading and internal error on 'My Documents' and 'Reports' pages. - Fixed the issue with missing permissions for default roles that occurred when migrating database from version 3.35 - Fixed incorrect product name of PMC in Lexmark Printer administration. **API** - Uploading print job to a non-existing input port via API no longer returns 200 instead of an error. **Printing** - In the Universal Print Driver settings dialogue window, the arrow button to increase the size of the watermark is now above the arrow button to decrease the size. **Konica Minolta IWS Gen 2 Cloud Terminal** - The terminal now supports Norwegian language. - Registration expiration no longer blocks the whole terminal. - IWS Marketplace versions can access settings via the header icon. **Scanning** - New error codes have been added to help admins with troubleshooting. - A scanned PDF/A document can now be opened in Adobe Acrobat without displaying the "Some characters may not display or print correctly" error. **HP Workpath Gen 2 Cloud Terminal** - Fixed the problem when multi-copy was not working on some HP printers. - Booklet printing now works in the Download\&Print scenario. **The Mobile app** x The Enforce tokens setting has been enabled for existing customers. - BW print jobs are no longer accounted as color print jobs when submitted from the Mobile app. **Performance and security enhancements** - Security has been improved for session user login. ## Build 3.46 \[2024-06-27\] **Scanning** + Users can now scan to Google Drive. **PMC Client** + The PMC Client now has the auto-update functionality. This feature is currently available upon request in the Early Access Program. - PMC Client defaults to the default API key if the API key field is left blank after deleting the optional API key. - When the PMC Client is installed with authentication type = 5 (legacy openid), the type no longer changes after rebooting the workstation, and the user stays logged in. **Web UI** + Users can now upload documents to be printed in the Web UI. This feature is currently available upon request in the Early Access Program. - When creating an Access control record, the authentication providers dropdown list is now correctly sorted from highest to lowest priority. - Fixed a problem when the first search after logging in to the Web UI in Mozilla Firefox wasn't working. - All successfully printed jobs are reported as 'success' in metrics. **Printing** - Direct print jobs are now printed even if they exceed the threshold of 2 minutes. **Konica Minolta IWS Gen 2 Cloud Terminal** - The user experience with scanning has been improved. - For a booklet with top binding, the orientation is now set to landscape so that the document can be printed correctly. **Ricoh Standard Gen 2 Cloud Terminal** + You can now configure the card reader PID/VID via the Terminal Deployment Tool. + The users now see their full names on the terminal. If the full name is not filled in PMC, the users will see their usernames. + Terminal version is reported to server in login report. + The terminal now supports Port 443. + You can now select the input tray (limitation removed). + Added Norwegian language support. x Scan app is no longer displayed on Printer-only devices. - You can now run an instant scan workflow even if its default parameters have invalid values. - The scan and workflow settings are now scrollable. - The order of Home and Up folder buttons on the folder browse parameter screen is now correct. - The terminal uninstallation no longer fails when the terminal was configured to use other authenticaion options than card. - Scan job accounting endpoint no longer fails with error 500 for unknown user. - If a document server application scans and the terminal wants to scan simultaneously, a correct error message is displayed. - Fixed issue where sometimes the "endpoint already exists" screen is misaligned. - The "Device encountered an issue" error message now has correct spacing. - After uninstallation from Web UI, the terminal icon no longer remains on the home screen of the MFD. - When scanning from the glass, the A4 format is now correctly detected; the terminal no longer displays an error message. - The authentication screen no longer freezes while the terminal attempts to fetch the logo. ## Build 3.45 \[2024-06-11\] **Web UI** + The Embedded clients section displays the buttons for each terminal's available terminal installation options correctly, according to what is supported for the given terminal. - When a user tries to filter deleted log files, they get the correct error message explaining why the log file is not displayed. - The keystore loading no longer fails occasionally due to a race condition between the Welcome message and the Reload message. - Fixed a problem where an authentication provider could not be deleted in some cases. - Color print jobs submitted to a monochrome print queue are correctly accounted for as monochrome. - In the Embedded clients section, the Add button is clickable even with a small browser window. **Scanning** - Scan jobs evaluated by OCR as empty documents are now delivered. **Printing** - Universal driver: conversion from XPS to PDF no longer results in a missing font in the document. - SQTS job accounting endpoint no longer fails with error 500 for unknown users. **Konica Minolta IWS Gen 2 Cloud Terminal** x The "service unreachable" screen has been improved. Now, it always displays the time of the error and the terminal version. - The Mediatype option is no longer ignored in the download\&print scenario while using a pull queue. - The terminal now indicates that it failed to load the scan workflows available to the user. **HP Workpath Gen 2 Cloud Terminal** - Fixed the slow authentication via PIN. **Ricoh Standard Gen 2 Cloud Terminal (awaiting certification)** - Users now have more than 60 seconds to fill in their username and password when activating an unknown card. - The terminal no longer breaks the job accounting by trimming usernames. - The terminal no longer attempts to account copy jobs for UNKNOWN_JOB_OWNER users. **PMC Client** + The beta version of PMC Client with auto-update feature is available for early adopters. + The Port Monitor is not reinstalled with every Client update. + The update package is not downloaded again if the Client already has it, for example, in case of rollback. + Information about update progress is logged to windowsEventLogger. - If automatic endpoint trust is enabled, the PMC Client no longer requires manual endpoint authorization. - Direct offline print no longer fails with PMC Client 3.43. - PMC Client authentication type no longer changes after workstation reboot. **The Mobile app** - Compatibility issues do longer appear after the application update on iOS. **API** - If the request does not contain the "Content-Type: form-data" header, the response status is no longer 500. **Performance and security enhancements** - Since version 3.43, PMC no longer runs the vulnerable JRE Version 11.0.20. - The OMNI Bridge no longer goes offline because of OutofMemory error. - The WebClientCanon vulnerability (deserialization of Untrusted Data in com.fasterxml.jackson.core:jackson-databind) is now resolved. ## Build 3.44 \[2024-05-09\] **Web UI** + The administrator can now see the cloud status and scheduled maintenance. + The user's username is pre-filled in the OIDC provider's authentication screen. + The administrator is notified about new PMC version in the Web UI. x My Profile, My Printers, My Documents, and My Authorizations have been consolidated into two sections (My Documents and My Profile) to improve user experience. - Fixed an issue where, in specific cases, emails were displayed incorrectly in the Web UI. - Renamed the "Type of login" to include "Card". - With the CardManagement role, the users can now edit cards. **Scanning** + Customers can now use custom SMTP for scan workflows instead of a default service level configuration (Amazon SES or SendGrid). **Printing** - Documents are no longer printed in color if there is a trigger that sets them to B\&W. - All non-local users are now able to print by default. **Konica Minolta IWS Gen 2 Cloud Terminal** x Auto color copy is now supported. - Fixed the issue when the user could not log in again by card after timeout, not even after waiting for a few minutes. **Ricoh Standard Gen 2 Cloud Terminal** -The installation no longer fails on setting the SP options. **HP Workpath Gen 1 (OXPd) Embedded Terminal** + The administrator can now configure the terminal from a secondary gateway. **Sharp Embedded Terminal** - Four-hole punching is now working on all devices. **PMC Client** - The Client no longer has connectivity issues on Mac after it wakes from sleep. ## Build 3.43 \[2024-04-04\] **API** x Administrators can now create multiple values per API Access Key, thus streamlining the administration. x GetAccount API now includes Account UUID. **Scanning** - Fixed issue with SharePoint Connector when scanning to a localized SharePoint destination where column data is not updated. **Printing** x Increased reliability of printed documents with improved document font handling and failover procedures. **Web UI** + Administrators can now combine the convenience, simplicity, and functions of OIDC and Service Account-based authentication for Microsoft Entra ID and Okta Identity Providers. - After deleting a secondary server, an internal error is no longer displayed. - Fixed user group synchronization with Entra ID Single Sign On Authentication causing failure in permissions being applied.- Fixed error incorrectly being displayed when an admin deletes jobs from a queue HBT-4281 - Fixed LDAP authentication for non-Active Directory customers who wish to use userPrincipalName for authentication. - Fixed Terminal Deployment Tool command generator from creating incorrect commands when a blank password is specified. **Konica Minolta IWS Gen 2 Cloud Terminal** + Added ID Copy Quick Action to the home screen so that users can now copy ID documents with just one tap. x Added Finnish and Ukrainian language support. - Fixed print job synchronization issue causing the terminal to become unresponsive and jobs to be accounted for multiple times. - Swedish language improvements. **Konica Minolta OpenAPI Terminal** - Fixed log retention for webclientKMOpenAPI.log. **Fujifilm BI Cloud Terminal** - Fixed Edge Erase margin causing grey border to appear on scanned images. **HP Workpath Gen 2 Cloud Terminal** - Card numbers are now stored in decimal format. **HP Workpath Gen 1 (OXPd) Embedded Terminal** - After card swipe, the device UI now displays a loading animation so that users have a better feedback on their authentication request. - Updated terminal branding and naming to reflecting PMC brand. - Fixed a rare scenario which could result in a user being authenticated as the previous user who logged in at the MFD. **Kyocera HyPAS Embedded Terminal** - Fixed issue with LDAP authentication where user1 string is appended to the user's display name. ## Build 3.42 \[2024-03-07\] **Scanning** x Users can see the expiration for each failed scan job on the My Documents page, so they know when the document will be deleted. + Significant additions to scan connectors and workflows for Konica Minolta IWS, Ricoh, HP Workpath, and FujiFilm BI pure cloud terminals. + Users may now search for an email when using scan to email + Added Scan to HTTPS scan connector, allowing scanned images and associated metadata to be securely transferred to web services for further processing. + Users can set resolution, sides, color, and merging originals (AKA job build) on the MFD panel. + Users can now navigate a folder structure when saving documents to OneDrive \& SharePoint Online. + Users can now enter metadata on the Cloud Terminal. Data types supported include Text, Number, Date, Email, and Select from a List. These metadata fields may be used to name files and provide variable input to scan workflows. For example, a user could enter the document's name and create a folder in OneDrive using the value of the metadata field. These metadata fields may optionally be required to be entered before scanning may proceed. **Konica Minolta IWS Gen 2 Cloud Terminal (version 2024.02.03)** x Added Dispatcher Stratus Single Sign On support. Please note that the availability of this feature is dependent upon Konica Minolta's release to the Konica Minolta Marketplace. **Ricoh Cloud Terminal** x Added link to Native Copy functionality so that a user may utilize the MFD's copier interface. x Native copy and scan jobs are now accounted allowing more comprehensive reporting. x Tenant logo is now optionally displayed on the terminal rather than the Y soft logo. x Scan updates as described above. **Fujifilm BI Cloud Terminal** x Scan updates as described above. **HP Workpath Embedded Terminal** x Scan updates as described above. This release also contains several performance improvements and bug fixes. ## Build 3.41 \[2024-02-08\] **Scanning** + Added additional Scan Workflow processing steps, including barcode recognition, page separation, and highlighted text extraction and redaction. x Updated OCR engine for improved document recognition performance. **Web UI** x Added target Server Name to Server Information page to improve the administrator's user experience. x Added a "search" filter to the Embedded clients deployment page for ease of administration. x Added Server mode to the Server Information view, allowing admins to differentiate between Primary and Secondary Servers easily. - Improved user data synchronization with Microsoft Entra ID (Azure). **FUJIFILM BI Cloud Terminal** + Before releasing a print job, the user can now define print settings at the MFD. - When printing from the native Fuji driver, print jobs no longer fail because of waiting for the header data. - Improved user feedback with clear error messages when browsing external directories. **Konica Minolta IWS Cloud Terminal** + The users can now change the print job finishing options at the MFD (number of copies, mono/color, duplex/simplex options, etc.). **Konica Minolta OpenAPI Terminal** - Fixed authentication issue occurring during specific installation rollback scenarios, causing incorrect user logins. - Removed sensitive user data from webclientKMOpenAPI.log. **HP Workpath Embedded Terminal** + Administrators can now view a user's Print, Copy, and Scan transaction data. + Users can now delete their waiting print jobs at the MFD. + Added the ability to display the custom tenant logo on the terminal. + A user can refresh the print job list and see print jobs that have been printed since logging in at the MFD. + Users can change the print job finishing options at the MFD, including color/mono, duplex/simplex, number of copies, and tray selection. + Added advanced scanning features such as duplex/simplex, merging originals, color/mono, email selection, and folder browsing. **API Enhancements** + Added a get user by username endpoint. + Page orientation now respects the request specified in the API request. ## Build 3.40 \[2024-01-15\] **Printing** + Added the ability to set a trigger condition based on the number of pages in a document. - Print jobs that are converted from mono to color based on a trigger are now correctly accounted for. - PDFs without a default page size parameter are now printed correctly. - Guest printing from the mobile app now works when 'enable token access' is enabled. **Web UI** +Added a new Quick Start panel menu guiding admins to set up push printing in a fast way. + Admins can now anonymize sensitive end-user personal information in the dashboard, reports, and all related interfaces. + Page separation is now available as a processing step in scan workflows. x Redesigned the Add and Edit Printers menu to simplify configuration tasks. x Added the ability to filter Printers and Embedded Terminals by name, printer address, or serial number. + Added languages: Portuguese, Brazilian Portuguese, Japanese, Simplified Chinese, Danish, Norwegian, Swedish, Thai, Indonesian, Malay, and Korean. - Account names taking up more than one line no longer prevent the admin from scrolling to the bottom of the navigation menu. - Changed the font used for one-time API key display to ensure letters are distinguishable. - Rectified UI language when displaying print job submission times. **Scanning** + Added page separation as a processing step to scan workflows. **Partner Hosted and On-Premises installations** x Upgraded PostgreSQL version. Due to the nature of the improvement, we removed the auto-updating function of existing PostgreSQL versions for Partner Hosted and On-Premises installations. **Secondary Gateway** x Upgraded PostgreSQL version and removed auto-update of existing instances due to upgrade reliability concerns. **PMC Client** x Removed the need to authorize PMC Clients installed using the preconfigured installer. - On macOS, users don't need to enter their credentials after a reboot anymore. - Printer synchronization no longer fails when using authentication types with the domain suffix appended. **API** - The Document history endpoint now returns the jobtype property. - The use of full API access keys is now discouraged to enhance security. - Whenever the API returns a 403 error due to missing permissions, it also returns the list of the missing permissions. **Fujifilm BI Cloud Terminal (terminal version 1.9.0)** + The terminal can now display the tenant logo. + Added Quick Action scan workflows for end-user efficiency. + Added languages: Norwegian, Swedish, Thai, Indonesian, Malay, and Korean. Note that this requires validation by Fujifilm. The estimated completion is mid-January. - When the terminal is loading OneDrive and SharePoint scan destinations, the user is informed about what is happening. **Konica Minolta IWS Cloud Terminal** x The Dispatcher Paragon branded KM IWS terminal is now published under Production Solution Key. - The brand versioning is now unified, and this is reflected in the terminal version to ensure proper discoverability. -Scan and copy jobs are properly accounted for. - Improved efficiency of releasing many print jobs at once. + Added languages: Norwegian, Swedish, Thai, Indonesian, Malay, and Korean. The terminal is released to Konica Minolta. Country-level availability is based on Konica Minolta release processes. **HP Workpath Cloud Terminal (Gen2) (terminal version 3.40.0)** x Added the ability to log, display, and report the installed terminal version. Note that the terminal requires validation by HP. The estimated availability is mid-February. **Sharp Embedded Terminal** - After enrolling their cards, users are no longer stuck on the enrolment page. **Mobile apps** + The iOS and Android mobile apps now support OAuth authentication. --- version: "2026.08.20" variant: "PMC" language: "en" --- # 2025 ## 2025.12.11 **Legend:** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Added feature** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Improved/changed feature** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Bug fixed** **Audit Log** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Administrators can now view detailed audit logs showing **who did what, where, and when** across their environment. Audit logs provide visibility for security, troubleshooting, and compliance, and can be exported for further analysis. This is the first public availability of Audit Logs. See [Audit logs](https://docs.ricoh-pmc.com/docs/latest/pmc/audit-logs.md) for details. (HCP-14039) ![image-20251212-111640.png](https://docs.ricoh-pmc.com/__attachments/a_b82a1c22ab61a0feda5285f4b6fa518926e097d1222131364be33b07ce4e8593/image-20251212-111640.png?cb=a9dde73ce3e1e46365c1a25aaee7a06e) **Reporting** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) ESG Reporting has been improved with clearer date range visibility, updated terminology (including US-specific page size naming), and chronologically sorted exports. (HCP-15439) **Google Workspace** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) User roles can be linked to groups and individual users - to manage access control. (HCP-15367) **Konica Minolta Gen 2 Cloud Terminal** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) The Device Locking feature is now **available to all customers as a BETA** without requiring a feature flag. Availability is limited to regions where the IWS Service Platform is offered via the Konica Minolta Marketplace (HCP-15338). ![image-20251212-103647.png](https://docs.ricoh-pmc.com/__attachments/a_6cfec057c3ada0ff31da2a9eefa280f98de27fa84a927baedef1da3cb504e097/image-20251212-103647.png?cb=d3a90f47b0fadb8d36a08f895e8d2778) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) The card registration flow has been improved to better handle multiple badge swipes during enrollment. This reduces risk of possible user confusion during the unfinished registration process and ensures a clearer, more predictable experience when completing card setup.(HBT-5900) **Ricoh Gen 2 Cloud Terminal** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Copies can be collated and shifted using EOPJOBOFFSET attribute. (HCP-14730) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Improved paper jam message. (HBT-5834) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) When a custom driver is used, the printer display no longer allows changes to finishing options. (HBT-5903) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Application stability improvements. (HBT-5684) **Sharp Gen 2 Cloud Terminal** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Scanning on Sharp devices has been improved by ensuring each scan job uses PagesPerFile=1, option, reducing issues with large scan jobs (the large jobs are send as individual pages and merged at the server processing side). **PMC Client** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Extended Language Support (HBT-5915) * Support has been expanded to include additional languages: Hungarian, Indonesian, Korean, Portuguese, Brazilian Portuguese, Romanian, Swedish, Thai, Turkish, Chinese, and Malay. ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Mac OS print driver is now fully localized. (HBT-5575) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) The PJL header parsing (HCP-15292) setup have been simplified and clarified a bit. (HBT-5891) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) PMC Client now correctly synchronizes even when `ClientSideAcl` is enabled in Citrix environment. (HBT-5911) **Mobile App** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Users can now print via the native print menu also when the app is not running. (HBT-5896) **Other** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Admin Web UI Italian and Portuguese translations were improved based on feedback. (HBT-5872) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Email templates now correctly translate `expiration-time` variable. (HBT-5788) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Scanning stability improvements. (HBT-5837) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Security improvements. (HBT-5716, HBT-5856) ## 2025.11.27 **Legend:** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Added feature** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Improved/changed feature** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Bug fixed** ### Reporting ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Simple Price List for Cost Reporting** (HCP-15323) Customers can now configure a simple price list to assign per-page costs, enabling clearer cost visibility and more accurate reporting across various usage reports. ![image-20251128-075108.png](https://docs.ricoh-pmc.com/__attachments/a_e7463e5c6de99ea207e4b30c225278fba6855ede350155783b49f4d9bd58b46d/image-20251128-075108.png?cb=a27523d21f908eecb22455335bb7bf58) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Reports Now Support Both Page Counts and Cost Views** All reports can now be viewed using either page counts or cost-based metrics, giving customers greater flexibility and insight into their print and scan activity. (HCP-15323) ![image-20251128-074919.png](https://docs.ricoh-pmc.com/__attachments/a_378be09d370d46b49c5e93df5e810199015c86bba374650c978dfcb077c97ac9/image-20251128-074919.png?cb=99e4da50110a298f3561f2d087279c80) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **ESG Impact Reporting Added** Customers can now access basic ESG reports that show the environmental impact of their printing, including estimated CO₂ emissions, electricity consumption, and the equivalent tree usage associated with their print activity. (HCP-15388) ![image-20251128-074936.png](https://docs.ricoh-pmc.com/__attachments/a_823ddc8cad641f2f759cf5e92abf01aa322c60bf0c8e355da109a1cf7d28222b/image-20251128-074936.png?cb=10630ee76a6bc66d18f8243ad02581a1) #### Web Admin UI ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Vendors now receive dedicated email notifications only when one of their tenants has an expired license or is scheduled for deletion. (HCP-15361) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Vendors now see tag "expired" directly in the customer tree menu (HCP-15401). ![image-20251128-072524.png](https://docs.ricoh-pmc.com/__attachments/a_185b64252bbbbffe6fc90545ec28a3b2a1b3c97652cc14876aa0e9d9f64186b5/image-20251128-072524.png?cb=6f2c555526b8f65c55e155acb22fe0c2) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) The printer list now displays the status of the embedded terminal configuration, along with additional details such as device or application version (when available). If an installation or configuration fails, the list also shows clear status or error details to help administrators troubleshoot quickly (HCP-15348). ![image-20251128-082449.png](https://docs.ricoh-pmc.com/__attachments/a_72240a241479faddcb32b0593a381147b43dada1237e47dc74f6394a8ebfd781/image-20251128-082449.png?cb=f49cf703f865dc9d595c74bcc85705fe) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Rules now support a new mechanism for parsing and manipulating PJL header usernames using regular expressions. This allows administrators to match and extract only part of a document attribute---such as the final username segment---rather than requiring an exact full-value match. This enhancement is especially useful when processing documents retrieved via API from large ERP or mainframe systems, where PJL headers often include complex or extended identifiers. (HCP-15292) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) If customers activate or purchase the newly structured license format, they can use different expiration dates for individual printers or device groups. The License tab clearly displays the expiration date of each device group, as well as the final group expiration that determines when the product stops functioning (HCP-15159) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Google Workspace identity provider now supports Google Directory groups and department synchronization (HCP-15352) #### Konica Minolta Gen 2 Cloud Terminal ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Simplified Deployment With IWS Platform** (BETA) Deploying the Gen 2 Cloud Terminal with the device locking on Konica Minolta devices is now significantly easier. To benefit from device function locking, managed access to the device functions and accurate reporting of printed, copied, and scanned pages, Konica Minolta customers still require the secondary IWS application (KM Service Platform PF, available in selected markets via local or regional KM offices). Previously, configuring device locking required two separate, highly technical setups, making deployment cumbersome and error-prone. Now, only the standard Cloud Terminal configuration is needed. Device locking is automatically enabled or disabled based on the **"Lock device"** toggle in the Administrator UI. Embedded terminal templates of "IWS Service Platform" application types have been updated to "IWS Gen2" application types. This change does not impact users; existing functionality continues to work as before. ![image-20251114-104626.png](https://docs.ricoh-pmc.com/__attachments/a_2837f0beaa7c63b1d86f9ea60b5df94e4d5a03c005e9b4b34cd2cf5bfbb76cd8/image-20251114-104626.png%3Fversion=1&modificationDate=1763145192889&cacheVersion=1&api=v2&width=760&height=265?cb=9bfcde77a4f1a08ea9121499ec2256b3) This functionality is still available as a**BETA** and requires the following feature flags: * **KmIwsDeviceLocking** (previous Feature flag **KmIwsServicePlatformEmbedded** have been removed) * Terminal**version 2025.11.01** or newer on the **KM BizHUB** **i-Series** device Contact your support representative to enable these features. (HCP-14946) #### Other Cloud Terminals ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) 'Offset' option in the Universal Print Driver to manage output stack collation now works properly for pull print on Ricoh (HCP-14730, HBT-5851) and Konica Minolta (HCP-14729) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Further improvements done on HP Cloud Terminal to prevent device loosing it's registration (HBT-5825) #### Android Mobile App ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Users can now properly remove added printers through the native print dialog on Android (HCP-15355) #### Scanning ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Scan Workflows now support the %deviceSerialNumber% variable, allowing the printer's serial number to be automatically inserted into output file names and metadata fields (HCP-15341). #### Various Security and Usability Improvements ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) SAFEQ Cloud administrator session token duration had been reduced to 30 minutes (HBT-5784) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) HTTP Response now doesn't contain some unnecessary verbose stacks (HBT-5734) ## 2025.11.13 **Legend:** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Added feature** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Improved/changed feature** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Bug fixed** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Automatic Creation of Scan to Email Workflow**: The Scan to Email workflow/connector is now automatically created when a new customer account is provisioned. The workflow name is fully localized, and access is automatically granted to the Local Users group. (HCP-14871) ### **License Management** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Administrator notifications for license and tenant lifecycle: All customer administrators (users with the *ModifyLicense* permission, e.g. the default Administrators role) are now notified several days before a license expires and again before the **expired tenant is automatically deleted**. Deletion occurs after 30 days for trial tenants and 90 days for tenants with an expired production license. (HCP-15279) Administrators can opt out of these notifications in their profile settings. ![image-20251114-083046.png](https://docs.ricoh-pmc.com/__attachments/a_130b28e4bed2df8fa36a4b538661f527d7bffa83bb68db628bf66faf5164ecb1/image-20251114-083046.png?cb=a4cc7d20f9c1508ee04fe05aad8c3dfb) #### Reporting ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Improved Detail in Reports:** Reports now correctly distinguish between A4/Letter/Small and A3/Ledger/Large page sizes across all views. Total page counts are calculated using normalized pages, where one A3/Large page equals two A4/Letter pages. For historical data where page-size breakdown was unavailable, the respective fields show **N/A**, while total normalized pages remain accurate. (HCP-15193) ![image-20251114-104201.png](https://docs.ricoh-pmc.com/__attachments/a_3996cd33ff37025038921b4003ced60cef5a6e1434a2616db48e0de08b846544/image-20251114-104201.png?cb=8951db82bb7f890d41fbfd932e26a933) #### Other Cloud Terminals ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Xerox Gen 2 Cloud Terminal: Fixed an issue where users could be redirected to Quick Actions even after being logged out (HBT-5836) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) HP Gen 2 Cloud Terminal: Fixed an issue where users could not authenticate with a card on slower devices (HBT-5803) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) HP Gen 2 Cloud Terminal: Direct printing while someone else is logged at the MFD is now accounted correctly. (HBT-5604) #### Mobile Application (iOS) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) The mobile app now includes a built-in tool to gather diagnostic logs and device information, making troubleshooting significantly easier. Users can collect and export logs---including app version, OS version, and device model---directly from the profile page and send them to support via email or any preferred channel. (HBT-5757) #### Other ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) PMC Client now correctly lists hostname when registering an endpoint in local storage mode. (HBT-4979) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Admin Web UI visual improvements (HCP-15330) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Chromebook extension stability improved. (HBT-5776) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Various fixes and security improvements (HBT-5840, HBT-5809, HBT-5830, HBT-5826) ## 2025.10.30 **Legend:** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Added feature** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Improved/changed feature** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Bug fixed** ### Reporting ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Enhanced Reporting is now fully supported and available to all customers (BETA tag removed) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Enhanced Reporting now includes detailed export and aggregation features, improved column management, and a clear distinction between **Summary** and **Detail** views (HCP-15134). * The Summary view aggregates data by **user, department, printer,** and **job type**, with aggregation columns highlighted in grey. Sorting by department, user, printer and job type is supported, where the default sorting highlights sorts by department and highest number of jobs. * Exports always include **all records** , regardless of search queries or column reordering in the UI. The search bar functions as a **full-text search** across all columns, not as a data filter. * The **Summary view** shows aggregated data (excludes dates), while the **Detail view** includes **date, time, document name,** and **UUID** --- ideal for customers looking to analyse the data externally. * When 'Hide sensitive data' is enabled in Security settings, sensitive fields such as usernames and document names are replaced with anonymized strings. Exported data respects the same anonymization rules to ensure privacy in both the UI and downloaded files. ![image-20251031-100301.png](https://docs.ricoh-pmc.com/__attachments/a_3395c4adffe9a4b223258cecb17f79293148c6fc9edb0663cbd319aaf2e2cd0a/image-20251031-100301.png?cb=547ee1a54ec3e1d630ab638861964b78) #### PMC Client Improvements ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) User Principal Names (UPNs) are now supported in the PMC Client for AD-joined macOS devices, improving compatibility with enterprise directory authentication (HCP-15291) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Users in **Citrix and remote desktop** environments now see **only the printers they have access to**, based on access rights or their personal selection. Previously, all configured print queues were visible to all users unless a Windows print server was used. With this update, print servers are no longer required, simplifying deployment and improving security and user experience. Note: to enable this feature (ClientSideAcl), ask your support representative. (HCP-15045) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Added new 'Offset' option in the Universal Print Driver to manage output stack collation for direct (instant push) print on Ricoh, Sharp and Konica Minolta devices with respective finisher (HCP-14727). See known limitations for supported scenarios. ![obrazek-20251030-074133.png](https://docs.ricoh-pmc.com/__attachments/a_40664d1678b09007ec9924975d5635057d07a28e7b7e7acf3b9ed6bcb4585380/576afafc-fac9-4531-bcbb-a7c77567c260%23media-blob-url=true&id=ba7f0567-d628-43e4-9e87-f45affd2eca2&contextId=203858&collection=?cb=e2daca3a8a83568bc1cd3dc2ac3de973) ![image-20251031-101648.png](https://docs.ricoh-pmc.com/__attachments/a_2ca3c0ab5baf7d8ad1258f3986069555052885a6b679df0c82a34b37b1c16cd7/image-20251031-101648.png?cb=713bfbeafe836dfeec820db406a6fd2d) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) PMC Client installer provides option to keep or overwrite configuration if the client was already installed. (HCP-15277) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) The login success screen on the PMC Client now clearly informs users that their job has been sent when authentication is required before printing, removing confusion about whether they need to resend the document. (HCP-15072) ![image-20251031-102402.png](https://docs.ricoh-pmc.com/__attachments/a_1a6ab05a1f8db218464922dc37e3860cebeb45c013c27a1bdfca477cec38ea7f/image-20251031-102402.png?cb=1b613df4738d2c16067515f3aec57a07) **Xerox Gen 2 Cloud Terminal** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Improved behavior with long user sessions. (HBT-5836) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Settings admin menu translations corrected. (HBT-5353) **Ricoh Gen 2 Cloud Terminal (v3.0.7)** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Security advisory:** Customers are strongly advised to update to this version or newer. Resolved a rare issue where a newly logged-in user could see and release print jobs belonging to a previously logged-in user.(HBT-5636) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) See more information in the Ricoh Terminal release notes. #### Cloud Terminals ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Booklet and stapling now works with all Cloud Terminals (HBT-5808) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Having more printers with the same IP address in one environment is no longer causing problems with embedded installation. (HBT-5057) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) HP OXPd: Authenticated users can not access restricted device functions (Settings, Reports) without authenticating with the device administrator credentials (HBT-5742) #### Mobile Print ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) iOS users can now search for a print queue. (HCP-15222) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) 'Page Range' finishing option is not supported with the mobile app, it was removed. (HBT-5726) #### Various fixes ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Web UI has corrected alignment in logs page. (HBT-5794) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Reorganize buttons on Customer account page for consistency. (HBT-5736) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) When deleting a messaging service there is now a validation of its use for password recovery. (HBT-5469) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Other security fixes (HBT-5761, HBT-5782, HBT-5705, HBT-5718) ## 2025.10.16 **Legend:** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Added feature** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Improved/changed feature** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Bug fixed** **Google Workspace integration** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) User groups are now automatically loaded and assigned without the need for a service account, simplifying setup and synchronization. (HCP-15135) **Google Chrome Extension** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) The Chrome Extension now offers seamless integration with all authentication providers, delivering faster, more stable sign-in. Users can log in using any configured method --- from internal application accounts to external Single Sign-On options like Entra ID, Google Workspace, or even legacy systems such as LDAP. (HBT-5576) ![image-20251009-102457.png](https://docs.ricoh-pmc.com/__attachments/a_295cfbd36dfca6349e07668d516eae33fe87f49481b149823d2d94893025701f/image-20251009-102457.png?cb=fe7267eb61752d9be3aff97133e89915) ![image-20251006-124147.png](https://docs.ricoh-pmc.com/__attachments/a_bded109f6b734fcbeb3a51089d1bc18fc887c619c5ab0bd01e03e13580f95708/image-20251006-124147.png?cb=c414efc8eb31bac98a808ecf7c8f4c97) **OMNI Bridge Gateway** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Connecting and onboarding OMNI Bridge as an on-premises gateway is now simpler. Partner Portal credentials are no longer required for authentication --- devices can now be registered directly from the web interface using only the OMNI Bridge serial number and the displayed device code. (HCP-15133) ![image-20251017-064543.png](https://docs.ricoh-pmc.com/__attachments/a_ff3639375a3f291e6b471953d7712ab6e4a5dc3a97c912143af69c50e9ff9a1c/image-20251017-064543.png?cb=05af5f019ca956b00f9f3821bd033970) **New Reporting** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) The Web UI no longer limits reports to 1,000 objects --- larger datasets can now be fully displayed and exported. (HBT-5686) **PMC Client** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Auto-update now works as expected even when the PMC Client is connected to a local gateway. (HBT-5664) **Other** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Security enhancements (HBT-5735, HBT-5732, HBT-5731, HBT-5720, HBT-5773, HBT-5704) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) User attributes (primarily `Department)` are now handled based on the identity provider configuration. If the provider does not supply such claim, the field is treated as local and can be edited via the Web UI and API (HBT-5685) ## 2025.10.02 **Legend:** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Added feature** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Improved/changed feature** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Bug fixed** **Admin Web UI** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) We've extended the ability to use the new raster formats beyond the onboarding wizard. Printers can now be configured in the Printers Advanced Setup UI for all customer tenants. (HCP-15071) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Trial license now allows 200 core and 100 enhanced licenses (100 print and 100 MFD). (HCP-15151) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Guest users can now properly login when OIDC authentication provider is set with asterisk in domain. (HBT-5172) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Search results are now properly anonymized when Hide sensitive data feature is enabled. (HBT-5680) **PMC Client** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) PMC Client now correctly respects changes in proxy settings on the workstation (such as turning on VPN) without the need to restart the client. (HBT-5493) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) PMC Client on MacOS can now be uninstalled using a dedicated uninstaller. (HCP-14932) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) PMC Client now properly shows Windows notifications when installed using offline mode. (HBT-5710) **New Reporting (still in Public Beta)** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Reporting now properly respects "Hide sensitive data" configuration option in Security Settings -\> Privacy part so that user-level reporting is not visible to anyone. (HCP-15156, HBT-5681) ![image-20251007-090317.png](https://docs.ricoh-pmc.com/__attachments/a_9b67f0224d061f4e7ae661aacbd688e1175adfbc28163dcbdbad07b37a222a02/image-20251007-090317.png?cb=943a09de597dc530babefbb6e445ccdb) **Mobile App** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) iOS app has been adapted to iOS 26 look and feel. (HCP-15155) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Fixed an issue on iOS where the plus button was still accessible when an error modal was displayed, allowing unintended actions. (HBT-5687) **Web Upload** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Users now receive a clear message when they try to upload a file type that isn't supported for printing (HBT-5719) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) When users select an output page size during upload, the source document is automatically scaled to fit the chosen format.(HCP-15101) **FUJIFILM BI Cloud Terminal** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) FUJIFILM BI Cloud Terminal now allows users to navigate directly to the native copy application via the quick actions screen. (HCP-15148) ![image-20251003-085933.png](https://docs.ricoh-pmc.com/__attachments/a_328321ca720f2032f31288228077676de0504c95c3025daa83bbac472697f2d8/image-20251003-085933.png?cb=26a18894351cb4386f14a2c9292097c6) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Login times on FUJIFILM BI Cloud Terminal have been improved. From card swipe or PIN entry to the quick menu is now over 50% faster, making access feel almost instant.(HBT-5690, HCP-11629) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Logout button on FUJIFILM BI Cloud Terminal is now aligned with the rest of the user interface. (HBT-5412) **Sharp Gen 2 Cloud Terminal** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Sharp Cloud Terminal can now be successfully installed and configured on the latest firmware. (HBT-5668) **Xerox Gen 2 Cloud Terminal** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Xerox Cloud Terminal now preserves page order for multi-file scanning workflows. When scanning multiple batches from the flatbed within a single workflow, the resulting files keep the exact sequence in which pages were scanned. (HBT-5638) ## 2025.09.18 **Legend:** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Added feature** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Improved/changed feature** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Bug fixed** **Email-to-print** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Attachments from email clients that include them inline are printed successfully. (HCP-14977) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) All new customers have email-to-print available and enabled by default. (HCP-14996) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Default print values are now respected on all terminals. (HBT-5672) **Web Admin UI** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) An administrator can set PIN expiration. (HCP-14508) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Customers with Standard or Premium SLA can now open a detailed SLA report directly from the Overview page. (HCP-15090) ![image-20250919-071126.png](https://docs.ricoh-pmc.com/__attachments/a_efd3545e2360ce22327c2c9cd337b21783993bc98ff3fe66dd78159d78a71843/image-20250919-071126.png?cb=ea9eb8657e6aa978cc4d45dbabba9bc1) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Improved experience when accepting legal documents. (HCP-15085) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Printer location now matches the settings associated print queue. (HCP-15080) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) An administrator can see unknown card login attempts at the web UI (HCP-15097, HCP-14847) ![image-20250919-092445.png](https://docs.ricoh-pmc.com/__attachments/a_cb1daaa109274a00e57361c3acf8456e4a065f69069dbbd03066dd24a825b1ce/image-20250919-092445.png?cb=ef929a2bcf033ec1a9ca309d55f09979) **PMC Client** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) New customers in countries that don't use metric system no longer need to manually change the default paper size from "A4" to "Letter". When creating a new account, the default value for page size is automatically inherited from the parent account. (HBT-5625) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Tray icon is now showing even when using Azure Virtual Desktop. (HBT-5659) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Mac OS logging improvements. (HBT-5631) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Automatic proxy configuration is now working correctly with WPAD. (HBT-5573) **Mobile app** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) iOS users are informed that encrypted office files are not supported. (HCP-15095) **Google Workplace Support** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Service Account Secret file can be directly uploaded. (HCP-14993) **New Reporting (still in Public Beta)** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Reports now allow a custom interval. (HCP-14683) ![image-20250919-070739.png](https://docs.ricoh-pmc.com/__attachments/a_638871f1e47adbbecb7b1f1e4af1bcf4f0dca6429a9373033963919082692f20/image-20250919-070739.png?cb=d6163838ed1f3c3a3f48b244d1d78a05) **HP Gen 2 Cloud Terminal** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) The app now performs as expected even on devices without scanner. (HBT-5662, HBT-5662) **Xerox Gen 2 Cloud Terminal** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Pressing enter in the username field moves the user to password field. (HBT-5382) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Domain validation improvements. (HBT-5234) ## 2025.09.04 **Legend:** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Added feature** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Improved/changed feature** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Bug fixed** ### Authentication ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Administrators can now disable 'Local Users' on the authentication screen --- ideal for customers using only external SSO providers such as Entra ID, Okta, or Google. When enabled, users are automatically redirected to the provider's SSO page, skipping the authentication selection step (HCP-14831) ![image-20251105-221613.png](https://docs.ricoh-pmc.com/__attachments/a_ec42dd45343c16bb532beb9223ef2c605f7dad1be0a0ad043ef8b0bf69b677ed/image-20251105-221613.png?cb=7bab65f0c6a21d57f5740a9402c9f53f) #### **Mobile app** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) iOS users can now submit Office documents for print. See [Using the iOS mobile app](https://docs.ricoh-pmc.com/docs/latest/pmc/using-the-ios-mobile-app.md) (HCP-14428) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Android App stability improvements. (HBT-5607) #### **PMC Client** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Installers are signed with a valid certificate. (HBT-5532) #### **Xerox Gen 2 Cloud Terminal** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Terminal template now has options to specify what copy defaults should be set for users. (HCP-14980) ![image-20250905-055802.png](https://docs.ricoh-pmc.com/__attachments/a_c6403d002a61baa6f00a86d4c9c85a49235366d5033b1e0291513ed27c2b46ed/image-20250905-055802.png?cb=d57f4a490fd50a580b4552c6f2c339f6) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) AltaLink devices now allow scanning uncommon paper sizes. (HCP-14938) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Improved panel responsiveness. (HBT-5563) **Web Admin UI** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Scheduled reports UI visual improvements. (HCP-14876) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Language change no longer requires a page reload. (HBT-5416) **Legacy Terminals** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Konica Monilta OpenAPI terminal now correctly staples documents based on its page orientation. (HBT-5581) ## 2025.08.21 **Legend:** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Added feature** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Improved/changed feature** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Bug fixed** **Google Workplace Support** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Customer can now use the standard OIDC authentication mechanism, including MFA for log in to the cloud. (HCP-14934) ![image-20250818-114658.png](https://docs.ricoh-pmc.com/__attachments/a_f3d00e870c5b713451c071a3b571ab6ab847b15c57c07d9de4c870564a9f2b12/image-20250818-114658.png?cb=7c59091de333b2371e4ffe8017f296a2) **Guest print** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Guest users now have a limit of 10 print jobs. (HCP-14945) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) MIME-Encoded attachments are now parsed and stored correctly. (HBT-5603) **Mobile app** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Android users can now submit Office documents for print. See [Using the Android mobile app](https://docs.ricoh-pmc.com/docs/latest/pmc/using-the-android-mobile-app.md) (HCP-14428) **Web UI** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Trial license now allows 100 core and 100 enhanced licenses. (HCP-15020) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Users can no longer remove documents from job history panel. (HBT-5237) **PMC Client** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Post login screen has been reworked for an improved user experience. ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Print jobs with missing PJL headers are now correctly processes when custom driver is used. (HBT-5545) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Auto-update now works even in rare environment-change cases. (HBT-5399) **New Reporting (still in Public Beta)** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) New Improved Reporting is now available to all customers in all regions (HCP-14969) * Almost real-time, fast and visual volume, usage and trend analysis at hand​ * Overview of weekly/monthly and annual volume of printing, copying and scanning with totals and timeline; duplex and color usage comparisons.​ * Monthly and annual print, copy and scan volume trends​ * Quick glimpse on efficiency of printer use or excessive/underutilized print​ * Overview of most used scan workflows​​ * Top used **printers** by volume, color/monochorme split and top outliers (printers with unusual activity)​ * Accurate drill down of usage per **printer** - Weekly, Monthly and Annual usage per **user /** per **department /** per **group**​ / printer / container * Drill down of **trends** per selected user, selected department or group​ * Print and copy volumes, Scan volume, Duplex and color usage analysis and trends​ * One click export of data to excel * Scheduled export to email **Security Updates** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Legacy and week ciphers `RSA_WITH_AES_128_CBC_SHA` and `RSA_WITH_AES_256_CBC_SHA`had been disabled everywhere (HBT-5587) ​​ ## 2025.08.07 **Legend:** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Added feature** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Improved/changed feature** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Bug fixed** **Print via email** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Users can send an email with documents attached. Those files will be converted and available for print in their secure print queue. See [here](https://docs.ricoh-pmc.com/docs/latest/pmc/email-to-print.md) for more details. (HCP-12336) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) When enabled, guest users can use the service and receive login instruction in an email response. See [here](https://docs.ricoh-pmc.com/docs/latest/pmc/guest-users-guest-printing.md) for more details. (HCP-14771) ![image-20250808-104258.png](https://docs.ricoh-pmc.com/__attachments/a_1acd9548412f5091db9fdad0a250fc86309bbfde1cfb724184d04ff559249b69/image-20250808-104258.png?cb=6214ddf255dbec1ca70ba9546cdef77b) ![image-20250808-104156.png](https://docs.ricoh-pmc.com/__attachments/a_7b4f413594af5511780c5ef21445b156f810d485348209a62e99a2753bba0b32/image-20250808-104156.png?cb=66cb45b64931f1f01841daa4e3e21ab8) **Web Admin UI** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Card conversion now shows what card values are available for each user in their user detail. (HCP-14905) ![image-20250808-083717.png](https://docs.ricoh-pmc.com/__attachments/a_52e1c5bb2467c28add2c8e787bcfe18e29c82353a95d0810b7e91c25a97968b0/image-20250808-083717.png?cb=6f6b5a5b9a424e40dd26a8b1d12369b0) Customers with beta reporting enabled * ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) can now schedule reports to be delivered as dashboard screenshots. (HCP-14875) * ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) can now change language. (HCP-13774) * ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) see improved Spanish translations. (HBT-5594) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Customers in all public AWS clusters will have beta reporting enabled. ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Text is now correctly translated to other languages. (HBT-5583) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Web upload now respects the selected paper size. (HBT-5515) **PMC Client** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) When a PMC Client filename contains a domain, for example: `safeq-cloud-client-2025.08.07.1-setup[customerdomain.com],` then the advanced installation option is not offered. The PMC Client will start the installation right after the End User License Agreement screen. The advanced options screen is available when the domain is not present in the filename. (HCP-14907) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Proxy Auto-Configuration (PAC) file-driven proxy is now correctly detected also when set via Group Policy Object (GPO). (HBT-5597) **HP Gen 2 Cloud Terminal** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) HP Gen 2 Cloud Terminal now accurately accounts for what was printed. For example, when a print job is not completely printed due to running out of paper, the reports reflect that. (HCP-14951) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Rare cases when large print jobs would print two times in certain conditions were mitigated. (HBT-5531) **Konica Minolta IWS Gen 2 Cloud Terminal** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Terminal template now has options to specify what copy defaults should be set for users. (HCP-14562) * Note: requires 2025.08.07 or higher version ![Untitled-20250808-105041.png](https://docs.ricoh-pmc.com/__attachments/a_89c025aabd51c420a504b5e499e20f7e7ed3c24e1e713fa81a4a9e4b052acf52/Untitled-20250808-105041.png?cb=2cc3c3d2f816e2473895bed185d9e143) **FUJIFILM BI Cloud Terminal** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Accounting information is now correctly processed even for users from external sources. (HBT-5470) **Mobile App** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Files with non-ASCII characters are now printed correctly. (HBT-5476) **Security** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Legacy unused port 8421 was removed from secondaries. (HBT-5504) ## 2025.07.24 **Legend:** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Added feature ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Improved/changed feature ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Bug fixed **Admin Web UI** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Administrators can now configure card conversion on each embedded profile. See documentation for more details: [(2026.08.20) Using Card Number Conversion](https://ysoft.atlassian.net/wiki/spaces/sqcd/pages/1691549697/2026.08.20+Using+Card+Number+Conversion). (HCP-14877) ![image-20250725-053438.png](https://docs.ricoh-pmc.com/__attachments/a_d716201a8d1de9c83c3cbe87a94e8b029d40db9398a25a661bd6197fb785db6f/image-20250725-053438.png?cb=62a400d2fc49afab71a16c11babe2525) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Customers in EU cluster will have beta reporting enabled. ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Customers with beta reporting enabled can now schedule reports to be delivered into their email. (HCP-14873, HCP-14803) ![image-20250725-083631.png](https://docs.ricoh-pmc.com/__attachments/a_a6cd933809110e0c24649bed8355a0fc4c55f7d2b03acd0053fd03c4eef43d98/image-20250725-083631.png?cb=81e27fa761736810c6c6275f1ad5db71) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Security enhancements (HBT-4393) **Konica Minolta Gen 2 Cloud Terminal** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) The startup time and terminal responsiveness when used with Service platform has been significantly improved. (HCP-14833) **Scanning** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Scanning with OCR now correctly detects page orientation for Portuguese and Russian documents. (HBT-5579) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Scan separation now works correctly with Ricoh Gen 2 Cloud Terminal. (HBT-5527) **PMC Client** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Default values for `LOGINPOPUPTYPE` parameter are now properly documented in [Installing Cloud Client on Windows](https://docs.ricoh-pmc.com/docs/latest/pmc/installing-cloud-client-on-windows.md). (HBT-5569) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) PMC Client for macOS when using quick install mode no longer opens two browser windows for login. (HBT-5414) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) User now receives a conscious message when their print jobs become unavailable during printing. For example, if their notebook with PMC Client set to local storage mode shuts down in the middle of print job transfer. (HBT-5366) **Authentication** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Documentation was updated explaining system behavior on deactivated/deleted users with external authentication providers: [Authentication providers](https://docs.ricoh-pmc.com/docs/latest/pmc/authentication-providers.md). (HBT-5377) ## 2025.07.10 **Legend:** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Added feature ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Improved/changed feature ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Bug fixed **PMC Client** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) PMC Client now allows to use existing 3rd party print driver via a `/CUSTOMDRIVER` switch. See the documentation for usage and limitations: [Installing Cloud Client on Windows](https://docs.ricoh-pmc.com/docs/latest/pmc/installing-cloud-client-on-windows.md) . ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) PMC Client installer now blocks shutdown, sleep, hibernation, or restart while an update is running, ensuring your installation completes reliably. (HCP-14812) **Web UI** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) New reporting features (Beta) now available for all customers in the Singapore cluster. ![image-20250725-063437.png](https://docs.ricoh-pmc.com/__attachments/a_eb087c2c673e04790272d9401bb4a9e1dfbb1c56852c0761e25f8a732ad91107/image-20250725-063437.png?cb=11abe39980bc5f6018ab465032d83baa) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) %deviceDescription% now returns the actual device description instead of the generic "Printer" value when the variable is used in scan workflows. (HBT-5433) **Xerox Gen 2 Cloud Terminal** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Terminal Deployment Tool uninstall for Xerox now either omits the `-k` flag when it isn't needed or correctly populates it as `-k` restore in kiosk mode. Making sure application access is automatically restored (or no invalid flag is passed) after uninstall. (HBT-5040) **Konica Minolta Gen 2 Cloud Terminal** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Konica Minolta Gen 2 Cloud Terminal now processes very large batches of print jobs in smaller, managed requests, mitigating "Failed to fetch" errors on login or risk of memory issues on the device. (HBT-5392) **HP Gen 2 Cloud Terminal** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Scanning workflows now display the full workflow names instead of truncating them. (HBT-5164) **Ricoh Gen 2 Cloud Terminal** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Terminal now displays a clear "network unavailable" error if network connection is lost during a print job and correctly times the session out. (HBT-4169) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Job timestamps now display correctly on the terminal when the MFD is set to a later time zone (e.g., GMT-5), regardless of the device's locale. (HBT-4998) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Terminal now gracefully handles card swipes on a sleeping MFD. (HBT-5398) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Terminal no longer loses its registration. (HBT-5523) ## 2025.06.26 **Legend:** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Added feature ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Improved/changed feature ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Bug fixed **Sharp Gen 2 Cloud Terminal** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) There is a new option to "Enable numeric keypad for PIN entry" at the terminal template. When enabled, it will show numeric keypad for PIN input field at the terminal, instead of alphabetical one. (HCP-14767) This new option will become effective with new version of Sharp Cloud Terminal 2025.07.01. **Konica Minolta Gen 2 Cloud Terminal** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Added the option to show or hide the Cloud/Native Copy/Scan application quick action. (HCP-14767) These new options will become effective with new version of KM IWS Cloud Terminal 2025.07.01. **Web UI** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Improved localization of PMC Client auto-update page. (HBT-5474) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) The overview page no longer displays an alert about "PMC Clients with storage mode set to 'Cloud Storage' won't be able to print using Instant print and Mobile print". (HBT-5509) (also hotfixed) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) New reporting features (Beta) now available for all customers in the Singapore cluster **PMC Client** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) PMC Client now correctly authenticates using OAuth 2.0 (e.g. with OKTA) also when connected to a gateway. (HBT-4968) ## 2025.06.12 **Legend:** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Added feature ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Improved/changed feature ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Bug fixed **Web UI** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Adding printers was reworked for better experience. (HCP-14572) ![image-20250613-091719.png](https://docs.ricoh-pmc.com/__attachments/a_8f96424c4d91cb21f31344461398e41a4938ae8caaea0094a9de23eb0f0742f8/image-20250613-091719.png?cb=4bf0bd7a7cbdbc98166fb8ef24239cd7) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Minimal PIN length is now respected and can be lower than 6. (HBT-5454) **Xerox Gen 2 Cloud Terminal** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Sending large amount of individual scan jobs no longer causes some to fail to deliver. (HBT-5453) **Konica Minolta Gen 2 Cloud Terminal** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Added the option to show or hide the Cloud/Native Copy/Scan application quick action. (HCP-14724) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Automatic logout timeout now resets with typing or scrolling. (HBT-5441) **Printing** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Direct offline print is no longer changed when user profiles are applied - it keeps its value. (HBT-5424) **Authentication** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Built-in OIDC Web UI authentication is now available also on secondary gateway. (HBT-5039) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Guest users are now able to use the Mobile App also when SAML SSO is enabled. (HBT-5425) **Upgrading of customer-hosted environments** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) When upgrading to version 2025.06.12 from any prior release, manual database-level actions are required. For detailed procedure, please contact Technical Support. ## 2025.05.29 **Legend:** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Added feature ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Improved/changed feature ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Bug fixed **PMC Client** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) A new option for security-conscious environments: PMC Client can now optionally run under a restricted virtual service account instead of the default Local System. This significantly reduces security risk. To enable this requires `USESERVICEACCOUNT` switch to be used during installation. See [Installing Cloud Client on Windows](https://docs.ricoh-pmc.com/docs/latest/pmc/installing-cloud-client-on-windows.md) for more details. (HCP-14631) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) PMC Client login mechanism no longer requires some users to login two times. (HBT-5374) **Web UI** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) The waiting print jobs icon no longer shows a spinner. (HBT-5436) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Automatic endpoint trust was in some cases not applied even when enabled. This is now resolved. (HBT-5246) **Konica Minolta Gen 2 Cloud Terminal** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Performance optimizations were added to limit "Script Busy" error message on older devices. (HBT-5185) **Xerox Gen 2 Cloud Terminal** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Advanced finishing options like booklet printing, punching and stapling are now working as expected. (HBT-5383) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Push print mechanism with PMC Client in local storage mode was improved to mitigate a risk of document being printed two times. (HBT-5346) **HP Gen 2 Cloud Terminal** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Improved support for printing multiple copies via HP Universal Print Driver (UDP) over IPP in Pull Print; jobs now correctly respect requested copy counts where possible (HBT-5368) **IPP printing** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) IPP endpoint is now more robust and has better throughput for accepting print jobs. (HBT-4759) ## 2025.05.15 **Legend:** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Added feature ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Improved/changed feature ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Bug fixed **Web Admin UI** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) PMC Client Auto-updateinterface has been refined with clearer indicators for manual updates, updated visuals, improved sorting, and streamlined feedback submission. (HCP-14577) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Final color adjustments across key Web UI components have been applied to ensure a more consistent and accessible user experience. (HCP-14122, HCP-14279) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) My Profile -\> Sessions no longer fails to load the content. (HBT-5415) **Sharp Cloud Terminal** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Installation and configurationare now possible using the Terminal Deployment Tool, including advanced deployment scenarios across multiple devices. See [Terminal Deployment Tool](https://docs.ricoh-pmc.com/docs/latest/pmc/terminal-deployment-tool.md) for more details. (HCP-14585) **Scanning** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Scan to download scanning workflow now correctly separates pages when using barcodes. (HBT-5330) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Barcode processing is much more reliable now. (HBT-4825) **API** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Creating output port via API now correctly assigns embedded configuration. (HBT-5408) **Gateways** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) The exceptions with gateways unable to reconnect to the primary cloud servers are now correctly handled (TryConnect exception) and gateways operate as expected. (HBT-5342) ## 2025.04.30 **Legend:** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Added feature ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Improved/changed feature ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Bug fixed **Web UI** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Shared Print Queues - Users now can share print files with others by using the new shareable option. (HCP-14381) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) The Installation Files section of the vendor account now provide an up-to-date link to the latest version of the Universal Print Driver. (HCP-14510) **Xerox Gen 2 Cloud Terminal** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Manual configuration is no longer needed---when a Xerox Cloud Terminal is authorized, its printer and embedded configuration is now created automatically using the device's serial number. (HCP-14537) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Xerox Cloud Terminal now supports configurable session timeouts (up to 15 minutes), with smart handling that pauses during active use and logs the users out upon leaving the app. (HCP-14527) **Ricoh Gen 2 Cloud Terminal** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) You can now install the Ricoh Gen 2 Cloud Terminal using the Terminal Deployment Tool on networks where port 80 is blocked, with updated documentation reflecting this change. (HCP-14606) **Canon Embedded Client** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Added support for the Canon Embedded Client specific to the Oceania region. (HCP-14346) **Konica Minolta Gen 2 Cloud Terminal** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Both native and in-app scans are now accounted correctly. (HCP-14473) **Sharp Gen 2 Cloud Terminal** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) We've fixed an authentication issue that prevented jobs sent via IPP using a vendor driver from printing on Sharp Cloud devices---these jobs are now properly handled during pull print sessions (HBT-5338) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **HP Gen 2 Cloud Terminal** Improved performance and reliability of card login to address intermittent black screen issues caused by high printer usage; the terminal now delays initialization until the card is read, reducing SDK load and improving responsiveness (HBT-5308) **Scanning** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Scanned documents with PDF/A compliance other than PDF/A-1a no longer fail to embed fonts correctly. Errors in Adobe Acrobat are no longer happening in such cases. (HBT-5315) **PMC Client** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) PMC Client no longer returns a different set of input ports depending on whether it was using API mode (cloud storage) or websocket-channel mode. Ports are now consistent across both. (HBT-5337) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Default Windows printer set by the client is selected consistently, prioritizing the one with the lowest ID. (HBT-5371) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) When printing A3 documents as booklets, the output is now correctly downscaled to A4 size instead of incorrectly producing A5 on A4 paper. (HBT-5302) ## 2025.04.17 **Legend:** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Added feature ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Improved/changed feature ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Bug fixed **Web Admin UI** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Simplified process to add a Konica Minolta Gen. 2 Cloud terminal into the environment. (HCP-14497) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Print and scan delegation improvements. Users can now share documents with people who do not yet have an account. (HCP-14467) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Renamed Entra ID groups are now correctly displayed. (HBT-4215) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Fixed an issue where guest users were redirected to an incorrect login page after clicking the 'Go to Login Page' button in the invitation email. (HBT-5213) **PMC Client** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Support information package also contains safeqclientcore.conf. (HBT-4966) **Ricoh Gen 2 Embedded Terminal (3.0.5)** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Booklet Printing Support, users have a wider range of finishing options. ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Supported Languages, users can access the embedded terminal in their own language (Finnish, Welsh, New Zealand Maori, Arabic,Hebrew). ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Easier for users to navigate to the Secure Print \& Scan application. ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Provides more accurate usage reporting based on device counters. ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Improved logic for downloading jobs to the MFD to prevent large jobs failing to download properly ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Fixed issue where user was unable to cancel job or logout if network cable is removed during large print job processing. ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Fixed issue in UI with terminal version sometimes being pre-fixed with "null" ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Fixed issue with card login from sleep mode resulting in "You do not have permission to print" error ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Disabled System Auto Reset during print/scan background activity so that the device will no longer switch to home screen during print/scan processing ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Fixed issue where application could stop when restart button is pressed during installation from Ricoh Application site **Terminal Deployment Tool** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Fixed an issue where the Terminal Deployment Tool used unsecured HTTP (port 80) during deployment, configuration, and uninstallation of Xerox terminals, despite documentation stating that only HTTPS (port 443) should be used (HBT-5327) ## 2025.04.03 **Legend:** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Added feature ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Improved/changed feature ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Bug fixed ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Print and scan delegation improvements** (HCP-14351) Users now have an easier way to delegate their printing and scanning (scan to download workflow) to other users. Previously, this was only possible by the administrator, now the functionality is also available to users - a new "Sharing" section in "My Profile". ![image-20250404-094855.png](https://docs.ricoh-pmc.com/__attachments/a_1d7b75191b1d477e11b05ee03513f80e0b42313486684353cbeb4203177e5019/image-20250404-094855.png?cb=e83a63559e4c12d5a9b0e86e75aecdab) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Scan to download (My documents)** (HCP-13992) A new scan connector is now available: scan to download. It's designed for customers who don't use cloud storage and prefer not to send scanned documents via email. This workflow securely stores the documents in the cloud, the users are notified via email with a download link. The scanned documents are also available via 'My Documents' section in "My Profile". ![image-20250406-133718.png](https://docs.ricoh-pmc.com/__attachments/a_f5994abbb96a32f999751ddbc2ff3a7a1552bf3e1f4c73a8d3129e2704d6d71b/image-20250406-133718.png?cb=c897dc7bf90c5a3efa1560d7f0ec0172) ![image-20250404-095253.png](https://docs.ricoh-pmc.com/__attachments/a_1a441d2870c8a8213be7b1e9dd6fd9b9828c4946b8f4950b652947d33c54e928/image-20250404-095253.png?cb=0c2820b3a0d1ec1876f036eb5ff34f84) **Web Admin UI** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) UI improvements in PMC Client auto update section. (HCP-14427) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Cloud option removed from Terminal integrations settings. (HCP-14412) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) The default type of login on default embedded templates changed to "PIN or Card". (HCP-14412) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) The Gateway installer link is available on "Installation files" page. (HCP-14113) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Adjust license validations on add new printer page. (HCP-14411) **HP Gen 2 Cloud terminal** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) New language support added (HCP-14020) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Multiple print jobs are now reliably processed in FIFO (first-in, first-out) order based on submission time (HBT-5258) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Fixed an issue where HP Cloud Terminal Gen 2 incorrectly applied finishing options to print jobs sent via native drivers; such jobs are now passed through unchanged unless they are PDFs (HBT-4789) **Bux fixes:** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Fixed an issue where creating a trigger for OTP and/or Short ID would generate multiple codes and send multiple emails---one for each print job sent by the user. (HBT-5061) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Fixed an issue where not all parts of a split scanned document are delivered. This was sometimes happening during the split processing step combined with OCR when the document was split unevenly. (HBT-5202) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Fixed an issue where card registration triggered two consecutive authentication requests to Entra ID, potentially causing false-positive "bruteforce" alerts. (HBT-5236) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Fixed an issue on macOS where the client did not persist the logged-in user after reboot due to the remember_login setting not being properly saved to client_config. (HBT-5221) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Fixed an issue where case sensitivity in the customer tenant name caused device token validation to fail. (HBT-5313) ## 2025.03.20 **Legend:** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Added feature ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Improved/changed feature ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Bug fixed **Scanning** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) A new scan to download connector is available. (HCP-13992) * See the documentation: [Scan to download (My documents) connector](https://docs.ricoh-pmc.com/docs/latest/pmc/scan-to-download-my-documents-connector.md) **Web Admin UI** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) PMC Client auto-update report now shows more details. (HCP-14336, HBT-5245) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) PMC Client tab was simplified to show a quick overview of client versions. (HCP-14335) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Document encryption is no longer optional, it is now enabled by default and cannot be disabled. (HCP-14192) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Web upload: documented limitation that only standard fonts are supported, see [Web upload](https://docs.ricoh-pmc.com/docs/latest/pmc/web-upload.md) . (HBT-5049) **Chrome Extension** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Chrome Extension informs users when the server connection is unavailable. (HBT-3677) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Chrome Extension version is now visible in the options window. (HBT-3645) **Konica Minolta Gen 2 Cloud Terminal** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Simplified process to add a Konica Minolta Gen 2 Cloud terminal into the environment. It is created automatically now. (HCP-13692) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Clearer information when print job settings can't be changed (HCP-14179) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Multiple jobs sent to print are always printed in first-in, first-out order (HCP-14185) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Fixed inconsistency of displaying the full name in the scan and print menu (HBT-4580) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Added file rotation for the terminal log files. (HBT-5239) ## 2025.03.06 **Legend:** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Added feature ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Improved/changed feature ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Bug fixed **Web Admin UI** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) A new section "Installation files" is now available for customer admins. (HCP-14177) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Further tooltip visual improvements. (HBT-5251) **PMC Client** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) PMC Client with universal print driver is now ARM 64 compatible. (HCP-14183) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Universal print driver now support a new paper size: Arch B 12 X 18in. (HCP-13522) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) PMC Client mechanism to switch to port 443 from legacy 7400 was improved. (HBT-5215) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) With Windows Protected Print (WPP) enabled the print queue no longer fails to create when renamed at the Admin Web UI. (HBT-5156) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) PMC Client auto update report now correctly shows failed instances following the selected time period. (HBT-5193) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Documentation page "Rules - triggers and automation" now lists individual document statuses with description. (HBT-5225) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) The messaging configuration now allows modern authentication with Google allowing its use in email messages and scan workflows. ## 2025.02.20 **Legend:** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Added feature ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Improved/changed feature ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Bug fixed **UI improvements** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Web UI fonts, styles and tooltips updated for improved usability. (HCP-14018, HCP-14019) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) User is informed why print job Web Upload is not available for them. (HCP-13793) ![Screenshot 2025-02-21 at 13.08.02.png](https://docs.ricoh-pmc.com/__attachments/a_6d810ced33be8232fab7be1f44b794f12bbbf3f7051c3b6413b3ccb546e9573c/Screenshot%202025-02-21%20at%2013.08.02.png?cb=439d0abdb9d033c74f9aabe745d481a2) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) A user can go to "My profile" and uncheck a print queue even when it was added with "available by default" checked. (HBT-4803) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Web UI now correctly displays the number of pages for each print job when WPP (Windows Protected Print) is enabled. (HBT-5158) **PMC Client** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) PMC Client auto update now cleans up its folder structure after each version. (HBT-5150) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) PMC Client correctly auto updates to the selected version and automatically restarts. (HBT-5218) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) A user is not allowed to use a blank PIN when logging in(HBT-5107) **Terminals** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) KM OpenAPI terminal connected to OMNI bridge no longer stops responding with multiple logout button clicks. (HBT-5188) ## 2025.02.06 **Legend:** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Added feature ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Improved/changed feature ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Bug fixed **UI improvements** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) PMC Client auto update report now contains more information, can be exported into multiple formats and filtered by time period. (HCP-14108) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Web UI informs administrators about implications of using built-in CA. (HCP-14104) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Locations can now be reordered. (HBT-5058) **Sharp Gen 2 Cloud Terminal (v2025.02.01)** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Sharp Gen 2 Cloud Terminal requires admin password to access application settings. (HCP-13789) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Sharp Gen 2 Cloud Terminal requires admin password to access application logs. (HCP-13931) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Sharp Gen 2 Cloud Terminal UI improvements when folder-browsing. (HCP-13945) **API** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) The system can now process print job types even if they are not recognized as Postscript, PDF or PCL6 jobs. They are no longer rejected. (HBT-5078) **Various performance and security enhancements** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Virtual appliance OVA (Build 20240821_0932) now longer fails on vSphere with: An invalid argument "configSpec.guestId" error. (HBT-5071) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) HTTP Options methods are only used when needed. (HBT-5077) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Improved security of HTTP headers. (HBT-5076) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Weak cipher suites were disabled. (HBT-5075) ## 2025.01.23 **Legend:** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Added feature ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Improved/changed feature ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Bug fixed **PMC Client** * ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) When WPP mode is turned on, these Finishing Options are received via IPP and converted into the PJL headers stored in the document. * Page range * Stapling * Punching * Input tray * Output tray * More paper sizes **UI improvements** * ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Every new customer has a list of default, preconfigured embedded terminals created. ![Screenshot 2025-01-24 at 13.55.15.png](https://docs.ricoh-pmc.com/__attachments/a_7098da327f7d5fed0bb420fdf5d405ce99d488f2bdd8037e06b3d19002df222b/Screenshot%202025-01-24%20at%2013.55.15.png?cb=1bd16d350fc702bcf785fcff9a7615a2) * ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Admin now has the link to embedded configuration deployment from the printer list ![Screenshot 2025-01-24 at 14.42.06.png](https://docs.ricoh-pmc.com/__attachments/a_0da84c39018630063791540aca235aa1d23e0ba977addb6a765c889b888afefd/Screenshot%202025-01-24%20at%2014.42.06.png?cb=9ffdef01497c1d1d1e38f48ffff9cc2a) **Scanning** * ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Scan to email now support OAuth2 ![Screenshot 2025-01-24 at 15.13.02.png](https://docs.ricoh-pmc.com/__attachments/a_e753d39436036243c66324a35383d53a56f647e7c624b224dadc5a98f4dd04ab/Screenshot%202025-01-24%20at%2015.13.02.png?cb=ba33149043661fabc531615d438aab4b) **SafeQ Mobile application** * ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) The SafeQ Mobile app now supports releasing documents via a QR code scanned on the printer. This feature is available only in environments with a gateway or when local storage is enabled on the client. ![IMG_2C6605E0267E-1.jpeg](https://docs.ricoh-pmc.com/__attachments/a_099382cd00c1ce659145c81223feba2506bf180b25468ead59cc1a7a8029943e/IMG_2C6605E0267E-1.jpeg?cb=f63f18d15ef8499a845599c0c16e5308) **Konica Minolta Gen 2 Cloud Terminal (v2025.01.01)** * ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Copy accounting is done via Service platform authentication app. Native copy accounting is also supported. * ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) IWS Cloud terminal terminal gets the information about ISPF integration (Service platform authentication application is installed) from server and avoid asking for ISPF token when not integrated. * ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Logout button is hidden when integrated with Service platform. Hardware button must be used to log out. This avoids login user back right after pressing logout, which is a limitation of the integration. * ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Quick copy action on IT6 machines no longer triggers the "separate scans" native dialog. * ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Fixing configuration page- port can be added into URL * ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Users can access settings directly via cogwheel button on internal server error to possibly fix terminal configuration * ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Amount of copies are limited to 9999 so it behaves same as KM native applications ### 2025.01.09 **Legend:** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Added feature ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Improved/changed feature ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Bug fixed **PMC Client** * ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) MacOS users can now specify paperSize, duplex and color when installing the PMC Client in unattended mode (HCP-13908). * ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) User no longer gets logged out unexpectedly when the cloud connection is not established fast enough (HBT-5048). * ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) When PMC Client cannot operate with the existing token it will drop it and re-register itself (HBT-5031). * ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) "Domains" field of the "Customer information" is no longer case sensitive and does not cause problems when authorizing clients (HBT-5041). **Sharp Gen 2 Cloud Terminal - Production release** * ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) A user can select a destination folder at the Sharp terminal (HCP-13605). **Web Admin UI** * ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) An administrator can send a test email using the inherited mail configuration (HCP-13855). ![image-2025-1-9_15-24-23.png](https://docs.ricoh-pmc.com/__attachments/a_4d04936e5ddec53954764adb6fbb76e22daa66c3e94c509b97ac5f1430e31db7/image-2025-1-9_15-24-23.png?cb=29e9a3dd1b2855dc49892febaa75b395) * ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Left menu minor improvements (HCP-13891). * ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) reCaptcha was added to protect also forgotten password screen (HCP-13791). * ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) URL is generated correctly when navigating through the Admin Web UI (HBT-5050). * ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Significantly simplified experience to "Add device" (HCP-13801). ![image-2025-1-9_15-41-33.png](https://docs.ricoh-pmc.com/__attachments/a_75df04d18dbf75fc43a807cfa1e31bb3392141eed0fa63b4c9e86fab5575a4d6/image-2025-1-9_15-41-33.png?cb=5eb2c166ceb437008f74f71d0192b747) **Xerox Gen 2 Cloud Terminal** * ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) VersaLink 2nd Gen devices now correctly install on Windows 11 (HBT-5008). **Kyocera Embeded Terminal** * ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Users no longer see internal login "user1" when logged into the terminal. Instead, it shows "Kyocera" so it is less misleading (HBT-4243). **Scanning** * ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) The OCR engine was updated to the latest ABBYY FRE 12.6 (HCP-13399). --- version: "2026.08.20" variant: "PMC" language: "en" --- # 2026 **Important: Legacy port consolidation --- migration dates set** . Migration to port 443 will be carried out progressively starting from **16 September 2026** , and port 2560 closes progressively from **30 September 2026**. ## What you need to do, before 16 September 2026 * Upgrade all PC Clients and Gateways to **2026.06.25 or later**, across the whole estate. Watch for machines excluded from auto-update or from your deployment tool. * Confirm outbound **port 443 (TLS 1.2+)** to your tenant domain is permitted by your firewall and web proxy, and test from every relevant network segment, not just one. * If you want to migrate a customer sooner, your partner can request per-tenant migration from Y Soft ahead of the global enablement. Components on older versions that cannot reach port 443 will lose connectivity once the migration is enabled, and recovery is manual on every affected machine. Components on **2026.06.25** or later are safe in the same situation: they stay on the legacy port until port 2560 itself closes, which gives you time to fix the firewall. ### What is changing We are consolidating all communication onto **port 443 (HTTPS / WebSockets, TLS 1.2 or newer)**, in two steps: 1. **Port 2560 (Gateways and PC Clients) - September 2026.** * We are retiring the legacy communication channel on port 2560. Unlike the rest of our communication, this channel cannot be managed, monitored, or updated on a per-customer basis, which is why it is being removed first. * **From 16 September 2026:** we enable the migration to port 443 globally, across all data centers. Every Gateway and PC Client that meets both conditions below switches to port 443 automatically. * **From 30 September 2026:** port 2560 is closed, progressively, data center by data center. 2. **All remaining legacy ports --- by end of January 2027.** Port 443 has been the default requirement and setting for over two years, so the large majority of connections already use only 443. Some older components --- certain terminals, clients, mobile apps, and other legacy elements --- may still connect over legacy ports. Those ports will be closed by end of January 2027. We are adding tenant-specific reporting so we can identify affected customers ahead of time and notify them through their partner. Reducing the number of open ports also simplifies configuration and lowers the platform's exposure surface. ### Two conditions for a smooth migration **A. PC Client and Gateway on version 2026.06.25 or later.** From this version, the component verifies that port 443 is actually reachable before switching to it. If it cannot reach 443, it stays on the legacy port and retries later, without losing connectivity. **B. Outbound port 443 to your tenant domain is not blocked.** The component must be able to reach your tenant domain (for example customer.eu.ysoft.cloud) on port 443 with TLS 1.2 or newer: not blocked on the firewall, and not broken by a web proxy or TLS inspection. **Note that upgrading alone does not migrate a component.** If it was originally deployed with legacy communication settings, it stays on the legacy port even on a current version. The migration enabled on 16 September is what moves it to 443, and it succeeds safely only when both conditions are met. ### No change to Local communication between clients and on-premises Gateways is unaffected. ### Questions Please contact your Y Soft account manager or partner. ## 2026.08.20 ✅ **Added feature** ℹ️ **Improved/changed feature** ⚠️ **Bug fixed** ⚠️ **Secure print preferences no longer revert to a default profile** (HBT-6451) A defect in preference resolution meant that a user's saved paper size and color settings could silently fall back to a default profile (Letter size, greyscale) after some time, with no indication that anything had changed; signing out and back in temporarily masked the problem. The underlying lookup and fallback logic has been corrected so a user's own preferences are no longer silently overridden. ### Admin Web UI ℹ️ **Refreshed navigation and menu appearance** (HCP-17230) The navigation menu and its icons, and the top bar logo layout, have been visually updated for a more consistent look across the product's web interfaces. ![image-20260824-113309.png](https://docs.ricoh-pmc.com/__attachments/a_32ae9da37360cffd2f1929ba1a3d2b233e377d080bef26a01fc80a341a3421fd/image-20260824-113309.png?cb=a638e7ed729764b0a3099d504a3526cf) ### Authentication ⚠️ **Users are no longer logged out roughly every hour due to a stale directory connection** (HBT-6528) A pooled directory-server connection that had silently gone stale could be mistaken for the user not existing, which caused a token refresh to fail and the client to log the user out, typically about once an hour. The connection is now recognised as stale and refreshed, so this recurring logout no longer happens. ⚠️ **IP allow-list on API keys now works when accessed over port 443** (HBT-6456) When an API key's allowed-IP restriction was enforced through a reverse proxy on port 443 rather than a direct connection, the restriction was not applied. Requests are now filtered correctly regardless of which port they arrive on. ⚠️ **User Groups reporting no longer drops group membership for users with no department set** (HBT-6566) A print or scan job's group membership was only recorded if the user had a department value set; for users without one, all of their group memberships were silently omitted from reporting. Group membership is now recorded whenever it is available, regardless of whether a department is set. ### PC Client ⚠️ **Client no longer fails to connect when a proxy exclusion is configured for a domain** (HBT-6512) The client incorrectly checked proxy exclusion rules against the full host and port instead of the host alone, so a login could fail even though the destination was meant to bypass the proxy. Proxy exclusions are now evaluated correctly. ⚠️ **Client no longer falls back to the system proxy when a PAC script requests a direct connection** (HBT-6629) When automatic proxy discovery returned a "no proxy" result from a PAC script, the client could not distinguish that result from a discovery failure, and fell back to system-wide proxy settings anyway. A successful "no proxy" result is now respected, and no further fallback is attempted. ⚠️ **Client service on Linux and macOS now stops correctly when asked to** (HBT-6636) The client's background service on Unix-based platforms did not respond to a stop signal, so commands to stop the service, for example during a controlled shutdown or restart, had no effect. The service now shuts down correctly when requested. ### Cloud Terminal updates Some improvements and fixes require updated versions of Cloud Terminals. Please refer to the vendor-specific terminal release notes for details and required terminal versions. **Konica Minolta** ⚠️ **Quick scan tiles no longer change position between logins** (HBT-6540) The order of quick scan workflow tiles on the terminal's Quick Actions screen could change from one login to the next, making a tile appear to have moved or gone missing, an effect most noticeable with longer translated labels. Tile ordering is now stable across logins. ⚠️ **Pressing Enter while filling a scan workflow field no longer logs the user out** (HBT-6556) On terminals using the web-based scan workflow form, pressing Enter in a single text field triggered the browser's default form submission, which reloaded the page and logged the user out. Enter no longer submits the form, so the session is preserved. ### Legacy terminal support To support the ongoing migration away from legacy communication ports, the following terminals now proactively try to switch to port 443 on startup, rather than only falling back to it if the legacy port fails. **Sharp** ℹ️ **Proactive migration to port 443** (HCP-17140) The terminal now attempts to switch to port 443 on startup instead of waiting to fall back to it. **Konica Minolta IWS** ℹ️ **Proactive migration to port 443** (HCP-17141) The terminal now attempts to switch to port 443 on startup instead of waiting to fall back to it. ### Scan Workflows ⚠️ **SharePoint Online connector now resolves sites correctly for multi-geo Microsoft 365 tenants** (HCP-17116) The connector always addressed SharePoint sites relative to a tenant's default region, so scans failed to reach a site hosted in a different region of a multi-geo Microsoft 365 tenant, with no available workaround. Sites are now addressed correctly for multi-geo tenants. ⚠️ **A scan-to-download job that already succeeded is no longer marked Failed** (HBT-6546) If the email notification sent after a scan-to-download job completed took too long to send, the job could be reported as failed even though the document had already been stored and downloaded successfully, and its status was incorrectly reverted to Failed. The document's status is no longer overwritten once it has reached a final state. *** ** * ** *** ## 2026.08.06 **Legend:** ✅ **Added feature** ℹ️ **Improved/changed feature** ⚠️ **Bug fixed** ### Admin Web UI ✅ **Search bar for print queues** (HCP-16922) The Print Queues list in the Web admin UI now has a search bar, matching the search already available for printers and embedded terminals. Administrators managing large numbers of queues can filter them by name or by the printer they belong to instead of scrolling the full list. ℹ️ **Higher default card length limit for new card templates** (HCP-16998) The default card length limit for newly created card templates has been raised from 20 to 64. The field now also shows a hint explaining that this value has to match across embedded terminals so that a card works on all devices. ⚠️ **Printer status no longer stays OK after a terminal is uninstalled** (HBT-6582) After uninstalling a terminal from the Printers page, the printer kept reporting OK instead of Not installed whenever a user had signed in on that terminal before the uninstall, and stayed in that state for all later install cycles. The status is now reported correctly. ⚠️ **Deleted certificates are no longer left behind as stale records** (HBT-6558) When all remaining certificates except the token signing certificate were deleted, either between synchronisation windows or within a single window, the certificate records were not removed and stale entries were left in place. Deletions are now synchronised correctly. ### Authentication ⚠️ **Email addresses can again be used as a user full name** (HBT-6572) Since the previous release it was no longer possible to create a user whose full name is an email address, through either the Web admin UI or the API, because of stricter validation introduced with additional cross-site scripting protection. Such users can be created again. ⚠️ **Self-registration for session users can be disabled after a licence change** (HBT-6511) On accounts that were created with a direct-print-only licence and later moved to a licence with secure printing, the setting controlling self-registration of session users was hidden, so administrators could not turn it off even though it was still active. The setting is now available regardless of the current licence. ### PC Client ⚠️ **Print jobs no longer rejected as unsupported data on some Canon devices** (HBT-6505) PDF jobs produced by the client failed on several Canon imageRUNNER ADVANCE models with the panel error "Could not execute because the file contains unsupported data", while the same document printed correctly when uploaded through the Web UI. The jobs produced by the client are now accepted by these devices. ⚠️ **macOS client no longer changes the default printer on every sync** (HBT-6516) Printer synchronisation on the macOS client changed the default printer each time it ran. The behaviour has been narrowed so that it matches the Windows client. ⚠️ **Large documents no longer crash the universal print driver** (HBT-6418) Printing documents of roughly one hundred pages or more could crash the driver because of a buffer overflow, with the job failing before it reached the queue. Large documents now print reliably. This fix requires an updated driver version. ⚠️ **Advanced print options can be cleared again once they have been used** (HBT-6417) After an advanced option such as booklet or a setting on the Features tab had been selected once, it behaved as the effective default and could not be turned off, so later jobs were still produced with it even when the option was set to none. Each job now follows the option chosen for it. This fix requires an updated driver version. ℹ️ **Printer ports that the operating system still reports as in use are handled more cleanly** (HBT-4578) After a printer was removed, the Windows print spooler could continue to treat its port as in use until the spooler service was restarted, which surfaced as a misleading failure when the port was cleaned up. This situation is now handled without reporting a spurious error. ### Secondary Gateway ⚠️ **Re-registration now propagates the current credentials** (HBT-6406) When a bridge was re-registered after a failure, the new API key, registration code and endpoint identifier were not propagated, so the bridge kept using stale values and had to be recovered manually. Re-registration now updates them correctly. ⚠️ **Bridges no longer end up without their site server** (HBT-6497) A timing problem during enrollment meant the notification that a device had registered could be processed before its configuration was stored, and was then discarded instead of retried. The bridge reported itself as operational while remaining offline under Endpoints and Servers, because the site server was never deployed. The notification is now retried. ### Cloud Terminal updates Some improvements and fixes require updated versions of Cloud Terminals. Please refer to the vendor-specific terminal release notes for details and required terminal versions. **Xerox** ✅ **Stapling and punching in the copy application** (HCP-14696) The copy application on the Cloud terminal now offers stapling and punching options. This matters where device locking is not available and kiosk mode is used to restrict unauthorised use of the device, because only the copy application is then available to users. **Ricoh** ⚠️ **Jobs from the native PostScript driver are processed correctly** (HBT-6487) Jobs produced by the vendor's native macOS PostScript driver arrive without PJL headers, and the Cloud terminal assumed such jobs were PDF. The terminal now checks the actual format before processing the job. ⚠️ **Card reader configuration works when port 80 is disabled** (HBT-6243) Configuring a card reader with the terminal deployment tool failed on devices that had port 80 disabled, even though only secured ports were expected to be used. The configuration now completes over a secured connection. **FUJIFILM BI** ⚠️ **Card authentication survives waking the device from sleep** (HBT-6489) When the secure print and scan application was set as the screen default, so that it relaunched automatically on wake, card authentication silently stopped working after the device woke from sleep and users could no longer sign in with a card. Card authentication now remains available. **Sharp** ⚠️ **Documents are no longer released multiple times** (HBT-6561) Tapping print all, or the print button in the job list, several times in rapid succession started the print process once per tap, so documents were released repeatedly and errors appeared on the panel. Repeated taps are now ignored while a release is already running. **HP Workplace** ℹ️ **Device locking with the authorization agent service** (HCP-17013) The Workpath terminal has been updated to 1.6.3, which adds support for device locking through the authorization agent service. ## 2026.07.23 **Legend:** ✅ **Added feature** ℹ️ **Improved/changed feature** ⚠️ **Bug fixed** ### Admin Web UI ℹ️ **Primary domain is now explicit for multi-domain accounts** (HCP-16916) Accounts with multiple domains now have an explicit primary domain rather than one inferred from list order. Changing it prompts a confirmation, and the change is recorded in the audit log. ![image-20260727-130043.png](https://docs.ricoh-pmc.com/__attachments/a_ddfe2df52efa063b8ceb586c231b3d87c4b8679887d5d3ad5d7c2b2ab4b27dcd/image-20260727-130043.png?cb=d4aad01c63c18c3104a20d5db2427094) ⚠️ **Scheduled dashboard reports no longer arrive with a blank screenshot** (HBT-6507) Large scheduled user and printer email reports could include a completely blank screenshot due to a rendering race. The capture now completes reliably regardless of dashboard size. ⚠️ **Document color-page detection corrected** (HBT-4609) Documents processed without native color detection support were being marked entirely as color pages, which could affect reported page counts. Detection is now accurate. ### PC Client ⚠️ **Fixed a crash after manual printer synchronization** (HBT-6407) The Windows client could crash immediately after a manual synchronization completed. The underlying issue has been resolved. ⚠️ **macOS driver now supports borderless printing** (HBT-6529) Full-bleed content previously printed with an unwanted margin on all sides. Borderless paper sizes are now available. ### Secondary Gateway ⚠️ **Large print jobs routed via a secondary server no longer time out** (HBT-6422, HBT-6436) Larger jobs sent through a secondary server, or over port 443 with IPP authentication enabled, could fail partway through. The outbound request timeout has been corrected. ### Authentication ⚠️ **Fixed card login failure after card conversion on embedded terminals using a gateway** (HBT-6502) A card conversion could break subsequent card logins on embedded terminals connected via a gateway. Login now works reliably after conversion. ### Cloud Terminal updates Some improvements and fixes require updated versions of Cloud Terminals. Please refer to the vendor-specific terminal release notes for details and required terminal versions. **Xerox** ⚠️ **Corrected paper type for envelope printing** (HBT-6395) Selecting an envelope size when printing via Secure queue could result in plain paper being used instead of the configured envelope tray. The correct tray is now selected. ## 2026.07.09 **Legend:** ✅ **Added feature** ℹ️ **Improved/changed feature** ⚠️ **Bug fixed** ### Admin Web UI ⚠️ **Remove icon is displayed again in the Locations edit panel** (HBT-6482) The remove icon is now is now displayed correctly. ⚠️ **Guest self-registration shows the correct validity for short expirations** (HBT-6356) When a guest account's expiration was configured to less than 24 hours, the guest self-registration page displayed "0 days". The page now shows an appropriate time unit ("4 hours" or "1 day, 2 hours"), consistent with the guest activation emails. ⚠️ **Corrected French translations for API key types** (HBT-6469) Several API key type labels (General, Embedded, Chrome extension, Edge) were translated incorrectly in French. The translations have been corrected. ⚠️ **Recurring schedules calculate the next monthly run correctly** (HBT-6503) Recurring schedules (weekly / monthly / quarterly / yearly) now calculate the next run date correctly even around month boundaries. The scheduled runs now trigger on the right day. ⚠️ **Container-level Printers view no longer reports a valid license as expired** (HCP-16322) Printers viewed at container level could display "Your license has expired" despite a valid account license, and the message persisted after a replacement license was applied. The license state is now displayed correctly. ### PC Client ⚠️ **Old client versions are removed after auto-update** (HBT-5535) After an automatic update, older client versions were sometimes left behind in the client folder. The client now reliably removes the previous version once the update has completed. ⚠️ **Correct staple position for landscape jobs printed from macOS** (HBT-6343) Multipage landscape documents sent from the macOS client were stapled in the wrong position on Konica Minolta Cloud Terminals. Staple placement is now correct for landscape jobs. ### HP ℹ️ **Additional logging for OxPD** (HBT-5914) Extended logging on the HP OxPD embedded terminal now captures more data. ### Cloud Terminal updates Some improvements and fixes require updated versions of Cloud Terminals. Please refer to the vendor-specific terminal release notes for details and required terminal versions. **Canon** ℹ️ **Canon Cloud Terminal uninstallation** (HCP-16850) Uninstallation is now fully integrated into the UI and into the Terminal Deployment Tool (TDT). ### Other **Stability and security improvements** (HBT-6148, HBT-6463, HBT-6464) ## 2026.06.25 ✅ **Added feature** ℹ️ **Improved/changed feature** ⚠️ **Bug fixed** ### Admin Web UI ⚠️ **MFP licence count now displayed in manage terminal modal** (HBT-6414) An issue where terminals could not be installed to printers without an embedded terminal type in the manage terminal modal has been resolved. The MFP licence count is now also shown in this modal. (HCP-16588) ⚠️ **License violation grace period surfaced to administrators** (HBT-6413) Administrators are now notified of a license violation grace period before printing stops. Previously, the grace period was silent and admins were unaware until the printer ceased to function. ⚠️ **Wrong timezone in PIN expiration notification email corrected** (HBT-6443) PIN expiration notification emails now use the correct timezone when displaying the expiration date and time. ⚠️ **Enabling Direct print without a vendor no longer throws an exception** (HBT-6445) An issue where enabling Direct print on a printer that was added without a vendor caused an exception and saved the printer without a print queue has been resolved. ⚠️ **Translation corrections in Japanese and other languages** (HBT-6453) Several incorrect Japanese translations in the document and reporting UI have been corrected, including mistranslations for "jobs" and "duplex". The welcome message now correctly includes the product name in all non-English languages. (HBT-6448) ⚠️ **Minimum PC client auto-update version displayed consistently across languages** (HBT-6371) The minimum PC client version for auto-update was displayed inconsistently across different UI languages. This has been corrected so the same version is shown regardless of the active language. ### PC Client ℹ️ **New channel mode port 443 check before migration** (HCP-16645) The PC client in channel mode now checks port 443 availability before attempting to migrate, reducing connectivity failures during transitions. ℹ️ **PC client now attempts port 443 migration from legacy gateway** (HCP-16709) A PC client connected to a gateway via legacy ports now correctly attempts to migrate to port 443 when the legacy ports are no longer available. ⚠️ **PC client on macOS: high CPU and energy usage resolved** (HBT-6437) An issue where the macOS PC client caused abnormally high CPU and energy usage due to a continuous ThemeChanged event loop in the tray icon has been resolved. ### Scan Workflows ℹ️ **Scan email templates improved for new customer accounts** (HCP-16797) Scan-to-email templates for newly created customer accounts have been improved to provide clearer and more complete email content out of the box. ⚠️ **Scan-to-mail workflow no longer silently fails after logout race condition** (HBT-6450) A race condition where the finishScan call could be deferred behind an accounting cleanup and race a logout --- resulting in a 403 error and the scan-to-mail workflow never triggering --- has been resolved. ### Secondary Gateway ⚠️ **Edge gateway no longer gets stuck after prolonged health check failure** (HBT-6419) An issue where the edge gateway would get stuck and require a manual restart if its health check was unresponsive for 30 minutes or more --- as observed after a datacenter outage --- has been resolved. The gateway now recovers automatically. ### Managed Print API ℹ️ **Terminal installation: serial number now required for TDT-installed devices** (HCP-16757) When installing terminals to printers that were added via the Terminal Deployment Tool, the serial number is now required, consistent with the behavior for other device types. ℹ️ **Manage terminal modal: improved error handling for unhappy paths** (HCP-16587) Additional error cases and unhappy paths in the manage terminal modal have been handled, providing clearer feedback when terminal installation encounters issues. (HCP-16586, HCP-16588) ### Cloud Terminal updates Some improvements and fixes require updated versions of Cloud Terminals. Please refer to the vendor-specific terminal release notes for details and required terminal versions. **Xerox** ⚠️ **Xerox Gen 2 terminal no longer stuck on "Please wait" on devices without a scanner** (HBT-6457) Xerox Gen 2 Cloud Terminals on devices that do not have a scanner installed were getting stuck indefinitely on the "Please wait" spinner and never rendering the login screen. This has been resolved. ⚠️ **Xerox AltaLink C82xx booklet center stapling now working** (HBT-6441) An issue where booklet center stapling was ignored on Xerox AltaLink C82xx devices --- with the job printing and folding but no staples applied --- has been resolved. **Canon** ℹ️ **Canon Cloud Terminal installation time reduced** (HCP-16658) The installation time for the Canon Cloud Terminal has been significantly reduced, speeding up the deployment process. **HP Workplace** ⚠️ **HP Cloud Terminal now correctly switches to port 443 when legacy ports are cut off** (HCP-16778) An issue where the HP Cloud Terminal did not switch to port 443 when legacy ports were disabled has been resolved. ### Other **Stability and security improvements** (HBT-6428, HBT-6349, HBT-6390) ### End of Life ℹ️ **End of life notice for Equitrac embedded clients** (HCP-16724) Equitrac embedded clients have reached end of life. Customers currently using Equitrac embedded integrations should plan their migration to supported alternatives. ## 2026.06.11 **Legend:** ✅ **Added feature** ℹ️ **Improved/changed feature** ⚠️ **Bug fixed** ### PC Client ℹ️ **More resilient login token refresh** (HCP-15984) The client token refresh logic now better tolerates short server or network outages, reducing unwanted logouts. ⚠️ **Configuration profile is applied correctly on macOS** (HBT-5248) The configuration profile downloaded from the server was not reflected in the system print dialogs on macOS. Print settings defined in the configuration profile are now applied correctly. ⚠️ **User stays logged in after installation and automatic update on macOS** (HBT-4701, HBT-5871, HBT-6337) After an automatic update, or shortly after installation in managed deployments, the client re-registered the endpoint and invalidated the user session, so users were unexpectedly logged out. The session is now preserved. ⚠️ **Erroneous message at computer shutdown on Windows** (HBT-5867) Users no longer receive an error message from the client every time the computer shuts down. ⚠️ **Connection to a secondary gateway with self-signed certificates** (HBT-6396) The client on Windows failed to connect to secondary gateways that use self-signed certificates. Gateway connectivity now uses native certificate validation, restoring support for these environments. ⚠️ **Hotfix added later:** * **update to 2026.06.11 caused the PC client sync to change the default printer (HBT-6484)**This is no longer happening. * **Unattended installation on Mac PC client is now correctly recognized as a fresh installation**. (HBT-6490) #### Admin Web UI **✅ PC Client auto-update allows a delayed update cycle** (HCP-16723) It now offers two modes of operation: * Latest (default) --- PC Clients update to the latest stable release, published alongside each server release. Updates are rolled out gradually and monitored. * Previous - PC Clients **stay one release behind the latest** and still update automatically with each new release. Switching from Latest downgrades all clients already running the latest release. Choose Latest to keep clients on the same version as the server. ⚠️ **Add New service button respects permissions** (HBT-6153) Users without the permission to create a document output service no longer see a functional Add New button in the printer edit screen. ⚠️ **Public API validates user details** (HBT-6319) The public API endpoint for updating users accepted invalid values (for example a non-numeric user validity), which could break the automatic removal of expired guest users for the whole environment. The input is now validated and the issue can no longer occur. ⚠️ **License usage no longer counts deactivated printers** (HBT-6409) The periodic license recalculation incorrectly included deactivated printers, which could push an account into a false license-exceeded state. Deactivated printers are now excluded from the counts. #### Printing ⚠️ **Print jobs with large driver metadata** (HBT-6372) Print jobs sent from drivers producing large job metadata failed to spool. The metadata limit has been extended so these jobs now print correctly. #### Cloud Terminal updates Some improvements and fixes require updated versions of Cloud Terminals. Please refer to the vendor-specific terminal release notes for details and required terminal versions. **HP Workplace** ⚠️ **Scanned pages keep their original paper size** (HBT-6140) When scanning documents with mixed paper sizes, all pages in the output were formatted to the largest size. Each page now keeps its own paper size. #### Other **Stability and security improvements** (HBT-6273, HBT-6423, HBT-6376) ## 2026.05.28 **Legend:** ✅ **Added feature** ℹ️ **Improved/changed feature** ⚠️ **Bug fixed** ### Admin Web UI **🔄 Removal of PC Client Auto-update delay** (HCP-16722) Client updates are now distributed using a gradual rollout model, where updates are released in phases to subsets of devices and validated before reaching all clients. This approach improves overall **stability and availability** compared to updating all devices at once after a fixed delay. 💡 Impact * It is no longer possible to configure update postponement (e.g., delay by X days). * This change was not included in the original release notes. 💡 Next steps * Support for staying on **current‑1 version** is planned for upcoming releases. ℹ️ **Streamlined terminal management** (HCP-16330) Terminal management has been consolidated into a single, redesigned flow. The legacy "Manage terminals" dialog and the separate "Find on my network" option have been removed in favor of the new tabbed "Add printer" and "Manage terminals" experience, which already covers auto-discovery and uninstall. ⚠️ **Email to Print section on My Documents now has its own visibility permission** (HBT-6061) The list of Email to Print addresses on the My Documents page is no longer shown based on the download permissions (ViewPcClientDownload / ViewMobileAppDownload). Its visibility now follows the dedicated Email to Print permission, so the section appears only for users who are actually allowed to use that feature. ⚠️ **Non-functional options removed from My Documents for Container domains** (HBT-6348) When an end user signed in through a Container-specific domain, the "Submit your documents" panel previously offered Email to Print, mobile/QR print, and PC Client options that do not work in that context. These elements are now hidden for Container domains to avoid confusion. ⚠️ **Embedded configuration is preserved when creating output ports via the API** (HBT-6255) Creating or updating an output port with an embedded terminal configuration ID through the public API no longer saves the port without that configuration. The embedded configuration provided in the request is now reliably attached. ⚠️ **Restore-default-API-key action is no longer available at vendor level** (HBT-6331) The button to recreate the default API key was incorrectly available on vendor accounts. It is no longer shown, as a default API key should never be re-created at that level. ⚠️ **Corrected Danish translation on the Create account screen** (HBT-6363) A wrong Danish translation on the Create account screen has been fixed. #### Printing ⚠️ **ColorPrint restriction is now enforced for Direct print** (HBT-6314) When a role has ColorPrint restricted, the restriction was applied to Secure (pull) print but silently ignored for Direct (push) print, so colour jobs still printed in colour. The restriction is now enforced for both Secure and Direct print. #### PC Client ⚠️ **SSO session preserved when switching between Citrix session hosts** (HBT-6198) In pooled Citrix environments with a roaming profile, switching between session hosts could cause the PC Client to interpret a different install ID as a changed installation, delete the session files, and log the user out. This no longer happens, so SSO is retained across session hosts. ⚠️ **WebSocket reconnect no longer appears as being logged off** (HBT-6332) A race condition with a stale session cookie after a WebSocket reconnect could make active users appear logged off during printing. The session is now handled correctly on reconnect. ℹ️ **PC Client logs now capture more diagnostic information** (HBT-5322) PC Client logging has been extended on both Windows and macOS --- graceful start and stop of the client application and the client core service are now recorded, and session reuse messages provide more detail --- making support investigations easier. Security and stability improvements (HBT-6273, HCP-16246) #### Cloud Terminal updates Some improvements and fixes require **updated versions of Cloud Terminals** . Please refer to the **vendor-specific terminal release notes** for details and required terminal versions. **Canon Cloud Terminal** ✅ **Canon Cloud Terminal is now generally available** (HCP-15351) The Cloud Terminal for Canon multifunction devices is now generally available to all accounts. A default Canon embedded application type is available out of the box, so administrators can deploy the terminal directly from the terminal configuration --- no special enablement is required. **Xerox Gen 2 Cloud Terminal** ⚠️ **Booklet printing folds the whole stack correctly** (HBT-6216) Booklet jobs on Xerox AltaLink devices with a finisher were folding each sheet separately instead of folding the whole stack as a book. Booklet folding now behaves as expected for both push and pull print. ⚠️ **Scan Workflow email search keyboard hides automatically** (HBT-6358) During an email search in a Scan Workflow on the Xerox Cloud Terminal, the on-screen keyboard stayed visible after the search ran, hiding the results. The keyboard now disappears automatically so the results are immediately visible. **Ricoh Gen 2 Cloud Terminal** ⚠️ **Advanced embedded license now usable for Ricoh printers** (HBT-6336) Customers holding only an Advanced embedded (PMC) license, without a regular Embedded license, can now create and configure Ricoh embedded output ports with an Advanced terminal template. Previously the product behaved as if no embedded license were present. **Konica Minolta IWS Gen 2 Cloud Terminal** ⚠️ **Borderless print option now respected** (HBT-6163) The Konica Minolta IWS Gen 2 terminal now correctly honors the borderless print header, so jobs requesting borderless output are handled as expected. ## 2026.05.14 **Legend:** ✅ **Added feature** ℹ️ **Improved/changed feature** ⚠️ **Bug fixed** ### Admin Web UI ⚠️ **Configuration Profiles link now opens the correct page** (HBT-5876) The "Configuration Profiles" link under **Settings → Customer account → Regional → Default paper size** now opens the PC Client → Configuration Profiles tab instead of a blank page. ⚠️ **API key form no longer resets when enabling Automatic endpoint deletion** (HBT-6247) When creating or editing an API key, toggling **Automatic endpoint deletion** previously cleared the rest of the form (name and other options). The toggle now activates without resetting the surrounding fields. #### PC Client ⚠️ **PC Client refreshes proxy settings after a network change** (HBT-6299) The PC Client now detects network changes --- for example switching between Wi-Fi and Ethernet, or moving to a network with a different proxy --- and refreshes its proxy configuration accordingly, instead of continuing to use the previously detected value. ⚠️ **System printers preserved across concurrent RDP sessions on Windows** (HBT-6308) A combination of token-refresh timing and a second user starting a fresh RDP session could cause the PC Client to misclassify a long-running remote session as local and delete the system printers, leaving the original user unable to print until they manually re-synced. Remote-session detection has been hardened so printers remain in place across these handovers. ⚠️ **No spurious error notification while the PC Client is still connecting** (HBT-6328) With session authentication enabled, the PC Client no longer surfaces a transient error notification when the login is initiated before the core service has finished connecting. ⚠️ **Simplex jobs released as simplex with custom drivers** (HBT-6222) Print jobs submitted as simplex through a secure queue using a custom driver are no longer silently released as duplex. Page format and number of copies are also correctly preserved when using non-default drivers. #### Cloud Terminal updates Some improvements and fixes require **updated versions of Cloud Terminals** . Please refer to the **vendor-specific terminal release notes** for details and required terminal versions. **Xerox Cloud Terminal** ⚠️ **Reliable completion of rapid scan jobs** (HBT-5748) On Xerox AltaLink Cloud Terminals, submitting many scan jobs in rapid succession within a single user session could occasionally leave one job without a finish-scan notification, so the scan was not delivered (for example, not emailed). Scan completion is now reliably signaled for every uploaded job. **Konica Minolta Cloud Terminal** ⚠️ **Direct Print of uploaded PDFs is now correctly collated** (HBT-6033) PDF jobs uploaded through KM Direct Print are now collated by default, matching the behavior of secure print. Users no longer need to manually reorder pages when printing multiple copies. **Sharp Cloud Terminal** ⚠️ **Terminal initializes on devices without a scanner** (HBT-6275) Sharp devices without a built-in scanner (for example BP-B547PW) no longer fail terminal initialization with an "Action not supported" error. Scanner-dependent widgets such as **My scan workflows** are now automatically hidden on these devices. ## 2026.04.30 **Legend:** ✅ **Added feature** ℹ️ **Improved/changed feature** ⚠️ **Bug fixed** ‌ ✅ **PIN expiration notification email** (HCP-16144) Users now receive an automatic email when their Cloud PIN code is about to expire under the configured PIN expiration policy, so they can regenerate a new PIN before authentication is disrupted. Users who intentionally have no PIN configured (e.g., card-only users) are not notified. ### Admin Web UI ⚠️ **Trigger-based document assignment now persists in the database** (HBT-5541) The "Assign document" action in trigger rules now correctly updates the document record in the database, so the assignment is reflected across the system. ⚠️ **Removing a server preserves services shared with other servers** (HBT-6288) Removing a server through the Admin Web UI no longer cascades and deletes services that are also associated with other servers --- only services unique to the removed server are cleaned up. ⚠️ **Inherited role assignments are now protected from deletion** (HBT-6249) The Web UI now prevents administrators from deleting inherited role assignments, which previously led to inconsistent permissions. ℹ️ **Improved "Move selected to" modal in Organize Tree** (HCP-16263) The "Move selected to" modal in the Organize Tree view has been refreshed for clearer navigation and easier tree selection. ![image-20260504-112445.png](https://docs.ricoh-pmc.com/__attachments/a_1e2c639b74c1590436b98956021687de55fa822c8f3f77fd6c6b3943011971ec/image-20260504-112445.png?cb=ff62e1f18c9ddb94a1a5454d6ac7d277) ‌ #### PC Client ✅ **Modern UI in PC Client** (HCP-16239) A modernized PC Client user interface for configuration lands in 2026.04.30 including system dark mode support. ![image-20260504-142409.png](https://docs.ricoh-pmc.com/__attachments/a_42a44428e11fc766dbb50a5898d9192955962928d78b0348802df4b3a9a6d07e/image-20260504-142409.png?cb=83ea5b2eae8783390c0ad764add1dd5c) ℹ️ **Terminal Deployment Tool (TDT) for macOS now bundles its own Java runtime** (HCP-15687) The macOS distribution of the Terminal Deployment Tool now ships with a bundled Java runtime, removing the need to install or configure Java separately before running TDT. ⚠️ **Reliable write permissions on the TDT extraction folder (macOS)** (HBT-6272) The TDT installer now correctly applies write permissions to its extracted directory on macOS, so subsequent operations no longer fail with permission errors. ⚠️ **Print queue installation now succeeds in Windows Protected Print Mode** (HBT-5966) Print queues now install reliably on Windows machines that have Protected Print Mode enabled. ⚠️ **Uninstaller cleans up the installation folder reliably** (HBT-6134) The PC Client uninstaller now removes empty installation folders properly, even when the working directory is locked or the installation path uses symlinks with trailing backslashes. ⚠️ **Desktop shortcuts refreshed after PC Client upgrade** (HBT-6262) Shortcut targets are refreshed during PC Client updates so they no longer point to old, removed binaries after an upgrade. ⚠️ **Silent Windows installs respect the configured connectivity port** (HBT-6267) Silent Windows installations no longer overwrite the configured single-port setting to 443. On-premises gateways that expose the Cloud API only on port 7300 continue to work after a silent install. ‌ #### Authentication ⚠️ **Office 365 messaging works when Entra ID UPN differs from primary email** (HBT-6199) OAuth2 authentication for Office 365 messaging now succeeds for accounts whose Entra ID userPrincipalName (UPN) differs from the primary email address. ‌ #### Cloud Terminal updates Some improvements and fixes require **updated versions of Cloud Terminals** . Please refer to the **vendor-specific terminal release notes** for details and required terminal versions. **Xerox Cloud Terminal** ⚠️ **Advanced finishing options for pull-printed jobs** (HBT-5383) Stapling, punching, and other advanced finishing options now apply correctly when pull-printing on Xerox Cloud Terminal, completing the finishing-option support introduced in earlier releases. ⚠️ **Cancel print job returns the device to its idle state** (HBT-6276) Cancelling a print job on Xerox AltaLink C/B82xx no longer leaves the device stuck in "Cancelling..." until sleep mode kicks in. The device returns to the home screen immediately after cancel. **FUJIFILM BI Cloud Terminal** ⚠️ **Color print jobs on monochrome printers** (HBT-5620) Print jobs containing color content can again be released through FUJIFILM BI Cloud Terminal when the printer is configured as monochrome. **Konica Minolta Cloud Terminal** ⚠️ **Page counts for KM Universal PS print jobs** (HBT-6233) Page counting for jobs printed through the KM Universal PostScript driver now reports the correct number of pages instead of always reporting 0. **Ricoh Cloud Terminal** ⚠️ **Corrected text in the Scan Workflow help notice** (HBT-6219) A typo in the Scan Workflow help notice on Ricoh Cloud Terminal has been corrected. ‌ #### Secondary Gateway ⚠️ **Gen 2 terminal authentication on secondary gateways** (HBT-6257) A regression introduced in earlier 2026.03 builds caused all Gen 2 cloud terminal requests on a secondary gateway to fail with HTTP 500. Licensing checks are now correctly forwarded from the secondary to the primary, and Gen 2 devices on secondary gateways operate normally again. ‌ #### Legacy terminal support ℹ️ **Legacy terminals are no longer offered for new tenants** (HCP-12891) New tenants can no longer select or configure legacy embedded terminals (HP Workpath Gen 1, KM IWS Gen 1, Ricoh SOP Gen 1). Existing tenants who already have at least one embedded profile using a legacy terminal continue to work and can create additional profiles with the same configuration. Affected legacy clients are now marked **(DEPRECATED)** in the Web UI. ‌ #### Security ⚠️ **Disabled unauthenticated WebDAV endpoint on primaries** (HBT-6231) The legacy WebDAV endpoint used by older Gateway-embedded terminals (`https://:7301/webdav`) was previously reachable without authentication on primary servers. This endpoint is now disabled on primaries (it remains available where Gateway-embedded terminals require it). Konica Minolta and Xerox cloud terminals are unaffected --- they have always used a separate, authenticated WebDAV server on ports 8711/443. ## 2026.04.16 **Legend:** ✅ **Added feature** ℹ️ **Improved/changed feature** ⚠️ **Bug fixed** ### Admin Web UI ℹ️ **Updated customer tree loading spinner** (HCP-16229) The customer tree now uses the new unified loading spinner when expanding nodes, improving visual consistency across the Web UI. ⚠️ **Resolved empty screenshots in scheduled reports** (HBT-6207) Scheduled reports sometimes delivered empty screenshot/chart sections even though the Excel data was correctly populated. Screenshots are now rendered and included as expected. ⚠️ **Return to printer list after saving a printer with advanced settings** (HBT-6242) Saving a printer while the "Show advanced settings" panel was open no longer leaves the administrator on a blank form --- the user is correctly returned to the list of printers. ⚠️ **Correct API key stored in token when additional API-key values are used** (HBT-6184) When logging in with an additional value of an API key, it could previously store the original API-key value in the access token, leading to "API key mismatch in token" errors on subsequent calls. The token now correctly records the value that was actually used ‌ #### PC Client ⚠️ **Windows installer: reliable handling of repeated reinstalls** (HBT-6125) The Windows installer now detects existing installation directories more reliably (wildcard check) and, on a second same-version collision, shows a clear error instead of silently overwriting the previous install. ⚠️ **MacOS auto-update now respects uninstaller removal** (HBT-6214) Customers who deploy a `skip_uninstaller` flag (or who have manually removed the GUI Uninstaller) no longer have the uninstaller re-added by auto-update. The flag is treated as the source of truth. ‌ #### Chrome Extension ⚠️ **Loading indicator shown while long requests are processed** (HBT-5842) The Chrome extension now shows a loading indicator when a request takes longer than expected, instead of appearing unresponsive. ‌ #### Cloud Terminal updates Some improvements and fixes require **updated versions of Cloud Terminals** . Please refer to the **vendor-specific terminal release notes** for details and required terminal versions. **Xerox Cloud Terminal** ⚠️ **Stapling finishing option on Xerox VersaLink** (HBT-5521) Stapling jobs now use the correct Xerox PJL command (`@PJL SET STAPLE=TOPLEFT`) on VersaLink devices --- stapling is applied instead of silently ignored. ⚠️ **Workaround for slight down-scaling of DOCX pull-prints on Xerox** (HBT-6206) Administrators can now configure an `EOPSCALE` trigger to counter the slight down-scaling that could occur when DOCX jobs submitted via the Universal Print Driver were pull-printed on Xerox cloud terminals, restoring full-size output. ℹ️ **Xerox Cloud Terminal reports device status** (HCP-16116) Xerox Cloud Terminal now reports device model, firmware and status information aligning its reporting with other vendor terminals. **HP Workplace Cloud Terminal** ℹ️ **HP Workplace terminal reports device status** (HCP-16162) HP Workplace terminal now reports firmware version, model, and device information once a day. **Ricoh Cloud Terminal** ⚠️ **Terminal version refreshed on Printers page after upgrade** (HBT-6108) After upgrading a Ricoh Cloud Terminal (for example via TDT), the Printers page now shows the new terminal version after the next user login, instead of keeping the previous version. ‌ #### Security ⚠️ **Improved secrets masking** (HBT-6192, HBT-6241) ## 2026.04.02 **Legend:** ✅ **Added feature** ℹ️ **Improved/changed feature** ⚠️ **Bug fixed** ### Admin Web UI --- Manage Terminals ✅ **Kiosk mode installation via Manage Terminals on Xerox** (HCP-16078) With a new toggle box in Manage Terminals interface administrators can now deploy kiosk mode directly. ⚠️ **Corrected default template assignment during terminal installation** (HBT-6189) When installing terminals via Manage Terminals, the default terminal template is now correctly assigned to discovered printers. #### Scan Workflows ✅ **Autocomplete and new metadata variables now generally available** (HCP-16043) The autocomplete selector and new metadata variables in scan workflows. See [Workflow variables](https://docs.ricoh-pmc.com/docs/latest/pmc/workflow-variables.md) ![image-20260407-085707.png](https://docs.ricoh-pmc.com/__attachments/a_79435163083ade3a1c4cf8066bedf1ae7e2acb6c5e26f8ec185c9dd52fb2035c/image-20260407-085707.png?cb=5a458cd31a48436aa6328019f0f3bedf) ✅ **Timezone configuration at account level** (HCP-16042) Administrators can now configure a timezone at the account level, with the option to override it at child levels. The timezone respects daylight saving time and clearly indicates the current UTC offset. If no override is set, child accounts inherit the parent's timezone setting. Note: this settings apply to the scan workflows only and will be extended for other parts of the system in the future. #### Admin Web UI --- General ⚠️ **Improved dynamic translations** (HCP-15976) Fixed an issue where certain UI elements were not translated when switching the page language. All translatable resources now update correctly without requiring a page reload. ⚠️ **Fixed UI refresh loop** (HBT-5824, HBT-6116) Resolved an issue where the Web UI could enter a constant refresh loop, preventing users from interacting with the interface. ⚠️ **Fixed "Create new..." button toggle behavior** (HBT-5602) The "Create new..." dropdown button in the Web UI header now correctly toggles on repeated clicks or hover. #### Cloud Terminals Some improvements and fixes require **updated versions of Cloud Terminals** . Please refer to the **vendor-specific terminal release notes** for details and required terminal versions. **Xerox Gen 2 Cloud Terminal** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Error display when card service is unavailable** (HCP-15667) Xerox cloud terminals now display a clear error message when the card service is down or experiencing connectivity issues, instead of silently failing. ⚠️ **Corrected FIFO print order on "Print all"** (HBT-6169) Jobs are now released in the correct first-in, first-out order when using the "Print all" button. #### Other ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Reduced Entra ID throttling impact** (HBT-6234) Updated the Microsoft authentication library (MSAL) to the latest version, reducing throttling impact on service accounts during card registration with incorrect passwords. ⚠️ **Corrected PDF conversion for high bit-depth images** (HBT-6164) Document conversion to PDF now correctly handles images with color depth greater than 8 bits per channel (e.g., 16-bit PNG from iPhone, 16-bit TIFF). ⚠️ **Corrected document deletion on older secondary servers** (HBT-6202) Resolved an issue where document delete operations could fail on older secondary servers with an "Account not found" error. ⚠️ **Security and stability improvements** (HBT-6212, HBT-6121, HBT-6122, HBT-6152, HBT-6190, HBT-6173, HBT-6179) Various security and stability improvements have been applied, including fixes for installer reliability, certificate configuration, and internal resource management. ## 2026.03.19 **Legend:** ✅ **Added feature** ℹ️ **Improved/changed feature** ⚠️ **Bug fixed** **Legacy CDN Domain Retirement** Effective **April 16, 2026** , Cloud is retiring the legacy CDN domain `cdn.everyoneprint.com` and moving to `cdn.ysoft.cloud`. Customers using explicit firewall exception rules for CDN traffic must update their allowlists to include `cdn.ysoft.cloud`. Otherwise, PC Client auto-updates and website downloads may no longer work after the transition. ### Admin Web UI ✅ **Manage Terminals now available for all license types** (HCP-15711) The Manage Terminals feature is now accessible for all license types.Terminal management is available at the Customer and Container level. ![image-20260323-073153.png](https://docs.ricoh-pmc.com/__attachments/a_bd4dad88d4dae1b25e11b8f75fc9031a88113c5e2b35d1324d9471ff50cf921d/image-20260323-073153.png?cb=1fe7b90faa2fbf09be7d84aae8898b8f) ✅ **Location-based terminal management** (HCP-15713) Administrators can now manage terminal deployments filtered by location. When a PC Client has a location defined, the Manage Terminals modal displays only printers assigned to that location, supporting multi-location deployments with overlapping printer IP ranges. ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Pre-filled credentials in Terminal Deployment Tool** (HCP-15865) The Terminal Deployment Tool modal now automatically pre-fills the username and password from the terminal template, reducing manual input during terminal installation. ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Terminal deployment guide accessible for all licenses** (HCP-15765) The manual deployment guide for Konica Minolta and HP terminals is now available regardless of the license type. ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Default watermark trigger for all accounts** (HCP-15898) All accounts now include a default watermark trigger (disabled by default), serving as a ready-to-use template that administrators can enable and customize. ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Improved audit log user identification for Entra ID** (HBT-6110) Audit logs now correctly display the authenticated user's name for Entra ID authentication, even when the user identity is resolved after the initial request. ⚠️ **Corrected savings report calculations** (HBT-6064) Saved sheets in the Savings report are now calculated correctly, accounting for the number of copies when determining total printed sheets. ⚠️ **Corrected documentation link in Audit logs** (HBT-6181) The link to documentation from the Reports → Audit logs page has been corrected. ⚠️ **Reduced duplicate feedback messages** (HBT-6131) Saving services no longer displays multiple duplicate success messages. #### PC Client ✅ **Automatic endpoint cleanup for reimaged environments** (HCP-15046) A new option in API key settings allows administrators to configure automatic expiration of endpoints after a defined period. This is useful for Citrix or other virtual environments where instances are periodically reimaged, preventing the accumulation of stale endpoints. ⚠️ **Installer now prevents parallel installations** (HBT-6128) The PC Client installer now detects if another instance is already running and prevents parallel installations, avoiding potential race conditions during service configuration and file operations. ⚠️ **Resolved installation directory lock during OAuth login** (HBT-6135) The browser window opened for OAuth2 login no longer locks the PC Client installation directory, preventing issues with uninstalling or updating the client. ⚠️ **Corrected EULA display in macOS installer** (HBT-6156) The EULA in the macOS Cloud Client installer is now displayed correctly. ⚠️ **Corrected German translations** (HBT-6161) German translations in the PC Client have been corrected, including proper capitalization and grammar. #### Cloud Terminal updates Some improvements and fixes require **updated versions of Cloud Terminals** . Please refer to the **vendor-specific terminal release notes** for details and required terminal versions. ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Expired or deactivated printers now restrict print and scan operations** (HCP-15669) When a printer is expired or deactivated, releasing print jobs from cloud terminals is now blocked with a clear error message. Scanning features are hidden for expired printers, preventing users from attempting operations on unavailable devices. ![image-20260323-074001.png](https://docs.ricoh-pmc.com/__attachments/a_3d6d317f500f53f9a89d210a4fdf146e26ca9c4d4a05222beda2172419abfafd/image-20260323-074001.png?cb=d72bb716ee89481cf88ebd7deca15e2c) **Konica Minolta IWS Terminal** ⚠️ **Corrected media type handling in cloud storage mode** (HBT-6109) Certain media types (such as thick paper or recycled) are now correctly applied to print jobs on KM IWS Gen2 terminals in cloud storage mode. ⚠️ **Prevented registration of blank card numbers** (HBT-6174) KM IWS terminals no longer allow registering card numbers consisting entirely of zeros, which represent unprogrammed or empty card reads. **Ricoh Cloud Terminal** ⚠️ **Corrected stapling position for landscape documents** (HBT-6117) Stapling now correctly respects document orientation when using PostScript print protocol. **Sharp Cloud Terminal** ⚠️ **Fixed scaling of borderless documents** (HBT-6162) Pull printing no longer scales down borderless documents. The Fit-to-Page option is disabled when borderless printing is active. #### Scanning ⚠️ **Improved temporary file cleanup** (HBT-6188) Temporary files created during multi-page scan separation by barcode are now properly cleaned up after the workflow completes. #### Other ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Faster MyDocuments page for large environments** (HBT-5745) The MyDocuments page now loads significantly faster for customers with a large number of printers by optimizing how terminal configuration data is retrieved. ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Improved client secret security** (HBT-6013) Client secrets configured in Authentication Providers settings can no longer be revealed after saving. The reveal icon has been removed and secrets are permanently masked once saved. ⚠️ **Corrected page size for uploaded office documents** (HBT-5749) The output page size is now correctly applied when uploading office documents for printing. ⚠️ **Corrected copy count with cloud storage and third-party drivers** (HBT-6076) Print jobs sent via the PC Client in cloud storage mode using non-standard drivers now correctly apply the specified number of copies. ⚠️ **Security and stability improvements** (HBT-6172, HBT-5965, HBT-5875) Various security and stability improvements have been applied, improved Entra ID token caching to prevent rate limiting under high load, and infrastructure updates. ## 2026.03.05 **Legend:** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Added feature** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Improved/changed feature** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Bug fixed** ### **PMC Client** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Configurable delay for client auto-updates** (HCP-15771) Client auto-updates can now be delayed by up to **240 hours (10 days)**. This provides administrators with greater flexibility to control update timing and reduce potential disruption. ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Improved security of automatic terminal authorization** (HCP-15769) The automatic authorization process for terminals installed via the **Terminal Deployment Tool (TDT)** has been redesigned to reduce the authorization window and improve security. ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Various Fixes** (HBT-6079, HBT-5365) The MacOS client installer no longer creates an unintended `/Applications/Contents` folder during installation. An issue where MacOS client auto-updates could cause users to be logged out has been resolved, ensuring uninterrupted user sessions during updates. #### **Mobile App** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Collect support information option for Android users** (HCP-15739) Android users can now use a new **"Collect support information"** option to gather diagnostic data. This simplifies troubleshooting by allowing users to easily provide relevant information when reporting issues. ![image-20260306-071759.png](https://docs.ricoh-pmc.com/__attachments/a_2b267f918cbe1ddcdfcfb5fc298929c396a7b69d15d7d08da5be767dbd86cc91/image-20260306-071759.png?cb=d99a6d1e688c63d3a2cf6e566ed6a030) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Improved mobile print connectivity stability** (HBT-5982) Improved stability of mobile printing connectivity to ensure the mobile application reliably communicates with print services using standard HTTPS connections. #### **Admin Web UI** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Automatic printer discovery on the network** (HCP-15642) Administrators can now discover printers on the local network using the **Printer Discovery Tool** . After starting discovery from the **Printers** page, detected printers are displayed and can be selected and added directly. A direct print queue is automatically created for each added printer, and the printer is assigned to the PC's location if one is defined. * For more details, see [Printer Discovery](https://docs.ricoh-pmc.com/docs/latest/pmc/printer-discovery.md) ![image-20260218-094248.png](https://docs.ricoh-pmc.com/__attachments/a_a1b3735043220f7b50266240f5353bdeebace7105a8319361095ec145e56046f/image-20260218-094248.png?cb=d59c0a60bed7a9a32a2acee8f514b702) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Various Fixes** (HBT-6091, HBT-6024, HBT-5953,HBT-6058) Resolved an issue where some print jobs could appear twice in document reports. Document reports can now be successfully exported even when covering longer time ranges. Uploading DOCX files now correctly displays the number of pages in the document. Document assignment using triggers now works reliably also for users authenticated through non-local authentication providers. #### Cloud Terminal updates Some improvements and fixes require **updated versions of Cloud Terminals** . Please refer to the **vendor-specific terminal release notes** for details and required terminal versions. **FUJIFILM BI Cloud Terminal** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Improvements to accounting accuracy, connectivity handling. (HCP-15187, HBT-6112, HBT-5909) **Sharp Cloud Terminal** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Improvements to print job release performance, packaging reliability, and dependency security updates. (HCP-14653, HBT-6105, HBT-5804) **Ricoh Embedded Terminal** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Added option to hide Scan Workflow from the device interface. (HCP-14778) **Konica Minolta IWS Terminal** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Fixed firmware version reporting in SAFEQ Cloud. (HBT-6115) **Xerox Pure Cloud Terminal** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Improved handling of print jobs completed with device-side errors. (HBT-5615) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **(Security Advisory) The card enrollment process has been improved to correctly handle multiple user swipes on all cloud embedded terminals.** We have enhanced the card enrollment workflow to improve resilience in cases where users did not complete the enrollment session. Previously, incomplete enrollment sessions could, in rare circumstances, result in an unintended card-to-user association. Update to the latest version of all respective embedded terminals is recommended. ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Correct accounting for public user jobs on legacy Konica Minolta OpenAPI terminals** (HBT-5645) Legacy Konica Minolta OpenAPI terminals now correctly handle accounting for documents released under a public user. Activities are no longer counted based on device counters and only authenticated user activity is included in reports. **Other** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Improved font support for uploaded and emailed print jobs** (HBT-5984) Additional fonts have been added to improve rendering accuracy when printing documents uploaded through print job upload or email ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Improved reliability of license expiration notifications** (HBT-6139, HBT-6114) The process that sends license expiration and account removal notifications has been improved to prevent unexpected failures and ensure emails are reliably delivered. ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Improved compatibility with OIDC when using Gateway** (HBT-6056) Using Gateway with an OIDC identity provider now works correctly. ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Corrected Azure App permissions for Entra ID** (HBT-4916) Permissions for the Azure application integrated with Microsoft Entra ID have been corrected to ensure proper authentication and integration behavior. ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Security and stability improvements** (HBT-6130, HBT-6103, HBT-6101) Various improvements were implemented to enhance system stability and security, including fixes for edge cases in authentication token handling and infrastructure scaling improvements. Infrastructure improvements were also applied to ensure automatic scaling of OCR processing resources under load. ## 2026.02.19 **Legend:** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Added feature** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Improved/changed feature** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Bug fixed** **Admin Web UI** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Configurable card length limit** The card number length is no longer restricted to 20 characters. Administrators can now configure the maximum card length directly in the device template settings. This provides greater flexibility for environments using longer card identifiers. (HCP-15623) ![image-20260220-113513.png](https://docs.ricoh-pmc.com/__attachments/a_e62a3416cd3b9feeadc0252434bceefbb4972f8b6783761205b26e5b5022ff13/image-20260220-113513.png?cb=c3a047e73b14df1275526e0d2aebc9e1) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Various user interface improvements** Multiple UI refinements have been implemented to improve usability, consistency, and overall experience across the Admin Web UI. (HBT-5885, HCP-15662, HBT-6042, HCP-15720, HCP-15708, HBT-6077, HBT-5979, HBT-5746) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Improved watermark compatibility with special PDF characters** Watermarks containing special PDF characters are now generated correctly. This ensures consistent output and prevents formatting issues in printed documents. (HBT-6078) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Correct display of delete button for user documents** The delete button for user documents is now displayed correctly in the interface, improving usability and document management. (HBT-6072) **PMC Client** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Reliable client connectivity on Windows 11 23H2** Client connectivity now works correctly on Windows 11 version 23H2. This issue has been hotfixed to ensure stable operation on the latest Windows release. (HBT-6062) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **More reliable unattended PC Client installations** Unattended PC Client installations now skip server connectivity checks. This prevents silent installation failures when the server is temporarily unreachable and ensures more reliable scripted or automated deployments. (HBT-5899) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Optional macOS GUI uninstaller component** The macOS GUI uninstaller is now an optional installation component. Administrators or users can choose whether to include it during installation. Installer logic has also been improved to correctly handle updates and rollbacks regardless of whether the GUI uninstaller is present. (HBT-5893) **Xerox Gen 2 Cloud Terminal** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Improved card enrollment reliability** The card enrollment process has been improved to correctly handle multiple user swipes. Previously, if a user initiated enrollment with an unknown card and left the screen unfinished, a second user swiping their card immediately afterward could have their swipe ignored. If the second user completed the process, the first user's card could mistakenly be enrolled. (HBT-5905) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Improved scanning performance on Xerox VersaLink devices** Scanning performance has been optimized on Xerox VersaLink devices, resulting in faster and more responsive scan operations. (HBT-6009) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Improved reporting of jobs completed with device errors** Print jobs that are completed on the device with an error condition --- for example, when duplex printing is requested but not supported by the device --- are now correctly reflected in reports. (HBT-5615) **License expiration notifications** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **More detailed license and tenant expiration emails** License expiration and customer tenant deletion notification emails now inform also about trials and have been significantly improved to include clearer and more detailed information. This helps administrators better understand timelines and required actions. (HCP-15726) **Other** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Updated KM OpenAPI terminal logo** The legacy KM OpenAPI terminal logo has been replaced with the updated version to ensure visual consistency. (HBT-5993) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Chrome extension user interface improvements** Several improvements have been made to the Chrome extension user interface to enhance usability and consistency. (HBT-6071) ## 2026.02.05 **Legend:** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Added feature** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Improved/changed feature** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Bug fixed** **PMC Client** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Smaller and faster client installation** The client installer is now smaller because Ghostscript is no longer included by default. It will be downloaded automatically only when needed --- for example, if you choose it during installation or when an update requires a newer version. This helps reduce installation time and disk usage. (HCP-15499) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Improved experience in Citrix environments** User roaming profiles are now supported across multiple Citrix instances. This means your client settings can follow you when you move between different Citrix servers, providing a more consistent experience. (HCP-15411) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **More control over updates in virtual environments** Auto-update can now be enabled or disabled in virtual environments (such as Citrix, RDS, or remote desktop sessions). It is disabled by default, as updates in these environments are usually managed centrally by IT administrators. This helps avoid unnecessary network usage and reduces the risk of temporary printing disruptions. (HCP-15457) ![image-20260206-095517.png](https://docs.ricoh-pmc.com/__attachments/a_c0fa91a9312cb45e3dba98c4a730497771a4ebdefe3ecfed839d484ac7f4b8d2/image-20260206-095517.png?cb=57052c138742938b8104f8469e41c2d0) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Improved connectivity using system proxy settings** The client now uses the system-wide proxy configuration to establish its connection. This means it can connect immediately without requiring you to sign in first, improving reliability in environments that use proxies. (HBT-6001) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Better compatibility with Windows Enterprise editions** Clients using local storage mode can now successfully connect to the cloud on certain Windows Enterprise versions where this was previously not possible. This improves compatibility and reduces setup issues in enterprise environments. (HBT-6062) **Sharp Gen 2 Cloud Terminal** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Improved security during terminal installation** Embedded OSA Application Signature Verification is now enabled by default during terminal installation. This adds an extra layer of security by ensuring only trusted applications are installed. (HCP-15501) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Cleaner interface when scan applications are disabled** When the *Enable Scan Application* setting is turned off, the *My Workflow* widget is no longer displayed. This helps keep the terminal interface uncluttered and aligned with the enabled features. (HBT-5792) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **More detailed logs for easier troubleshooting** You can now retrieve more than 1 MB of the most recent terminal logs. This provides better insight when diagnosing issues and speeds up troubleshooting. (HBT-6003) **HP Gen 2 Cloud Terminal** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **More reliable terminal registration** The terminal registration process has been improved to better handle temporary connection or service issues. This increases the chances of successful registration and reduces the need for manual retries. (HBT-5970) **Admin Web UI Usability Improvements** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **More reliable filename handling in scan workflows** When editing scan workflows, the filename input is now correctly preserved as you make changes, preventing accidental loss of entered values. (HBT-6038) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Fixed documentation links** Several links to the documentation have been corrected, making it easier to find the right information when you need it. (HBT-6019) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Clearer feedback after saving changes** Pages now scroll correctly after saving, ensuring that success messages and results are immediately visible. (HBT-5884) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Improved language switching** Issues where parts of the interface were not fully translated after changing the language have been resolved, providing a more consistent localized experience. (HBT-5913) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Faster search performance** Search speed across the Admin Web UI has been significantly improved, helping you find users, settings, and objects more quickly. (HBT-6000) **Other** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Extended retention for NFR and Trial accounts** NFR and Trial accounts are now deleted 90 days after expiration, extended from the previous 30 days. This gives administrators more time to review or renew expired accounts. (HCP-15688) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Clearer expiration notification emails** Expiration notification emails have received minor formatting and wording improvements to make them easier to read and understand. (HCP-15668) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **New migration documentation of page reporting** New, detailed documentation has been added to [Accounting capabilities of Gen 2 Cloud Terminals](https://docs.ricoh-pmc.com/docs/latest/pmc/accounting-capabilities-of-gen-2-cloud-terminals.md) providing clearer guidance. (HCP-15636) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Additional language support** Kazakh and Ukrainian localizations have been added, expanding language support for users in these regions. (HCP-15599) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Authentication reliability improvements** Several fixes have been implemented to improve authentication stability and reliability. (HBT-6015, HBT-6018) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Security enhancements** Multiple security fixes have been applied to further strengthen the platform. (HBT-5995) ## 2026.01.22 **Legend:** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Added feature** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Improved/changed feature** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Bug fixed** **Admin Web UI** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Improved license expiration notifications** Email notifications for expiring licenses have been enhanced and are now enabled by default for users with **ModifyLicense** and/or **EnterCustomerLicense** permissions. Administrators (or users with ModifyUser permission) can enable notifications for selected users, and users can opt in via **My Profile** . Notifications now clearly display the number of days until deletion and the affected customer domain. (HCP-15608, HCP-15607, HCP-15558, HBT-5987) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Clearer visibility of expired customers** The remaining number of days before an expired customer is permanently deleted is now displayed directly in the tree structure. This provides administrators with better visibility and control. (HCP-15587) ![image-20260123-122950.png](https://docs.ricoh-pmc.com/__attachments/a_cdd6022f3b0175553b889df5c94baba659ed48d5ed7b7662a816d646c00198fe/image-20260123-122950.png?cb=262e640285f4006bc55714930b11bc0d) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Reporting dashboard feedback survey** When accessing the new reporting dashboards, users are now invited to complete a short survey. This helps gather feedback to further improve reporting features. (HCP-15385) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **More flexible mobile and PC client visibility controls** Mobile app configuration can now be hidden from the **My Profile** section. The previous ViewClientAndMobileDownload permission has been split into two separate permissions: * ViewMobileAppDownload * ViewPcClientDownload This allows more precise control over which download options are visible to users. (HBT-5758) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Reliable download of undelivered scanned documents** Users can now successfully download scanned documents from the Web UI even if the original delivery failed. This ensures important documents remain accessible. (HBT-5990) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Improved edge device re-registration handling** If an edge device is added, deleted, and added again, it now correctly appears in the endpoints list. This prevents confusion and ensures accurate device visibility. (HBT-5403, HBT-5969) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Fixed loading of associated print queues** Under **Settings → Locations → View associated objects** , print queues now load correctly. (HBT-5941) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) Other minor UX improvements. (HCP-15179, HCP-14838, HCP-14646, HCP-14186, HBT-5898, HBT-5918) **Google Workspace support** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Simplified user group synchronization** User groups from Google Workspace can now be synchronized without requiring a service account. This simplifies setup and reduces administrative complexity. (HCP-15459) ![image-20260123-134529.png](https://docs.ricoh-pmc.com/__attachments/a_29879afd5e160b35acec222e1ebe2edd5997a06901a31be3ec62b7dad6093919/image-20260123-134529.png?cb=a9eded91f5edc4752e2fd3c06b29a790) **Other Improvements** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Automatic cleanup of old update files** Secondary servers now correctly remove outdated update files. This helps reduce disk usage and improves system maintenance. (HBT-5978) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Corrected expired guest account email links** The expired guest account notification email now always directs users to the correct login page, even in environments using a proxy. (HBT-5822) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Fixed print job notification email behavior** Issues where print job processed and print job failed notification emails were not correctly enabled have been resolved. (HBT-5964) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Security improvements** Multiple security enhancements and fixes have been implemented to strengthen platform security. (HBT-5935) ## 2026.01.08 **Legend:** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Added feature** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Improved/changed feature** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Bug fixed** **Admin Web UI** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Environmental impact reporting and scheduling** Reports now include environmental savings metrics based on: * Submitted but unreleased print jobs * Duplex printing usage Reports can also be scheduled and automatically delivered via email, making it easier to track sustainability efforts. (HCP-15481) ![image-20260109-085127.png](https://docs.ricoh-pmc.com/__attachments/a_31a8875fbcf61d3d12993ceb1b36e914f2f53018b132604eb5452a54509cf672/image-20260109-085127.png?cb=390200b25da7a9069ef9ee75d2b4365e) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Configurable print watermark rules** Administrators can now configure a basic text watermark rule for selected types of print jobs. When enabled, the watermark is placed in the bottom-right corner of the page and can be customized using advanced rules. Variables such as `{{timestamp}}` can be included to dynamically insert information into the watermark. (HCP-15494, HCP-15225) ![image-20260109-095710.png](https://docs.ricoh-pmc.com/__attachments/a_ad314196823de0b875de029f537226e265e2bcce95223752734a4e523b845e4c/image-20260109-095710.png?cb=70a0d36e8524d0570a5993698895556b) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Improved printer selection experience for end users** The **My Profile → Printers** page has been visually redesigned to improve clarity and usability. A search and filtering option has been added, allowing users to find printers more quickly. ![image-20260109-103208.png](https://docs.ricoh-pmc.com/__attachments/a_740eb5681222bd91a1e5d812e963793a078e47f2ab019d44b6f8aff99c43d15a/image-20260109-103208.png?cb=eda6604fbf6b0bdceafbcd0af1cfb81e) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Search and filter when configuring print queues** When creating or editing a print queue, administrators can now search and filter available printers instead of relying solely on a dropdown list. This improves usability in environments with many printers. (HCP-15488) ![image-20260109-090118.png](https://docs.ricoh-pmc.com/__attachments/a_b0f491e9dbb37a1b1e20b95643414dbd49651715f5f764ea0a45aec92de04c1d/image-20260109-090118.png?cb=37a252ca667c0ff7e2c95874fd82a8a1) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Improved audit logging for Google authentication** Google authentication errors and warnings are now properly recorded in the audit log. This improves traceability and simplifies troubleshooting. (HCP-15458) **Gen 2 Cloud Terminals** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Konica Minolta application access control** Administrators can now configure **Konica Minolta** Gen 2 Cloud Terminals to hide the "Applications" quick action. This prevents direct access to other configured applications and improves device control. (HCP-15453) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Improved Konica Minolta print reporting on BW devices** **Konica Minolta**Gen 2 Cloud Terminals now correctly report print jobs on black-and-white printers when using push print. (HBT-5889) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Improved locking mode configuration (Public Beta)** When using **Konica Minolta** Gen 2 Cloud Terminal with locking (public beta): * Administrators can change connection settings even while the MFD is locked * Printer details correctly display the admin password during another active admin session These changes improve manageability in secured environments. (HCP-15567, HBT-5936) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Accurate native scan accounting** Native scan accounting on **Konica Minolta** Gen 2 Cloud Terminal with locking (public beta) now reports correct data. (HBT-5492) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Sharp post-login redirection option** **Sharp** Gen 2 Cloud Terminals can now be configured to redirect users to the native home screen after login instead of opening the application quick start menu. This allows better alignment with customer workflows. (HCP-15421) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Improved card enrollment reliability on Sharp** The card enrollment process has been improved to correctly handle multiple user swipes. Previously, if a user initiated enrollment with an unknown card and left the screen unfinished, a second user swiping their card immediately afterward could have their swipe ignored. If the second user completed the process, the first user's card could mistakenly be enrolled. (HBT-5906) **Public API** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) OutputPort provides deployment stage info and extended cloud terminal status info when available. (HCP-15552) **Others** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Improved compatibility and stability** Stability and compatibility improvements have been implemented for: * FUJIFILM BI Gen 2 Cloud Terminal * HP Gen 2 Cloud Terminal (2025.12.29 release) * OmniBridge (HCP-14973, HBT-5955, HBT-5923) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Improved OpenLDAP compatibility** OpenLDAP authentication now succeeds even when the baseDN is set higher than the user's actual directory location. (HBT-5921) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Corrected email templates** * Expired guest account notifications now include the correct login link, even when using a proxy. * "Scan is ready to download" emails now correctly include the download link. (HBT-5822, HBT-5747) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Additional UI and security improvements** Various minor UI refinements and security fixes have been implemented to further improve platform stability and protection. (HBT-5886, HBT-5739, HBT-5722, HBT-5666, HCP-15456, HBT-5779, HBT-5877, HBT-5811, HBT-5954, HBT-5818) --- version: "2026.08.20" variant: "PMC" language: "en" --- # 2026 Cloud Terminals * [Konica Minolta IWS Gen 2 Cloud Terminal Release notes](https://docs.ricoh-pmc.com/docs/latest/pmc/konica-minolta-iws-gen-2-cloud-terminal-release-notes.md) * [Sharp Gen 2 Cloud Terminal Release notes](https://docs.ricoh-pmc.com/docs/latest/pmc/sharp-gen-2-cloud-terminal-release-notes.md) * [Ricoh Standard Gen 2 Cloud Terminal Release notes](https://docs.ricoh-pmc.com/docs/latest/pmc/ricoh-standard-gen-2-cloud-terminal-release-notes.md) * [Canon Gen 2 Cloud Terminal Release Notes](https://docs.ricoh-pmc.com/docs/latest/pmc/canon-gen-2-cloud-terminal-release-notes.md) * [FUJIFILM BI Cloud Terminal Release notes](https://docs.ricoh-pmc.com/docs/latest/pmc/fujifilm-bi-cloud-terminal-release-notes.md) * [Xerox Cloud Terminal Gen 2 Release notes](https://docs.ricoh-pmc.com/docs/latest/pmc/xerox-cloud-terminal-gen-2-release-notes.md) * [HP Workpath Gen 2 Cloud Terminal Release notes](https://docs.ricoh-pmc.com/docs/latest/pmc/hp-workpath-gen-2-cloud-terminal-release-notes.md) --- version: "2026.08.20" variant: "PMC" language: "en" --- # Access Control Access control entries define the security configuration for a given tree node -- account, printer, print queue, server, or service. Each entry consists of the security role and a user or group to which this role is granted when accessing this particular tree node. For example, if an access control entry with user **admin** and role **Administrators** exists, it means that user **admin** has full administrative permissions on that tree node. ## Default settings Access controls are inherited by default so that all sub-elements of the tree acquire the same configuration. Inherited access controls are greyed out and cannot be modified or deleted. You can override inherited access controls in the child nodes or add more entries for users from sub-accounts. The following screenshot shows how the access control list is displayed on the **Customer 1** node for the user from **Acme** **Corporation** vendor: ![image-2024-12-10_10-36-12.png](https://docs.ricoh-pmc.com/__attachments/a_f145eb4afa44f58b3225d7d64c29caf0f2c8cbdc6575df5909a67ac31535c1f3/image-2024-12-10_10-36-12.png?cb=023b2cb68990b01dfcd14af0d743b579) Which access controls are displayed depends on the user viewing the current node. Given the following hierarchy, ![access-controls-tree.png](https://docs.ricoh-pmc.com/__attachments/a_c78856bda7198919b8394850f879018086bffb14d4f0874a813bf2eba4d7e4a3/access-controls-tree.png?cb=f798a573891167e1d5025fa96e580445) the top-level administrator of the **Acme Corporation** vendor can see all access control definitions for all the nodes. The users who are logged in for **AcmeEU** account will not be able to see, change, or override access control definitions inherited from the parent **Acme Corporation** node. The users from **Customer 1** account will only see and be able to manage access controls defined in that account. ## Changing default inheritance of access controls for child nodes Be careful when changing the default inheritance for the access controls. Make sure you understand the effects of this action beforehand. You can restore the default inherited access controls on customer account child nodes by clicking **Reset child nodes**. To see this button in **Access Control** , you must have the **PropagateAccessControl** permission. ### Reset child nodes The reset child nodes action will remove overridden access controls from child nodes. Following up on the example above, in the **Customer 1** node, click **Reset child nodes** and confirm the action. You will then see that the access controls originating in the **Customer 1** node are now inherited, as per default: ![image-2024-12-10_10-44-12.png](https://docs.ricoh-pmc.com/__attachments/a_1d58a56740dded1d0c4d0f51de5a20d715b0a5ef79429a16e9024ab6d59e4e13/image-2024-12-10_10-44-12.png?cb=28834cc48fc489148f28076aa6d56451) ## Creating Access control records Creating Access control records involves selecting a user or group and assigning it a role. The search options for the user or group depend on the type and configuration of the authentication provider you create the record for. Differences in search functionality across authentication providers are described in the "**Limitations in user and group search functionality**" section below. Perform the following steps to assign a role to a user or a group: 1. On the **Users** page in **Access control** tab, click **Add** to create a new Access control entry. A new dialog window will open. 2. In **Authentication provider**, select the authentication provider for which you want to create the new access control entry. 3. In **Security role** , select the role that you want to assign to your users or groups. For creating, editing, or deleting roles see [Roles](https://docs.ricoh-pmc.com/docs/latest/pmc/roles.md). The roles available by default are: * Users * Support * Reporting * Administrators 4. You can assign the Security role either to a particular user/group or to all authenticated users: 1. If you wish to search for a particular user or group in your authentication provider, enter the user or group name in the **User or group name** field. In the following example, you have a group called "Administrators_Sydney" in your identity provider, and you wish to assign the Administrators role to its members. ![image-2024-8-20_8-8-16-new-edited.png](/__attachments/a_86d36febd0b888b352e3241245213c64cd8aafd25ee7e8bdc99df657cfe05f63/image-2024-8-20_8-8-16-new-edited.png?cb=bcf665dc99a4464589576445ec9eac63) 2. In the following example, you wish to assign the Reporting role to all authenticated users. In such a case, leave the **User or group name** field blank and click **Search**. ![image-2024-8-20_8-9-19-new-edited.png](/__attachments/a_65cf14d1f1e2a32572d484c6975208f1ee7e2a07488bf3eeb028140f61d5e29c/image-2024-8-20_8-9-19-new-edited.png?cb=b154ca7b287cd10eae8ba43d20cda9a1) 5. Click **Search**. 6. Select the user or group that has been found. 1. Example for Administrators: ![image-2024-8-20_8-11-39.png](/__attachments/a_383b64c85b9ccfdd6a61eeeea378b818271404ef35d8be361b39820559464f5e/image-2024-8-20_8-11-39.png?cb=7fee8feec08a3cfbe29e41edfde1fcc4) 2. Example for all authenticated users: ![image-2024-8-20_8-12-13.png](/__attachments/a_5a69f3fbb16a9795fed16fcac1f71bc171fe9020cccaa7681a26bb62d5a5bfe3/image-2024-8-20_8-12-13.png?cb=aa4fcdd0cd218c189fdd90fed8b95e96) 3. **Hints:** * You can search for any string of characters in the username. When searching a provider that uses the email address of the user as their username, you can search for a common value, such as "**.com**", to retrieve a list of multiple users. * You can create several Access Control records simultaneously by selecting multiple entries from the list -- hold `CTRL` or `SHIFT` and left-click the desired individual items, or range, respectively. 7. Click **Save**to create the access control record. ### Limitations in user and group search functionality The user and group search functionality depends on the authentication provider's type and configuration. Its limitations depend on whether PMC can access users and groups in the external identity management. #### Specific OIDC-only authentication providers Includes: * Microsoft Entra ID (with OIDC authentication enabled, and Service account authentication disabled) * Google (with OIDC authentication enabled, and Service account authentication disabled) * OKTA (with OIDC authentication enabled, and Service account authentication disabled) Such authentication providers don't have direct visibility into external identity management systems, but PMC can leverage their specific APIs and get a temporary access this information. An alternative to creating an Access control record without granting PMC temporary access to the external identity management system is to use the Cloud API. See the section "**Creating Access control records via Cloud API**" below. When creating an Access control record with this authentication provider, you will see a switch to enable or disable "Search in external identity management". ![image-2024-8-20_8-9-19-new-edited.png](https://docs.ricoh-pmc.com/__attachments/a_65cf14d1f1e2a32572d484c6975208f1ee7e2a07488bf3eeb028140f61d5e29c/image-2024-8-20_8-9-19-new-edited.png?cb=b154ca7b287cd10eae8ba43d20cda9a1) Search in external identity management disabled When this switch is disabled, only local search is performed. That means only users who have already logged in to PMC and groups that are already known by PMC can be searched. This can be limiting, especially if you want to select a group, as the system will only know the group locally once you have already assigned an Access control record to it. To search for a user who has not logged in yet or a group that has not yet been assigned an Access control record, you will need to enable the external search switch and grant one-time temporary access to your external identity management system's users and groups. The first time an administrator searches externally, they will be prompted to authorize additional delegated permissions in their Identity Provider. ![image-2024-8-20_8-23-44.png](https://docs.ricoh-pmc.com/__attachments/a_65113f55836f14bc9e64f3614d67aa6c4ac51922daf432fd7c0bf67b0c63c194/image-2024-8-20_8-23-44.png?cb=b9f749a9e8e1f58a6d35d0042b98cfd6) This process **may**require the authorizer to have administrative rights in the Identity Provider as well. The additional delegated permissions that will be added to the application registration for each provider are: | **Identity Provider** | **User Search Permission** | **Group Search Permission** | |-----------------------|-----------------------------------------------------------------|------------------------------------------------------------------| | Microsoft Entra | `user.read.all` | `group.read.all` | | Okta | `okta.users.read` | `okta.groups.read` | | Google | `https://www.googleapis.com/auth/admin.directory.user.readonly` | `https://www.googleapis.com/auth/admin.directory.group.readonly` | After successful authentication, close the browser tab, and click **Search** again to complete the access control mapping. ![image-2024-3-21_9-43-50.png](https://docs.ricoh-pmc.com/__attachments/a_231e3b69a922405ac241e493527a7dd56d4ec9a751d2947feebb82b6cf0e8034/image-2024-3-21_9-43-50.png?cb=24510ab3a9c844b4ffae7b9e347a8579) #### Client (OAuth2) authentication providers Includes: Any Client (OAuth2) authentication provider Such authentication providers don't have direct visibility into external identity management systems. Only users that already logged in to the system can be searched. Groups need to be manually synchronized into PMC before they can be searched when creating an Access control record. Administrators can perform a one-time synchronization of all groups in the external identity management system, so these groups can then be used during Access control record creation. Navigate to the documentation page of your authentication provider type for more info on how to perform the group sync. An alternative to creating an Access control record without granting PMC temporary access to the external identity management system is to use the Cloud API. See the section "**Creating Access control records via Cloud API**" below. #### Generic OIDC authentication provider Includes: Generic OIDC authentication provider This authentication provider has no means to connect to the external identity management system to access the users and groups. Therefore, only users who have already logged in to PMC can be assigned a role. Similarly, only the predefined "Authenticated users" group can be assigned a role. An alternative to creating an Access control record is to use the Cloud API. See the section "**Creating Access control records via Cloud API**" below. #### Authentication providers with Service access Includes: * Microsoft Entra ID (with Service account authentication enabled) * Google (with Service account authentication enabled) * OKTA (with Service account authentication enabled) * LDAP Such authentication providers have direct visibility into external identity management systems and, therefore, searching for users and groups is not limited. ## Creating Access control records via Cloud API This option is highly technical and requires specific skills to perform API calls, manage API keys, and related tasks. Please, proceed with caution. If unsure, contact PMC representative for help with this approach. It is also possible to use the Cloud API to create new Access control records. While this option is highly technical, it allows creating Access control records when the standard web form is insufficient. For example, this option can be used when the administrator doesn't want to give PMC access to external identity management. Creating an Access control record can be done via the [Add access control](https://ysoft.atlassian.net/wiki/spaces/sqcd/pages/26805472/API+Functions#Add-access-control) API endpoint. When creating a mapping for an external group, the `groupDn` parameter must contain the exact representation of the group returned by the external identity management system during the user's authentication; otherwise, the group names won't match. --- version: "2026.08.20" variant: "PMC" language: "en" --- # Access rules In order for users to be able to see and execute a scan workflow on a terminal, you must configure their access. By default nobody has access. ## Types of access rules Access to each individual workflow can be configured via rules on a **group** or **user**basis: * **Allow** -- the given user/group has access to the workflow. * **Deny** -- the given user/group is denied access to the workflow. ## Configuring access rules 1. In the PMC Web UI, go to **Scanning** \>**Access control** . ![AccessControl.png](https://docs.ricoh-pmc.com/__attachments/a_6608937693d8fbccd32836b0ddfb1dcff08883098ed46c330589ef0527af69db/AccessControl.png?cb=35afdccb7ba1a429ff9485a9d65c91f8) 2. To create a new access rule, click **Add** . You must have both the *ViewScanWorkflow* and *ViewScanWorkflowAccessRule* permissions to access the section, and at least*CreateScanWorkflowAccessRule* permission to create an access rule. 3. Configure the access rule: ![image2023-9-13_13-36-22.png](https://docs.ricoh-pmc.com/__attachments/a_87f58a64e95309bef79b3ebc5fc303043c38616476a7b9d24c4e471fa60f2930/image2023-9-13_13-36-22.png?cb=41af39614cf5498686c5bc6a9a5d25cf) * **Authentication provider** -- choose the provider which contains the target users or groups. * **Workflow** -- scan workflow for which the access should be granted/denied. * **Access** -- choose the type of rule to create for the target users or groups. * **User or group name** -- full-text search under the given authentication provider. If you leave the search field blank, all users and groups from the selected provider will be listed. In the selection box, either one or multiple users \& groups can be selected via standard selection methods (mouse drag, shift+click, ctrl + click). 4. Click **Save** . If you selected multiple users or groups, multiple access rules will be created after clicking **Save**. ## Effective workflow access evaluation To determine whether a user has access to a workflow (and therefore can see it on the terminal and execute it), the system is evaluating a combination of all configured rules that apply to the given workflow and target the actual user + any group, that the user is a member of. **Rules are evaluated with the following priority:** * Rules that target the user explicitly have higher priority than rules that target a group containing this user * Rules that deny access have higher priority than rules that allow access on the same level. For example, deny rule for a group is stronger than allow rule for a group, but it can be overruled by a user-explicit allow rule. Availability of the workflow for a user is also affected by the "active status" of the workflow itself -- even if a user has access to it, inactive workflows aren't shown on the terminal. --- version: "2026.08.20" variant: "PMC" language: "en" --- # Accounting capabilities of Gen 2 Cloud Terminals The following table provides an overview of the accounting capabilities of Gen 2 Cloud Terminals for each type of action (printing, copying, scanning). Refer to each terminal's documentation and limitations sections for more details. | | **HP** | **KM IWS Gen 2** | **KM IWS Gen 2 with device locking** | **Xerox** | **FUJIFILM BI** | **Sharp** | **Ricoh (G2.5+,** preciselySmartSDK 3+**)** | |------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------| | **Documentation** | [HP Workpath Gen 2 Cloud Terminal](https://docs.ysoft.cloud/docs/hp-workpath-gen-2-cloud-terminal) | [Konica Minolta IWS Gen 2 Cloud Terminal](https://docs.ysoft.cloud/docs/konica-minolta-iws-gen-2-cloud-terminal) | [Konica Minolta IWS Gen 2 Cloud Terminal with device locking (IWS Service Platform integration)](https://docs.ysoft.cloud/docs/latest/safeq-cloud/konica-minolta-iws-gen-2-cloud-terminal-with-device-locking-iws-service-platform-integration) | [Xerox Gen 2 Cloud Terminal](https://docs.ysoft.cloud/docs/xerox-gen-2-cloud-terminal) | [FUJIFILM BI Terminal](https://docs.ysoft.cloud/docs/fujifilm-bi-terminal) | [Sharp Gen 2 Cloud Terminal](https://docs.ysoft.cloud/docs/sharp-gen-2-cloud-terminal) | [Ricoh Standard Gen 2 Cloud Terminal](https://docs.ysoft.cloud/docs/ricoh-standard-gen-2-cloud-terminal) | | **Limitations** | [Limitations](https://docs.ysoft.cloud/docs/hp-workpath-gen-2-cloud-terminal#Limitations) | [Limitations](https://docs.ysoft.cloud/docs/konica-minolta-iws-gen-2-cloud-terminal#Limitations) | [Limitations](https://docs.ysoft.cloud/docs/latest/safeq-cloud/konica-minolta-iws-gen-2-cloud-terminal-with-device-locking-iws-service-platform-integration#Limitations) | [Limitations](https://docs.ysoft.cloud/docs/xerox-gen-2-cloud-terminal#Limitations) | [Limitations](https://docs.ysoft.cloud/docs/fujifilm-bi-terminal#Limitations) | [Limitations](https://docs.ysoft.cloud/docs/sharp-gen-2-cloud-terminal#Limitations) | [Requirements and limitations](https://docs.ysoft.cloud/docs/requirements-and-limitations) | | Download and print (e.g., **Print**using Pull Queue) | exact | estimated | exact | estimated | exact | exact | exact | | Push print local delivery (e.g., **Print**using Push/Direct Queue, Client Local storage) | exact | estimated | estimated | estimated | estimated | exact | exact | | **Print** using direct queue (using the solution) | estimated | estimated | estimated | estimated | estimated | estimated | exact *Accounted under the last authenticated user, may be accounted twice* | | Direct **print**to the printer IP (bypass the solution) | exact *Accounted under the* `hp_gen_2_unidentified_user`*user (if it exists in the customer's account).* | not tracked | not tracked | not tracked | not tracked | exact *Accounted under the* `direct_print`*user (if it exists in the customer's account).* | exact *Accounted under the last authenticated user* | | **Print**using native app (e.g., USB print) | exact *Accounted under logged-in user or under the* `hp_gen_2_unidentified_user`*user (if it exists in the customer's account) if no user is logged in.* | not tracked | exact | not tracked | not tracked | exact | exact | | **Copy**using Gen 2 Cloud Terminal | n/A *Not available on HP.* | exact | exact | estimated | n/A *Redirect to the native copy app.* | n/A *Not available on Sharp.* | exact | | **Copy**using the native app | exact *Accounted under the logged-in user or under the* `hp_gen_2_unidentified_user`*user (if it exists in the customer's account) if no user is logged in.* | not tracked | exact | not tracked | estimated *If one page is colored, everything is considered colored.* | exact | exact | | **Scan**using Gen 2 Cloud Terminal | exact *Everything is accounted for as color.* | exact *Color information might be incorrect.* | exact | exact *If one page is colored, everything is considered colored.* | exact *If one page is colored, everything is considered colored.* | exact | exact | | **Scan**using the native app | exact *Accounted under logged-in user or under the* `hp_gen_2_unidentified_user`*user (if it exists in the customer's account) if no user is logged in. Everything is accounted for as color.* | not tracked | exact | not tracked | exact *If one page is colored, everything is considered colored.* | exact | exact | ## Legend exact - accurately accounted by the terminal (reflects actual pages printed). estimated - accounted based on submitted print data (may not reflect pages actually released at the printer). not tracked - not accounted for at all, invisible to the solution n/A - not applicable ## Additional notes If you would like to know how the accounted pages translate into reports, see [Accounting - Impressions vs pages](https://docs.ricoh-pmc.com/docs/latest/pmc/accounting-impressions-vs-pages.md). ### Download and print vs Push print local delivery These two types of print actions apply when authenticating with the Cloud terminal and selecting a document to print. The terminal will choose the appropriate action based on the solution's MFP visibility. If the solution can see the MFP and push the document there directly, it will do so. Otherwise, it will fall back to the Download and print action. ### HP MFP admin can lock native applications to require user authentication. Our Cloud Terminal cannot lock native applications at the moment: only Workpath SDK v1.6.3 and newer support application locking, which is not yet publicly available. *** ** * ** *** Also see: [Reports](https://docs.ricoh-pmc.com/docs/latest/pmc/reports.md), [Accounting - Impressions vs pages](https://docs.ricoh-pmc.com/docs/latest/pmc/accounting-impressions-vs-pages.md) --- version: "2026.08.20" variant: "PMC" language: "en" --- # Accounting - Impressions vs pages This table shows the conversion between actual paper sizes and their representation in reports. | **Accounted unit** | **Reports unit** | **A4/Letter-equivalent count** | |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|--------------------------------| | Paper size | | | | **Normal size** * Letter (Small Letter), Letter extra, Legal * A4, (ISO A4, ISO A4 Rotated, A4Small), A4 Plus * B4 * Executive, Folio, Esheet * Fanfold STD German * Csheet **Small size** * A5, A6 * Statement, Note * B5, B5 Extra * Envelope, Env 10, PENV 1, PENV 4, Env DL, ENV C4, Env personal, Env B6, PRC7 Envelope Rotated * Japanese postcard, DBL Japanese Postcard * 180x210MM | A4 / Letter | 1 | | **Large size** * Tabloid (Ledger, 11x17, 17x11) * A3 (ISO A3, ISO A3 Rotated, A3 Traverse) * A3 Plus, A3 Extra, A2 * Fanfold US * Arch B 12x18 | A3 / Tabloid | 2 | | **Unknown or other** | A4 / Letter | 1 | *** ** * ** *** Also see: [Accounting capabilities of Gen 2 Cloud Terminals](https://docs.ricoh-pmc.com/docs/latest/pmc/accounting-capabilities-of-gen-2-cloud-terminals.md), [Reports](https://docs.ricoh-pmc.com/docs/latest/pmc/reports.md) --- version: "2026.08.20" variant: "PMC" language: "en" --- # Add a custom app in Microsoft Entra ID To create a custom application in Microsoft Entra ID, perform the following steps: 1. Log in to the Azure portal and click **Manage Microsoft Entra ID.** 2. Navigate to **Enterprise Applications \> All applications**. 3. Click **+New application** and then click **Create your own application.** ![image2023-11-7_10-3-31.png](https://docs.ricoh-pmc.com/__attachments/a_a074998a9821820b8562d918c61b11440f024ba567d66bed30545d2a0066fc1f/image2023-11-7_10-3-31.png?cb=4a1ce6d3a67df1e607e54d266e074c7f) 4. Name your application, select **Register an application to integrate with Microsoft Entra ID (App you're developing)** , and click **Create** . ![image2023-11-7_10-6-0.png](https://docs.ricoh-pmc.com/__attachments/a_efbfe80f2304a58ea19f03bb1bca841c763a0d64126836f78aae2ff847a56c84/image2023-11-7_10-6-0.png?cb=d21a873c75c583995524f82f0eab7029) 5. On the following screen, fill in the following values: 1. **Name** -- Represents the name of the application. 2. In **Supported account types,** select **Accounts in any organizational directory (Any Microsoft Entra ID tenant -- Multitenant)**. 3. In**Redirect URI** , select **Public client/native (mobile \& desktop) and enter** the URI. The field value should match this pattern: `https:///callback/azure`. The domain and the port should be the same as the ones of the PMC website URL. For example, if the PMC web URL is `https://print.acme.com:8443,`the value should be: `https://print.acme.com:8443/callback/azure`. In environments with reverse proxy infrastructure, do not specify the port number in the URL, meaning the default HTTPS port 443 will be used. Example: `https://print.acme.com/callback/azure`. ![image2023-11-7_10-29-46.png](/__attachments/a_bec3290b9deb7c195bc0bc2b8bba3fcd0c4b0fa0a7fd453bf8db3ce5c0ba1ff5/image2023-11-7_10-29-46.png?cb=0cb96bb6b8feb5a6c5fa51e540253bb4) 6. Click **Register**. 7. Navigate back to **Microsoft Entra ID** \> **Enterprise Applications** \> **All applications**. 8. Click your application (click refresh if it does not appear at first) to open the application details to copy the Application (client) ID. ![image2023-11-7_10-30-45.png](https://docs.ricoh-pmc.com/__attachments/a_3c53c31f8a3e65756cf820990f030d1b87e4355ba370e099103a679aecfba61f/image2023-11-7_10-30-45.png?cb=3d894f4d6922dcbc69958aeeceb55baf) 9. Log in to the PMC Web UI and go to **Users**. 10. On the **Authentication providers** tab, click **Add**. 11. A new dialog window will be displayed. ![image2025-4-23_16-13-20.png](/__attachments/a_4b160dab9e0d876533a108a5f33c14efdcc335ec64abe8158afb9b547b61fbca/image2025-4-23_16-13-20.png?cb=6b875a1bf3afae11c0d916de6327cce5) * In **Type** , select **Client (OAuth2)**. * In **Name**, enter the name of the authentication service. Should be prefilled with the selected Type. * In **Domains**, enter your Entra ID domain (Example: the "acme.com" part of john.doe@acme.com). * In **Identity provider** , select **Microsoft Azure OAuth 2.0**. * In **Custom application ID**, enter the value of the Application (client) ID from the newly created application. * In the **Callback domain for custom application** drop-down menu, select the domain that matches the one from the Redirect URIs that is already added in Azure application. The pre-selected value represents the domain from the PMC Web URL. For adding or updating the Entra Redirect URIs, go back to the Entra ID homepage in Azure portal and click **App registrations** . Click your application and then click **Authentication** . ![image2023-11-7_11-12-14.png](/__attachments/a_4141371c5b73f24523e6f2b68ace62b947c2aa5ce91ad11b524c030b425ea5b0/image2023-11-7_11-12-14.png?cb=9f5d5de0c81e6e348aca7a7a8d4d74af) * In **Services** , select **authentication service**. 12. Click **Save**. 13. Click **Sync groups**. 14. After that,the end users must accept all the required permissions. ![sync-groups-accept-all_v1.png](/__attachments/a_0c6563283c4ccbe26425534d58176486cffdfe7e7a2cb0fadec21722806a8be8/sync-groups-accept-all_v1.png?cb=302af2c6679bee4337b1af61509ba091) 15. When the users accept the permissions, the sync groups operation is done. If you perform the synchronization for the same account/application again, the users will not be required to grant permissions again. 16. Go to **Users** page and to **Access control** tab. ![image-2024-8-20_8-35-11.png](/__attachments/a_07dfe9824afabddd5ef89262d98f09f61ca1213300f9bbb16a8d92987ed3e617/image-2024-8-20_8-35-11.png?cb=a0021877b33a0378f644ab6d3a2dfa29) 17. Select your newly created authentication provider and click **SEARCH** . Then, the default group **Authenticated Users** and the Entra groups are visible. You can use all these groups in access controls to enable permissions for authenticated users. --- version: "2026.08.20" variant: "PMC" language: "en" --- # Add a custom app in the Auth0 identity platform This page describes the steps to create an authentication client application in the Auth0 identity platform. ## Creating a Native application 1. Log in to Auth0 identity platform and navigate to **Applications \> Applications** *.* ![image2023-4-18_15-24-21.png](https://docs.ricoh-pmc.com/__attachments/a_039b9b49c65c5a433fd3978e2abc4746f76b26fcc2840c546855e2b1cc680f9f/image2023-4-18_15-24-21.png?cb=f2adddd85041428077ab87810d875c23) 2. Click **Create application** . In **Choose application type** , click **Native** *.* ![2 create application.png](https://docs.ricoh-pmc.com/__attachments/a_3dc69d6143e29893b51716c5b3cc597e46919b96ea91df852ebb271a5426ed3b/2%20create%20application.png?cb=3710bb67cba47a5d4a2891b1dc1fb2b5) 3. In **Name**, enter the application name. 4. Click **Create** and go to the **Settings** tab. ![image2023-4-18_15-26-24.png](https://docs.ricoh-pmc.com/__attachments/a_7bbf0e41092edd5344c74b182431dc57133433e42dbf0cb89c6cc8ff1f01c061/image2023-4-18_15-26-24.png?cb=da061ca629f5c0b6bfc6eda4f5221e07) **Domain** -- The domain used for authentication. You will need this value to create the Client Authentication provider in the PMC web UI. **Client ID** -- The ID of the application. You will need this value to create the Client Authentication provider in the PMC web UI. 5. In **Application URIs** , enter the following URL in the Allowed Callback URLs field: http://127.0.0.1:7311/oidc/callback. This is necessary for end users to use the PMC Client with client-based authentication. ![image2023-4-18_15-27-45.png](https://docs.ricoh-pmc.com/__attachments/a_13d86f6d95984d4dcc6a52a975c961407ea8bc4dd3a45ac52ebe638d8b0cb0f7/image2023-4-18_15-27-45.png?cb=b3737fe4a3230335b55fafaa5944c140) ## Creating Client Authentication provider in PMC web UI 1. In the PMC Web UI, navigate to **Users**page and to **Authentication providers**tab. 2. Click **Add**to add a new Authentication provider. ![8cbd6bd7-427f-465f-8f4c-23d18107e41f.png](https://api.media.atlassian.com/file/8e5a0c9a-5ad0-4251-98df-30b5c72f0955/image?mode=full-fit&client=60fa17c8-8da1-46f3-87e3-bc17a59ee670&token=eyJhbGciOiJIUzI1NiJ9.eyJpc3MiOiI2MGZhMTdjOC04ZGExLTQ2ZjMtODdlMy1iYzE3YTU5ZWU2NzAiLCJhY2Nlc3MiOnsidXJuOmZpbGVzdG9yZTpmaWxlOjhlNWEwYzlhLTVhZDAtNDI1MS05OGRmLTMwYjVjNzJmMDk1NSI6WyJyZWFkIl19LCJleHAiOjE3NDU1MDM2MTcsIm5iZiI6MTc0NTUwMDMxN30.p_flx1EcuGBWWcTgIPBnrKeJpYGqPfCqZhrKn-m7Z90) Fill in the following fields: * **Domains** -- Enter the domains of all users (with emails *user@domain*)who will authenticate to PMC. * **Custom application id** -- Mandatory field. Enter the **Client ID** value of the Native application you created in the Auth0 platform. * **Auth0 Domain** -- Enter the **Domain**of your application in Auth0 platform. * **Client ID** -- Client ID of the application. * **Sync Groups - Client ID** - Client ID of the Regular Web Application. This field requires you to have a synchronization app in the Auth0 identity management. See [Add group synchronization app in the Auth0 identity management](https://docs.ricoh-pmc.com/docs/latest/pmc/add-group-synchronization-app-in-the-auth0-identity-management.md). * **Sync Groups - Client Secret** - Client Secret of Regular Web application. This field requires you to have a synchronization app in the Auth0 identity management. See [Add group synchronization app in the Auth0 identity management](https://docs.ricoh-pmc.com/docs/latest/pmc/add-group-synchronization-app-in-the-auth0-identity-management.md). * **Custom token claim names** - in this section, you can define claim names in the token. Their values will be stored in the user attributes after login. 3. Click **Save**. 4. (Optional) If you wish to synchronize groups from Auth0: 1. Click the edit icon next to your newly created Authentication provider. 2. Click Sync Groups to start synchronization of groups from your Auth0 account. For prerequisites, see [Add group synchronization app in the Auth0 identity management](https://docs.ricoh-pmc.com/docs/latest/pmc/add-group-synchronization-app-in-the-auth0-identity-management.md). ![image2025-4-24_15-10-42.png](https://api.media.atlassian.com/file/032f132b-e85b-4d38-9ec6-ea948935c97b/image?mode=full-fit&client=60fa17c8-8da1-46f3-87e3-bc17a59ee670&token=eyJhbGciOiJIUzI1NiJ9.eyJpc3MiOiI2MGZhMTdjOC04ZGExLTQ2ZjMtODdlMy1iYzE3YTU5ZWU2NzAiLCJhY2Nlc3MiOnsidXJuOmZpbGVzdG9yZTpmaWxlOjAzMmYxMzJiLWU4NWItNGQzOC05ZWM2LWVhOTQ4OTM1Yzk3YiI6WyJyZWFkIl19LCJleHAiOjE3NDU1MDM2MzgsIm5iZiI6MTc0NTUwMDMzOH0.AkIgzD9ilBOxqkkXHj8hDpCOFeZ_ZWza68z-LEKKLoU) 5. Go to the **Users**page and to **Access control** tab. 6. Click **Add** . ![image-2024-8-20_8-43-18.png](https://docs.ricoh-pmc.com/__attachments/a_9bca92bf0eac3cc3bda06c26f17874849d2efb907a64a218a718467674722ece/image-2024-8-20_8-43-18.png?cb=91a069a8997e92f008052a49e2150811) 7. In **Authentication provider** , select your newly created Authentication provider and click **Search**. 8. The default group**Authenticated Users** will become visible. You can use this groups and individual users in access controls to enable permissions for authenticated users 9. If the group synchronization is set up, Auth0 Groups will be visible too. For more information about Auth0 Groups see . ## Logging in as a user 1. When an end user logs in for the first time, they must authorize the app. ![authorization1.png](https://docs.ricoh-pmc.com/__attachments/a_9cb19127d6b3b52d98bdf3cc8c0444fc14c6bb2c245d1a9b1e84022833222e69/authorization1.png?cb=b9c9f1a162e51fb4705c3c7a1437fcb6) ![authorization2.png](https://docs.ricoh-pmc.com/__attachments/a_612a2858f4e01858a5ff2c031e3098742f473cf07ffee8b8e3331c297e9f7f5a/authorization2.png?cb=ddcee1c2777ef657e27fd3fe7f0034c7) --- version: "2026.08.20" variant: "PMC" language: "en" --- # Add a custom app in the Ping identity platform To set up authentication and group synchronization with the PingID provider, you must create an OAuth2 Worker application in your PingID environment: ![Ping13.png](https://docs.ricoh-pmc.com/__attachments/a_5fe6a689011d71acee6ae01a65f78ca50e08be867b2bd97c7e363a0be46b7c1a/Ping13.png?cb=39c3537a5bf64e4f55deb6dc2bb91dc0) ## Overview of steps Make sure to perform the following actions in the correct order, otherwise you might disable your existing authentication to your PMC tenant. These steps are: 1. Set up the authentication provider in PMC using a PingID Worker application. 2. Perform group synchronization for your PingID authentication provider. 3. Create Access Control records for the imported groups. Make sure that you will retain an administrative role in PMC when you log in using your PingID identity. You must create access control records with the Administrator role for the group where you are a member. ## OAuth2 Configuration Authentication to PingID is done via the PingID OAuth Worker application. Group synchronization with PingID is done via OAuth2 authentication of a user with administrative privileges for the Worker application. ### Creating the Worker application 1. Log into your PingID environment. Go to **Applications** andclick**+** to create a new application. ![Ping2.png](https://docs.ricoh-pmc.com/__attachments/a_2600653b22b78de459d0e61928d9ad9035180cf2c0aac1ff24a6a2d8f0f29c63/Ping2.png?cb=03f6626a62e30c70c2a87ad83dd28962) 2. Enter the **Application Name** , an optional **Description** , and select **Worker** as the **Application Type** . ![Ping3.png](https://docs.ricoh-pmc.com/__attachments/a_5f155a37592baf4b92766dca80911d78e3e126f27f25f06066a4dd334f1af9d4/Ping3.png?cb=5b1b5c31c5939d94fb59aeea2f514fba) 3. Click **Save** . ### Configuring the Worker application 1. Once saved, select the **Configuration** tab, and click the pencil icon to edit it. 2. In **Response Type** , select **Code.** 3. In **Grant Type**, select: 1. **Authorization Code** . Also, in the **PKCE Enforcement** field, select **OPTIONAL**. 2. **Refresh Token**. 4. Disable (uncheck) the **Client Credentials** grant type. ![Ping4.png](https://docs.ricoh-pmc.com/__attachments/a_ef2586f882d4b5a74ef79e1a9369c501d2159eacd0d9a4b1fd8b0c5eeeda4822/Ping4.png?cb=49d3b12485027e332fab79d782259798) 5. In**Redirect URIs** , enter the following: 1. ` http://127.0.0.1:7311/oidc/callback ` This redirect address is essential for the PMC Client to work correctly with PingID authentication. 2. `https://:8443/callback/ping`. In environments with reverse proxy infrastructure, do not specify the port number in the URL, meaning the default HTTPS port 443 will be used. ![Ping5.png](/__attachments/a_d7d8ab7106ac9e1a3ed747106809e22227497780bed2a16e990a4f45d9a455fb/Ping5.png?cb=37dafcc196dca038ac3b45cff1d8bca7) 6. In **Token Endpoint Authentication Method** , select **None**. 7. Click **Save**. ### Selecting Resources 1. Once saved, click the **Resources** tab, then click the pencil icon to edit it. Enable the following scopes: 1. email (OpenID Connect) 2. profile (OpenID Connect) ![Ping6.png](/__attachments/a_068a7ec4f0b61749f96c74ad9707f369b17cbd48c86e89442038e06a0f828972/Ping6.png?cb=a97f50d27900b6345281a358dae5f4de) 2. Click **Save**. ### Mapping the attributes 1. Once saved, click the **Attribute Mappings** tab, then click the pencil icon to edit. You should see one Attribute Mapping --- **sub = User ID**. 2. Change this mapping to **sub = Username** . ![Ping7.png](https://docs.ricoh-pmc.com/__attachments/a_3102d3451ccceddaf37128bb4942243569354c10588ab18b88fd2943a106aa74/Ping7.png?cb=125cd32442a85488b0335e64840eb761) 3. Click **Save**. ### Removing roles 1. Once saved, select the **Roles** tab. If there are any Roles listed, click the **Trash** icon to delete them, and **Save** once all are removed. If none are listed, proceed to the next step. ![Ping8.png](https://docs.ricoh-pmc.com/__attachments/a_bb68ec60822efbbedf828906c293b42ead78ce6c622543dc7534518e5c6108ea/Ping8.png?cb=6d539e940dbc41d6638f786dc409466d) For security reasons, it is essential to remove all roles from this application. This will restrict the ability to use the application without an OAuth2 token. OAuth2 token is more secure because it is not stored anywhere and acquired only in interactive mode. ### Enabling the Worker application 1. Click the **Overview** tab and click the slider in the top-right corner to enable your application. This will automatically save it. ![Ping9.png](https://docs.ricoh-pmc.com/__attachments/a_8b14abca2a277c21660d15ad4b036e58080fecd576f968ccedd01303eddfc1af/Ping9.png?cb=5b0c74f61079538947436fba7ec3bd6d) 2. Leave this page open as you will need access to some of the application IDs displayed there. ### Configuring the PingID Authentication provider in PMC Web UI Now that the configuration on the PingID side is complete, proceed to register and configure the Authentication Provider in PMC. 1. Log into PMC Web UI and go to **Users** page and to **Authentication providers**tab. 2. Click **Add**to add a new provider. 3. In **Type** , select **Client (OAuth2)** . ![image2025-4-23_15-56-10.png](https://docs.ricoh-pmc.com/__attachments/a_8d8871dc5e0114a3cb6239a2f4ea341469541d423531e8e1b76e8f2c48e2314b/image2025-4-23_15-56-10.png?cb=f05fafbbc24802f846f2ae181bc80f61) 4. In **Name**, enter the Authentication provider name. Should be prefilled with the selected type. 5. In **Domains** , list all of the domains present in your PingID environment that will need to authenticate to PMC. For example, to allow user *john.doe@acme.com* to log in via this Authentication provider, enter the *acme.com* domain here. 6. In **Identity provider** , select **Ping OAuth 2.0**. 7. In **Custom application ID,** paste the **Client ID** from your PingID application **Overview**tab. 8. In **Ping environment ID** ,paste the Environment ID from your PingID application **Overview**tab. 9. **Ping region** is the region in which your PingID environment is registered. You can determine it from your PingID Console URL which is in the format of ` https://console.pingone.[region]. `Alternatively, you can find it in any of the URLs listed under your PingID OAuth application **Configuration** tab such as ` https://auth.pingone.[region]/[client]/as/authorize ` 10. In **Callback domain for custom application** , enter the PMC tenant address you used as the **Redirect URI** in your PingID OAuth application configuration. 11. Click **Save**. For more details on the available options for OAuth2 authentication, see [Client authentication](https://docs.ricoh-pmc.com/docs/latest/pmc/client-authentication.md). ### Synchronizing groups After creating and saving your new Authentication provider, you can perform group synchronization, which will allow you to manage Access Control of your PMC tenant via PingID group membership. To synchronize groups perform the following steps: 1. On the PMC Web UI **Users** page, under the **Authentication** **providers** tab, click the **Edit**icon for your PingID provider. 2. Click **SYNC GROUPS** . ![image-2024-8-28_14-46-25.png](https://docs.ricoh-pmc.com/__attachments/a_97d1b8353dce8ea929c72ee0c25924512650779345ff1099006ee8d772d86691/image-2024-8-28_14-46-25.png?cb=487640a94c19ae416dde97131526e68a) 3. You will be redirected to the PingID login page. 4. Log in with an account that has permission to read groups and follow the on-screen instructions. When the form closes, group synchronization is complete. For more details, see [Client authentication](https://docs.ricoh-pmc.com/docs/latest/pmc/client-authentication.md), section *Sync groups*. 5. You will now be able to search for PingID groups on the **Access Control** tab of the **Users** page. For more details, see [Access Control](https://docs.ricoh-pmc.com/docs/latest/pmc/access-control.md). --- version: "2026.08.20" variant: "PMC" language: "en" --- # Add a secondary gateway server Install a secondary gateway when you need to add a new server to the existing deployment, where either a vendor or a customer primary server already exists. This page is applicable to [Gateway on Software Appliance](https://docs.ricoh-pmc.com/docs/latest/pmc/gateway-on-software-appliance.md) and [Gateway on Hardware Appliance](https://docs.ricoh-pmc.com/docs/latest/pmc/gateway-on-hardware-appliance.md). This is often necessary in the following cases: * Scalability, when some load should be distributed across multiple servers * Access to the private network, for example for authentication or embedded terminal deployments. Because primary server doesn't normally has access to the customer's internal networks an additional server is required which will connect to internal authentication services (LDAP) or to printers on the Intranet. If you want to send print jobs or use embedded terminal clients from a secondary gateway server, make sure you create a DNS entry for the server. For a complete guide to setting up an appliance and installing the gateway, see the [Gateway Guide](https://docs.ricoh-pmc.com/docs/latest/pmc/gateway-guide.md) section. To install secondary server the following options should be provided: ![secondary-params.png](https://docs.ricoh-pmc.com/__attachments/a_07d30c3446689dfb515d42e2208083794ad4420f784c529f74ccac134556e0d2/secondary-params.png?cb=2765c2e5d325a00432be410be20c4f3c) * **Primary server address** -- this is the IP address or domain name of the primary server. It does not have to match any DNS names of the accounts. * **Account domain name** -- this field should be filled with the DNS name of the account to which this server will be attached to. * **API key** -- optional API key from the account settings, used for server registration. If left blank the default restricted API key will be used. The installer will try to connect to the primary server and validate the entered information. If there is no connection or the specified account domain name is wrong the error message will be printed. If the entered details are valid installation will proceed. After the secondary server starts it will attach itself to the specified account. It will be possible to see it under the tree on the left side of the web UI. By default, secondary servers are "not trusted" by a primary server. So after adding the secondary server, go to the server's **Server information** and click **Authorize** to allow the secondary server to establish a secure connection to the primary server. ![server information2.png](https://docs.ricoh-pmc.com/__attachments/a_1e4daeba43622bc9d5aee1c3504e504f5feb741b23f8f9f2b699bc9f4ac2f961/server%20information2.png?cb=5cc6fe16957ec3318cea785fdd995661) --- version: "2026.08.20" variant: "PMC" language: "en" --- # Add group synchronization app in the Auth0 identity management To synchronize groups from Auth0, you must create a group synchronization application in the Auth0 identity platform. ## Creating a Regular Web Application in Auth0 1. Log in to Auth0 identity platform and go to **Applications \> Applications** . ![image2023-4-18_15-20-11.png](https://docs.ricoh-pmc.com/__attachments/a_eeafd0007688387e65a12093ba00dab34e4952befe03fc67d054225adacd4635/image2023-4-18_15-20-11.png?cb=f2adddd85041428077ab87810d875c23) 2. Click **Create Application**. 3. Enter the name of the application. 4. In **Choose an application type** , select **Regular Web Applications** . ![image2023-3-27_15-31-44.png](https://docs.ricoh-pmc.com/__attachments/a_706b7c13af6803d19acc28c4722b82b18275aa304c78254ad1e599465352405d/image2023-3-27_15-31-44.png?cb=053011416d2c9f97700e787e99d39613) 5. Click **Create**. 6. Go to the **Settings** tab. ![image2023-4-18_15-17-29.png](https://docs.ricoh-pmc.com/__attachments/a_f37e58f381492f53c269e6d27666cfe2e62eaadeb0e95445b7ad79a50c235020/image2023-4-18_15-17-29.png?cb=ca1b24a1360119309c1aa3b2368d9b27) **Domain** -- The domain used for authentication. This is common for all your applications. **Client ID** -- The ID of the application. **Client Secret** -- The client secret of the application. 7. Go to **Advanced settings \> Grant Types** . ![image2023-3-28_7-36-2.png](https://docs.ricoh-pmc.com/__attachments/a_fda5aac2a9b6778f3e8254299e748508a47a29980496322be41962d246d37041/image2023-3-28_7-36-2.png?cb=202b5f17f1a0cf16a1528851e0aae780) 8. Make sure that the following grants are selected: * Authorization Code * Refresh Token * Client Credentials 9. Go to**Applications \> APIs** . ![image2023-3-29_12-19-31.png](https://docs.ricoh-pmc.com/__attachments/a_dba195fab01b0d28f1ed8e2683098b0cef213dff04fb48661df3108df5761c18/image2023-3-29_12-19-31.png?cb=416832611c3090e980c02367dbf78aea) 10. Select the API you want your newly created application to access. 11. Go to to **Machine to Machine Applications** tab and find your newly created application. Authorize it, and in **Permissions** , select **read:roles** . ![image2023-4-18_15-4-5.png](/__attachments/a_0492afa931de139fb9d8210dc2acbea50252dd99b84623ae52a57e86bc7d5d03/image2023-4-18_15-4-5.png?cb=5f7efa0e97c964f16bf993189120d8a9) ### Adding user roles into the JWT token For more information, see Auth0 documentation: 1. In Auth0 Identity platform, go to **Actions \> Library \> Custom**. 2. Click **Build Custom**. ![image2023-3-28_8-0-49.png](https://docs.ricoh-pmc.com/__attachments/a_aa68aa8a8fd79ff5bdc8d14aa113fcbf971b1418ab88ae1317f52777a10619fe/image2023-3-28_8-0-49.png?cb=ba6b2a34b962ad5e4c56afa61c146b48) 3. Enter the Action name. 4. In **Trigger** , select **Login / Post Login**. 5. In **Runtime** , select **Node 16**. 6. Click **Create**. 7. An editor will be displayed. ![image2023-4-18_15-11-41.png](https://docs.ricoh-pmc.com/__attachments/a_01fd5cd2caaaecf1db7e1ab7b43911ab1aaf2388886d84c1a4cad024bed48b96/image2023-4-18_15-11-41.png?cb=b95aabea021373c8fc723ea331cd08a6) 8. Paste the following block of code and click **Deploy**. JavaScript exports.onExecutePostLogin = async (event, api) => { const namespace = 'SAFEQ Cloudsafeq_cloudDispatcher Paragon Clouddipa_cloudCloudStreamcloudstreampmcpmc'; if (event.authorization) { api.idToken.setCustomClaim(`${namespace}/roles`, event.authorization.roles); api.accessToken.setCustomClaim(`${namespace}/roles`, event.authorization.roles); } }; 9. Go to **Actions \> Flows \> Login**. ![image2023-4-18_15-14-23.png](https://docs.ricoh-pmc.com/__attachments/a_48eaebb577b13d9b20d6103242216b5b648514604a3bb88e26a6c0d39fa7d10d/image2023-4-18_15-14-23.png?cb=56077d4d61fa7dac6385fa7cd9579633) 10. Drag and drop newly created **Action** to **Login**flow. 11. Click **Apply**. --- version: "2026.08.20" variant: "PMC" language: "en" --- # Adding Embedded configuration and Ricoh MFD in Cloud Portal Web UI Before you begin, prepare the serial number of the MFD that you wish to add. ## Creating the Embedded configuration 1. In the PMC Web UI, go to **Printers** \> **Embedded templates**. 2. If not done already, create an embedded configuration for Ricoh by clicking **Add**. 3. In **Vendor** , select **Ricoh**. 4. In**Application Type** , select **Standard Gen 2**. 5. Optionally, enable **Configure USB reader** to set up the card reader and perform the following steps (set to disable to leave the card reader configuration untouched for future installations): ![image-2024-6-10_11-8-0.png](https://docs.ricoh-pmc.com/__attachments/a_dccc53dbed1edeb4143f69f5aae2be1aa8e81f54eaecd837f73819bc8386ece5/image-2024-6-10_11-8-0.png?cb=24018e078821093be8e48cc908e3c0e6) 1. Enter its VID and PID in the configuration, in HEX format, with or without the 0x prefix. 1. Please see [Compatible Card Readers](/docs/latest/pmc/compatible-card-readers.md) for the values. 2. [Click **Install and Configure** in the embedded menu](https://docs.ricoh-pmc.com/docs/latest/pmc/embedded-terminals-configuration.md) (if applicable due to network visibility). 3. Or [Click **Manual operations** in the embedded menu](https://docs.ricoh-pmc.com/docs/latest/pmc/embedded-terminals-configuration.md). 1. Make sure the VID and PID values are explicitly specified in the respective command parameters 4. Beware that until the terminal is installed or reinstalled, changes are not propagated. 5. If you reinstall, there is no priority for the installation options - the card reader configuration specified last will be applied. 6. When installing the terminal by other means (directly through Web Image Monitor), the USB reader must be configured manually. 6. Fill in the rest of the configuration according to your needs and click **Save** . For more information on embedded configuration, see [Embedded Terminals' configuration](https://docs.ricoh-pmc.com/docs/latest/pmc/embedded-terminals-configuration.md). ## Adding the MFD 1. Go to **Printers**tab. 2. Click **Add**. 3. In **Vendor** , select **Ricoh**. 4. In **Model family** , select **Ricoh SOP** . ![Ricoh_SOP.png](https://docs.ricoh-pmc.com/__attachments/a_87cb3fdeca077230017d086980a79026279c899ea0a72945a2dd1e2e4db7cb86/Ricoh_SOP.png?cb=fd339fe4e4e91e2741477c0cc5d62795) 5. Fill in all required information. 6. Click **Save**. 7. Proceed to [Cloud Terminal installation](https://docs.ricoh-pmc.com/docs/latest/pmc/cloud-terminal-installation.md). You will have a choice of three installation methods. --- version: "2026.08.20" variant: "PMC" language: "en" --- # Adding IPP print queue manually in Mac OS If you are not using the [PMC Client for MacOSX](https://docs.ricoh-pmc.com/docs/latest/pmc/installing-cloud-client-on-macos.md), you can print directly from the programs on your computer, by adding an IPP print queue manually. Your administrator must provide you with the print queue address and with information on which print driver to use. When you have this information, perform the following steps: 1. Go to **System Preferences** . ![driver-mac-1.png](https://docs.ricoh-pmc.com/__attachments/a_ce0b149cc29dea120f058c516803693d5c78f0237704b6f91aac3ef96998ed3d/driver-mac-1.png?cb=49e482e6e064a16e7362e060f1a3e0bf) 2. Click the Print \& Fax icon. ![driver-mac-1b.png](https://docs.ricoh-pmc.com/__attachments/a_0895f08fee8eb0c9065a1a17833f29e9362436edb1c83d8380577e29cacf0a84/driver-mac-1b.png?cb=cbda9e07fd1acd4f8312497bb2f7a073) 3. Click the **+** to add a new printer. ![driver-mac-2.png](https://docs.ricoh-pmc.com/__attachments/a_1d1792a44b38c7f778b19b428b6ac013cd829b9ac1d42ae796c50a547b246da1/driver-mac-2.png?cb=96f07b00d17bd32ba2eef1ed2191a085) 4. The **Add**dialogue window will be displayed. Enter the following: 1. In **Address**, enter the print queue address that you received from your administrator. 2. In **Protocol** , select**Internet Printing Protocol -- IPP**. 3. In **Queue**, enter the queue name that you received from your administrator 4. In **Name**, enter a user-friendly name. This name will be visible only to you. 5. In **Use** , select the print driver recommended by your administrator. ![driver-mac-3_v1.png](/__attachments/a_5d1a6ecb552683095bd408fa6f1a301808d8234c095483b5a9e6a4e90d65b4ab/driver-mac-3_v1.png?cb=4dcb5afe2dd4ff34ca23fc4dccc7b4eb) Information for administrators: * Address: *pmc* *-gateway:8631* (or 9631 for HTTPS) * Queue: *ipp/input-port-name* 5. If a window opens asking about options, click **Continue**. ![driver-mac-4.png](https://docs.ricoh-pmc.com/__attachments/a_1b74b9d582682ded298883e61c393882ef2f3b8e21ed8ba0bc4ef9bae913b0e0/driver-mac-4.png?cb=58dd8f656101a6304a29d11be6331c3c) 6. Now you can print from the programs you use. In the **Print** dialogue, select your newly created print queue. ![driver-mac-5.png](https://docs.ricoh-pmc.com/__attachments/a_e71c34828c49740f65d4aa21fed3138c2ad264508effed866e5185342fa687db/driver-mac-5.png?cb=edfce2dec479882f7a8f7171ed17fb7d) --- version: "2026.08.20" variant: "PMC" language: "en" --- # Adding IPP print queue manually in Windows If you are not using the [PMC Client for Windows](https://docs.ricoh-pmc.com/docs/latest/pmc/installing-cloud-client-on-windows.md), you can print directly from the programs on your computer, by adding an IPP print queue manually. Your administrator must provide you with the print queue address and with information on which print driver to use. When you have this information, perform the following steps: ## Windows 10 1. Enter **printer** in the Search field in in your task bar. Click **Printers \& Scanners** . ![hcp-windows10-01-printers-scanners.png](https://docs.ricoh-pmc.com/__attachments/a_75f2d92a3d0878ad43a844a0a8e2855657f04db7e76f9acc364fd215a133ddcd/hcp-windows10-01-printers-scanners.png?cb=5f06f7afad3f6698f80965d8607b9ee3) 2. Click **Add a printer or scanner** . ![hcp-windows10-02-add-a-printer.png](https://docs.ricoh-pmc.com/__attachments/a_b1d95790f1064bbe51c2a31aded5c6fa031e36b228b52a85a24477fc4c9d9946/hcp-windows10-02-add-a-printer.png?cb=df83daa422183a808fc8173f9daf1b97) 3. Wait until you see **The printer that I want isn't listed,** and click the link. ![hcp-windows10-03-the-printer-that-i-want.png](https://docs.ricoh-pmc.com/__attachments/a_be0661718892c4ad4354336cb8f20d39a81aee1c16cc9b0ad126503501551ea1/hcp-windows10-03-the-printer-that-i-want.png?cb=dc5a8661b6fdb9ef71931c5a149b5160) 4. Select **Select a shared printer by name** and enter the address of the IPP print queue that you received from your administrator. ![hcp-windows10-04-select-a-shared-printer-by-name.png](https://docs.ricoh-pmc.com/__attachments/a_a2a24a8560425e9998ae8e49f97cc7b1dfb2c9ab685912426f761296ecc5bff0/hcp-windows10-04-select-a-shared-printer-by-name.png?cb=33d30bc04df50e00987666795c2b4907) Information for administrators regarding the print queue URL customization: SSL (requires a valid certificate for the domain): *https://\:9631/ipp/\/accountdomain=\/username=\/providerid=\* Non-SSL: *http://\:8631/ipp/\/accountdomain=\/username=\/providerid=\* For both types: * Replace **\ with the domain name of the server that hosts the IPP service. * Replace **\ with the print queue name or ID as created in the **Print queues** section in PMC Web UI. We recommend using the ID of the printer in the IPP URL, so that any potential queue renaming doesn't break any existing client configurations. You can leave out the port and use the default HTTPS port (443) in environments with standard port 443 support. * Replace **\** with the user name. * Replace **\** with your PMC domain name. * Replace **\** with your authentication provider ID as created in the **Authentication** section in PMC Web UI. This can be useful if your users have the same usernames in different providers. 5. When prompted for the Printer Driver, select the one specified by your administrator, or the PMC Universal Driver depending on your installation. 6. Fill in user name and password in the printer properties if instructed by administrator. ![hcp-windows11-05-usernamepassword.png](https://docs.ricoh-pmc.com/__attachments/a_c51b69cbe3246f573191fcf3d91833a9dd224a1711782e387538a038eaa761f4/hcp-windows11-05-usernamepassword.png?cb=38e9ad88c04dfa7923a9dfd34e3f47ad) This is essential when the **"** IPP authentication is mandatory**"** is enabled in [Security options](https://docs.ricoh-pmc.com/docs/latest/pmc/security-options.md); otherwise, the job will not appear in the print queue. --- version: "2026.08.20" variant: "PMC" language: "en" --- # Admin guide This section contains: * A detailed description of all the settings and functions available in [PMC Web UI](https://docs.ricoh-pmc.com/docs/latest/pmc/cloud-portal-web-ui.md). * Installation, setup, functions, and modes of operation of the [PMC Client](https://docs.ricoh-pmc.com/docs/latest/pmc/cloud-client.md). --- version: "2026.08.20" variant: "PMC" language: "en" --- # API access keys API keys in RICOH PMC server are required to access various server functions using API calls. Please refer to separate API documentation for a full description of the available API endpoints and how to use them. By default, there are several API keys predefined for each customer account which are used by various clients connecting to PMC server, for example, the PMC client or a Chrome browser extension. For security reasons, we recommend you to use a custom API key instead of the predefined ones and disable the predefined keys. A custom API key can be specified during PMC client or PMC gateway installation. ![image-2024-12-9_14-16-37.png](https://docs.ricoh-pmc.com/__attachments/a_66bcd38ad199d1dd21e0dce6ee452342ae5433b20d58ad3b4112fce2e6bc7c61/image-2024-12-9_14-16-37.png?cb=0a616ca765e7618b2bb38d1a80593f0d) Access to the API key section in the PMC Web UI is controlled by **ModifyApiKey** , **ViewApiKey** , and **DeleteApiKey**permissions set in the user roles. API keys are inherited from top-level vendor nodes. If an API key is defined on a vendor account level, it can be used to access API functions across all sub-accounts associated with that vendor. ## Creating an API key 1. In the PMC Web UI, click **Security \> API keys**. 2. Click **Add**. 3. Fill in the required properties. * ![Screenshot_20260316_130508.png](https://docs.ricoh-pmc.com/__attachments/a_e5f10ed2be4d3e2982dface0e99416ec169a1f93818124ed9189e6b843963859/Screenshot_20260316_130508.png?cb=4fb24c59dcb052acc8a47260d1fd711a) * **Type** * **General** -- The default type. You can set all the permissions according to your needs. * **Embedded** -- Used in Embedded configurations. Use the raw value if you wish to install a terminal via **Manual operations** (see [Embedded Terminals' configuration](/docs/latest/pmc/embedded-terminals-configuration.md) and [Terminal Deployment Tool](/docs/latest/pmc/terminal-deployment-tool.md)). * **Chrome** -- Used for Chrome extensions. If you wish to use the one that is created by default, regenerate it to see the value behind the hash. * **Edge** -- Used for Edge devices such as the OMNI bridge. When you add a new edge device, a new value is added to this default Edge API key. * **Name** -- a descriptive name of the API key. * **Value** -- an automatically generated unique value associated with the API key. * **Active**-- a flag indicating whether this API key is active. * **Allow unauthenticated requests** -- if this option is enabled, it is possible to send API requests without acquiring the user token first. * **Allow untrusted endpoints** -- if this option is enabled, it is possible to perform login operations and acquire a user token for insecure login types without completing the device registration workflow. Insecure login types include **Session user** , **Session user + domain** , and **User principal name**. See the API documentation for more information. If both unauthenticated requests and untrusted endpoints are enabled, the API key can be used without any authentication and a leaked API key could result in unauthorized access to the system. When configuring the PMC Client with a custom API key, we recommend you to keep **Allow unauthenticated requests** and **Allow untrusted endpoints** turned off. If both of these options are disabled and an insecure authentication type is used, you must enable the **Enable secure login for session authentication types** option in the PMC Client configuration. * **Automatic endpoint trust** -- if this option is enabled, PMC Clients, secondary gateways, printers, and other endpoints will be automatically authorized when they use this API key for registration. Note that this grants them access to company data; therefore, we recommend enabling this option only for selected keys and only for the necessary duration. * **Automatic endpoint deletion** - if this option is enabled, endpoints registered with this API key will be automatically deleted after the specified period (in hours). It can be used when endpoints are periodically re-imaged, for example Citrix server instances that are re-provisioned each week or client workstations that are re-imaged with a specified interval. * **Expiration date** -- an optional field indicating the date when this API key expires. If not set, the key does not expire. * **Allowed IPs** -- a list of whitelisted IP addresses from which API requests are allowed for this key. If not specified, all IPs are allowed. If the server is accessed through a reverse proxy, the real client IP is only used for this check when the proxy is configured as trusted --- see [Configure environment behind proxy](https://docs.ricoh-pmc.com/docs/latest/pmc/configure-environment-behind-proxy.md). * **Advanced API permissions** -- if this option is enabled, it allows you to additional special permissions required for specific API calls. See the API documentation for additional details. * Additional values associated with the API key are present in the Values tab at the top of the configuration form. Note that for the predefined key **Default key for client and gateway** or for a custom key which is intended to be used by the PMC Client or PMC gateway, you must enable the **Allow unauthenticated requests** and **Allow untrusted endpoints** flags. Otherwise, you won't be able to install or use the PMC Client in the local storage mode, and to install the secondary PMC gateway. ### Creating additional values for an API key 1. After you have created and saved your new API key, click the edit icon to edit it. Go to the **Values** tab and then click **Add new value** . ![image-2024-12-9_14-19-45.png](https://docs.ricoh-pmc.com/__attachments/a_0a28d7d0cf5342ead30ee202d6ce8efd6bd431b6156168b3399b820744389960/image-2024-12-9_14-19-45.png?cb=59e11acbc35a964d69679883b62495d1) 2. A new dialog window will open. ![image-2024-12-9_14-21-35.png](https://docs.ricoh-pmc.com/__attachments/a_b74af55adff00d5b3e29908d359ec933030d43a2f87bd59ad0620bdebdaf779e/image-2024-12-9_14-21-35.png?cb=ed3766990920aa390b2493cf83791805) 3. In the **Description** field, enter a description that you can later use to identify this specific API access key value. 4. Click **Generate** to generate a unique value associated with the API key. All other properties are inherited from the associated API key. 5. Click **Save**. --- version: "2026.08.20" variant: "PMC" language: "en" --- # Application configuration copy through Marketplace If the app is not present under Copy App Settings, check Available Apps and click on the app in the Apps list in the left. ![image-2025-1-31_13-2-9.png](https://docs.ricoh-pmc.com/__attachments/a_7f9d00cc63d626e65c582671ca774ac01394b9be98e3a7eb4b36866e838ee1f4/image-2025-1-31_13-2-9.png?cb=eb9130c20d6b8cddb460cf0db34130ba) To copy an app's settings from one device to other devices, do the following: 1. Install the app on a device and configure it using the App Manager. 2. Install the app on all devices that you want to copy the app's configuration settings to. 3. Click on **Apps \& Licenses** on the MarketPlace menu bar. The Apps \& Licenses drop-down menu appears. 4. From the drop-down menu, select Copy App Settings. ![image-2025-1-31_12-47-49.png](https://docs.ricoh-pmc.com/__attachments/a_95fbc6c2d2103c03f0b9ac71fd6dcc7b0265b9f477a5a1c55cf16c5196b24c8e/image-2025-1-31_12-47-49.png?cb=24e9fbac0f87e5e6df585faf51a1c364) The Copy App Settings page appears displaying the following panels: * Select App - Lists the apps for which the Copy App Settings feature is available. * From: Reference Device - Lists the devices (if any) on which the selected app is currently installed and has been configured. Devices in this panel are organized by device group. * To: Target Device - Lists the devices (if any) on which the selected app is currently installed, organized by device group. 5. In the Apps panel, select the app whose settings you want to copy. The From and To panels populate with the devices on which the selected app is currently installed, restricted to devices for which you are an **administrator**. 6. In the From panel, select the reference device (that is, the device containing the app settings you want to copy). The To panel activates. 7. In the To panel, select the target devices (that is, the devices to which you want to copy the app's settings). The **Copy App Settings** button activates. 8. Click on the **Copy App Settings** button. The copy process begins and the **Operations page** updates with the copy status for each of the selected devices. * If the copy process was successfully initiated for all devices, the following occurs on the Copy App Settings page: * A green banner appears briefly on the screen. * A green check mark appears next to each selected device. * The **Close** button appears. To end the current operation, click on this button. * If the copy process was not successful for one or more devices, the following occurs on the Copy App Settings page: * A red banner appears on the screen. * A red icon appears next to the unsuccessful devices and **Select devices with an error and try again** appears in red. * To retry the copy process, select one or more failed devices and click on the **Copy App Settings** button. Notes: * The Copy App Settings feature overwrites all of an app's configuration settings on the target devices. * The "Last Synced" timestamp indicates the last time the selected app's configuration settings on the selected device were synced with MarketPlace. If you updated an app's settings in the last few minutes and you want to include the changes when using the Copy App Settings feature, be sure to check the Last Synced timestamp to confirm the changes have been synced with MarketPlace. * The "No Configurations" label appears in the To panel for any devices on which the selected app's configuration settings have never been changed from the default settings and then synced with MarketPlace. --- version: "2026.08.20" variant: "PMC" language: "en" --- # Architecture and solution design ## Introduction This document is meant for solution designers who want to understand how the solution works, and in what ways it can be set up. While it is focused on PMC hosted by Ricoh, other options are also mentioned. ## Architecture In this document, you will find three scenarios represented by three example customer sites: 1. A site using direct print only. 2. A site using a local gateway (edge printing) 3. A site using pure cloud printing These are the most common use cases, but there are more options for how data flow can be set up. Note that all of these site options can co-exist in one customer environment. ### Data flow and data processing in PMC **Data input:** * Print jobs from the PMC Client * Mobile App * Print to IPP(S) backend * Using API * Scan data from the MFD * Chrome browser extension **Data processing:** * Printing: additional finishing options can be applied using triggers and automation. * Scanned documents are optionally processed using ABBYY FineReader OCR Engine (only available with PMC hosted by Ricoh). **Data output**: * Print jobs are released after authentication, or without authentication, depending on the setup. They can also be held for printing again later. * Reports on consumption are available in PMC Web UI or via API. * Scan connectors to multiple destinations. #### Visualization ![architecture new.png](https://docs.ricoh-pmc.com/__attachments/a_042353a3dd68f6e389bb961539567eddf2e8427f0c919ffc4fd786b1054fc187/architecture%20new.png?cb=b7c50464e35f2e635a89e7ee9c4eb884) ##### Customer site A - direct print only * No embedded / MFD license is required for this case. You can add the license later, when the customer is ready to expand the feature set available to users. * The main benefit is that the customers no longer need print servers. Setting up this scenario is extremely fast - after the printers and users are added to the Web UI, the PMC Client automatically displays the correct print queues to all users. ##### Customer site B with a gateway (edge printing) * Gateway is HW or SW component. For more information on gateways, see the *Gateways*section of this document. * Print jobs can be routed in the following ways: * PMC Client using local storage and connected to the primary server -- the most common deployment. * PMC Client using cloud storage and connected to the primary server -- when the print jobs cannot be stored locally on the user's PC, for example, because the PC is set up to go to sleep mode shortly, print jobs can be routed to the cloud. * PMC Client using gateway storage and connected to the secondary server (this scenario is not captured in the diagram schematics) -- this setup may be useful if you want your devices to only accept print jobs coming from the Gateway. For example, for compliance reasons. ##### Customer site C - pure cloud * No local HW is required for the full feature set of PMC. * Print jobs are routed through Cloud servers or using the PMC Client with local storage. #### Features available in each scenario | Feature | Description | Customer site A (direct print only, no embedded / MFD license) | Customer site B (with gateway) | Customer site C (pure cloud) | | Supported devices | Supported printer vendors for the individual scenarios: [Supported printers](https://docs.ricoh-pmc.com/docs/latest/pmc/requirements.md#SupportedPrinters) | All listed devices with PDF/Postscript (and some PCL) printing (Brother, Canon, Epson, FujiFilm, HP, Konica Minolta, Kyocera, Lexmark, Ricoh, Sharp, Xerox) | All listed devices with PDF/Postscript (and some PCL) printing (Brother, Canon, FujiFilm, HP, Konica Minolta, Kyocera, Lexmark, Ricoh, Sharp, Xerox) | Gen 2 Cloud Terminals | | No more print servers! * queue management * driver management | Admin: Configures the locations in the PMC Web UI. Users' print queues are created automatically. Everyone is using the same universal print driver. Users: their print queues are synchronized automatically by the PMC Client See [Cloud Client](https://docs.ricoh-pmc.com/docs/latest/pmc/cloud-client.md). | ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Direct print | Submitted print jobs are printed at MFDs without authentication. Note: embedded /MFD license is not needed for this scenario. | ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Pull print with embedded terminal (Also known as Print Roaming) | In this scenario, users send a print job to PMC and authenticate at any connected MFD to release it. The MFD has an embedded terminal (client) deployed. | ![cross mark](https://docs.ricoh-pmc.com/__attachments/a_09d880b62cdb7cd2d9c7abeca56eaec88cf57a6c6d1cd9f7ce37093dd78cdca5/atlassian-cross_mark?cb=a9c671cfc7809253be52d640dbbf1019) Not applicable in this scenario. | ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Pull Print with QR code + mobile app (Also known as Print Roaming) | This scenario does not require a deployed embedded terminal (no need for a license). Authentication is done using a QR code and the mobile app. See [Creating QR-codes](https://docs.ricoh-pmc.com/docs/latest/pmc/creating-qr-codes.md) and [Using the mobile app](https://docs.ricoh-pmc.com/docs/latest/pmc/using-the-mobile-app.md). | ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Available with local storage mode. | | Scan Workflows (including OCR) | Scan the file to pre-defined destinations. See [Scan workflows](https://docs.ricoh-pmc.com/docs/latest/pmc/scan-workflows.md). | ![cross mark](https://docs.ricoh-pmc.com/__attachments/a_09d880b62cdb7cd2d9c7abeca56eaec88cf57a6c6d1cd9f7ce37093dd78cdca5/atlassian-cross_mark?cb=a9c671cfc7809253be52d640dbbf1019) | ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Available for Gen 2 Cloud Terminals | ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Scan to email | Some devices offer additional scanning options | ![cross mark](https://docs.ricoh-pmc.com/__attachments/a_09d880b62cdb7cd2d9c7abeca56eaec88cf57a6c6d1cd9f7ce37093dd78cdca5/atlassian-cross_mark?cb=a9c671cfc7809253be52d640dbbf1019) | ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) * Available per device/model. See [Scan To Mail](https://docs.ricoh-pmc.com/docs/latest/pmc/scan-to-mail.md). * You can also use the native scan to email when available. | ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) * Available per device/model. See [Scan To Mail](https://docs.ricoh-pmc.com/docs/latest/pmc/scan-to-mail.md). * You can also use the native scan to email when available. | | User identity - cloud providers | See [Authentication providers](https://docs.ricoh-pmc.com/docs/latest/pmc/authentication-providers.md). | ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | User identity - local Active Directory (LDAP) | Connect to local Active Directory, Novell eDirectory, and IBM Domino. This requires a gateway to be deployed in the customer's environment. See [LDAP authentication](https://docs.ricoh-pmc.com/docs/latest/pmc/ldap-authentication.md). | ![cross mark](https://docs.ricoh-pmc.com/__attachments/a_09d880b62cdb7cd2d9c7abeca56eaec88cf57a6c6d1cd9f7ce37093dd78cdca5/atlassian-cross_mark?cb=a9c671cfc7809253be52d640dbbf1019) | ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Gateway with visibility to the LDAP is required. | | Chrome extension printing | SAFEQ Cloud Chrome extension can be installed on Chromebook or in the Chrome browser to allow direct and pull printing. See [SAFEQ Cloud Chrome extension](https://docs.ricoh-pmc.com/docs/latest/pmc/safeq-cloud-chrome-extension.md). | ![cross mark](https://docs.ricoh-pmc.com/__attachments/a_09d880b62cdb7cd2d9c7abeca56eaec88cf57a6c6d1cd9f7ce37093dd78cdca5/atlassian-cross_mark?cb=a9c671cfc7809253be52d640dbbf1019) | ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Direct print not available | | Wide Area mobile print (mDNS, AirPrint) | Users with compatible phones will see the available print queues. See [Wide area mobile print](https://docs.ricoh-pmc.com/docs/latest/pmc/wide-area-mobile-print.md). | ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![cross mark](https://docs.ricoh-pmc.com/__attachments/a_09d880b62cdb7cd2d9c7abeca56eaec88cf57a6c6d1cd9f7ce37093dd78cdca5/atlassian-cross_mark?cb=a9c671cfc7809253be52d640dbbf1019) | | Mobile App | Use your phone to submit print jobs to the solution and release them. See [Mobile print](https://docs.ricoh-pmc.com/docs/latest/pmc/mobile-print.md) and [Using the mobile app](https://docs.ricoh-pmc.com/docs/latest/pmc/using-the-mobile-app.md). | ![cross mark](https://docs.ricoh-pmc.com/__attachments/a_09d880b62cdb7cd2d9c7abeca56eaec88cf57a6c6d1cd9f7ce37093dd78cdca5/atlassian-cross_mark?cb=a9c671cfc7809253be52d640dbbf1019) | ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Reporting | ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) PMC does not act as a print accounting solution and only considers the attributes of a print job at the time of submission, whether it was overall sent as color vs. mono, and the total number of pages sent to PMC. Changes in attributes at print time, print errors, or mixed color/mono jobs are not accounted for. See [Reports](https://docs.ricoh-pmc.com/docs/latest/pmc/reports.md). | ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Using API | See [API documentation](https://docs.ricoh-pmc.com/api/). | ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Basic finishing options | Tray selection, stapling, color/bw, hole punching, simplex/duplex | ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Finishing options that perform layout altering changes after the job is submitted * Using triggers * Using API calls * At the embedded terminal screen | Change of paper size, orientation and scaling, booklet | ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Only when PMC Client with local storage is used. | |--------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| ### Print roaming **Scenario 1** ![PrintRoaming scenario 1.png](https://docs.ricoh-pmc.com/__attachments/a_264f4d5ca7fe783436b008c638b004380b2f8a300c25384a120a540be6a33c2c/PrintRoaming%20scenario%201.png?cb=3b5ab82a72e168d3a48e0c2a3b3e73a2) **Scenario 2** ![PrintRoaming scenario 2.png](https://docs.ricoh-pmc.com/__attachments/a_d68c7557e68b00aee2fce694911004089b6df02a403e8c5605afc092c4f46ae4/PrintRoaming%20scenario%202.png?cb=a85a4870bb8facea47494f07044620eb) **Scenario 3** ![PrintRoaming scenario 3 new2.png](https://docs.ricoh-pmc.com/__attachments/a_336d6fabd8b8ff3069f6ef6fab3d679ed9ba10a8ef1cd0be1f3717b15ef2f9a2/PrintRoaming%20scenario%203%20new2.png?cb=4a38bc51e0385e57ef573a7d9b7930bb) ### Data input - getting the data in ![DataInput new.png](https://docs.ricoh-pmc.com/__attachments/a_2bd1c59b9e105bfdc4a680ff5a2049a28d054f508b1036983b37110d01c55853/DataInput%20new.png?cb=5d3f498be143fca8c860e8ab9008c551) #### PMC Client PMC Client is the most common way for users to submit their print jobs. It contains the Universal print driver. Customers opting for a custom print driver can set up an IPP(s) print queue and select their preferred driver in the configuration process. See [Adding IPP print queue manually in Windows](https://docs.ricoh-pmc.com/docs/latest/pmc/adding-ipp-print-queue-manually-in-windows.md) and [Adding IPP print queue manually in Mac OS](https://docs.ricoh-pmc.com/docs/latest/pmc/adding-ipp-print-queue-manually-in-mac-os.md). **Print queue deployment** Print queues are automatically created on users' workstations based on the location configured by the administrator. This requires the Universal print driver. **Universal print driver** Universal Print Driver is used for automated print queue creation. See [Supported printers](https://docs.ricoh-pmc.com/docs/latest/pmc/requirements.md#SupportedPrinters). **Delivering the print job** There are two modes of operation: 1. **Local storage mode** -- the PMC client connects to the primary server via a persistent channel and performs all print and job storage operations locally. Local storage mode requires PMC client registration and authorization in the PMC server. When a user prints, the jobs are stored on the PC. In case of Citrix or other VDI, it depends on where the PMC Client is running, specifically the underlying PMC Client service "PMC Client Core" runs. Jobs are stored on the Citrix server (where client core service runs), and they will remain there when the thin session is terminated, assuming they have session retention etc configured in their VDI environment. 2. **Gateway mode** -- the PMC client sends all print jobs to the primary PMC server, and has no persistent connection to the server. When the user prints, the jobs are delivered from the PC to the PMC server, either primary or secondary gateway, depending on the configuration. Jobs are delivered to MFD using the *Document Output* service. Jobs are delivered from the PMC Client to the MFD directly if the PMC Client can reach the printer. If the PMC Client cannot reach the MFD, the job will automatically be routed via the primary PMC server to the appropriate *Document Output* service, which will then deliver it to the MFD. **Supported platforms** | OS | Supported | |---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Windows | ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Mac | ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Linux | ![cross mark](https://docs.ricoh-pmc.com/__attachments/a_09d880b62cdb7cd2d9c7abeca56eaec88cf57a6c6d1cd9f7ce37093dd78cdca5/atlassian-cross_mark?cb=a9c671cfc7809253be52d640dbbf1019) Planned, beta available upon request | For more information, see [Cloud client overview](https://docs.ricoh-pmc.com/docs/latest/pmc/cloud-client-overview.md). #### Mobile App The mobile app is available for Android and iOS. It allows users to submit print jobs and release them. For more see [Using the mobile app](https://docs.ricoh-pmc.com/docs/latest/pmc/using-the-mobile-app.md). and [Creating QR-codes](https://docs.ricoh-pmc.com/docs/latest/pmc/creating-qr-codes.md). #### IPP Printing You can print to the cloud servers directly using IPPS. See [Adding IPP print queue manually in Windows](https://docs.ricoh-pmc.com/docs/latest/pmc/adding-ipp-print-queue-manually-in-windows.md) and [Adding IPP print queue manually in Mac OS](https://docs.ricoh-pmc.com/docs/latest/pmc/adding-ipp-print-queue-manually-in-mac-os.md). #### Chrome browser extension SAFEQ Cloud Chrome extension can be installed on Chromebook or in the Chrome browser to allow direct and pull printing. * Chromebook user authenticates via Chromebook user email address. * Print queues are synchronized. #### Scanning Use scan workflows to scan data to the solution. See [Scan workflows](https://docs.ricoh-pmc.com/docs/latest/pmc/scan-workflows.md). #### Using API See [API documentation](https://docs.ricoh-pmc.com/api/). ### Data output -- printing #### Direct printing The print job is released immediately -- users are not required to authenticate at the MFD. At the time of print job submission, users must select which printer they wish to use by selecting the respective Direct queue. Direct queue can route print jobs using local storage (PMC Client) or Gateway. User's workstation must have network visibility to the MFD. ![PushPrint new.png](https://docs.ricoh-pmc.com/__attachments/a_2cf73ef83a6a1c85538394349d27305b91e013f17565a7b6aef6b7044a2b2c50/PushPrint%20new.png?cb=d6ff697c652864c47120a1ca7cde8cf0) #### Pull printing Pull print requires users to authenticate at the MFD, ensuring they are authorized to release the print job. The users send the print jobs to the Pull queue and choose where to release them by going to any compatible and connected MFD. Users can release the print job via the following methods: * Authenticating at an MFD with an embedded terminal. The available authentication methods are: card, PIN/Short ID, one-time password, username+password. * Selecting the printer using the Mobile app. ![PullPrint new.png](https://docs.ricoh-pmc.com/__attachments/a_7a41609fa30e2af1cfa147d085a49359675b5817aee40190e5cc807a56816403/PullPrint%20new.png?cb=fef6dedf1263f234aefcd08315caca7c) For the fallback route to work, when the primary server is in the cloud and a document is printed from a secondary server in the local network, storage services must be enabled on both primary and secondary servers. ### Data output - Scanning #### Scan Workflows ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Scan Workflows are only available with Gen 2 Cloud terminals. ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Scan Workflows are only available when hosting is provided by Ricoh. ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) The scanned data is always processed by Ricoh servers, even when a local gateway is used. The solution uses ABBYY FineReader OCR Engine. See [Scan workflows](https://docs.ricoh-pmc.com/docs/latest/pmc/scan-workflows.md). For the available scan connectors, see [Connectors](https://docs.ricoh-pmc.com/docs/latest/pmc/connectors.md). ![scanning3 new.png](https://docs.ricoh-pmc.com/__attachments/a_bb30a8d3f478a631cf16a0644830dd2d908282bdd5e8d38b2543afe088b8d392/scanning3%20new.png?cb=d0c63d71ec3f830d31923044531ef91a) #### Scan to email Available for selected embedded terminals or via native integration. See [Scan To Mail](https://docs.ricoh-pmc.com/docs/latest/pmc/scan-to-mail.md). ### Data output -- MFDs, printers | **Device integration** | Required license | Capabilities and integration method | |-------------------------------------------------------------------------------------------|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | MFD | * Core / Print | Direct printing * ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Can receive print jobs from PMC Client * ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Can receive print jobs from Gateway * ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Mobile App with direct queue Pull printing * ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Mobile app with QR code Scan Workflows * ![cross mark](https://docs.ricoh-pmc.com/__attachments/a_09d880b62cdb7cd2d9c7abeca56eaec88cf57a6c6d1cd9f7ce37093dd78cdca5/atlassian-cross_mark?cb=a9c671cfc7809253be52d640dbbf1019) Not available | | MFD with pure cloud terminal * Without a local gateway (most common) * With local gateway | * (Core + Embedded) / MFD | Direct printing * ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Can receive print jobs from PMC Client * ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Can receive print jobs from Gateway * ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Mobile app with direct queue Pull print * ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Mobile app with QR code * ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Full terminal client for print job release and management Scan Workflows * ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Available | | MFD with an embedded terminal with a local gateway | * (Core + Embedded) / MFD | Direct printing * ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Can receive print jobs from PMC Client * ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Can receive print jobs from Gateway * ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Mobile app with direct queue Pull printing * ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Mobile app with QR code * ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Full embedded terminal client for print job release and management Scan Workflows * ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Only available at selected terminals | ### Gateways Other terms for gateway are: * Secondary gateway * Secondary gateway server * Secondary server * Edge device #### Architecture There are two types of server in PMC: * **Primary server** -- the primary server runs PMC Web UI for configuration and management, handles core communication and connection to backend databases and similar master roles. * **Secondary gateway server** -- the secondary servers are additional server gateways that can run services. Note that a "server" can take any form. It can be either a hardware or software appliance, or it can be implemented on existing server infrastructure, virtual or physical. It can run anywhere -- in the public cloud, private cloud, completely disconnected on-premise, or on-premise connected to a primary in the cloud for central management. Regardless of whether it's primary or secondary, it can run a single service or all services, depending on the features needed for that particular node. There can be any number of primary and secondary gateway servers, from one individual server to tens of thousands of servers in a very large distributed configuration, without a single point of failure. Gateways allow document storage and processing to remain local, ensuring document integrity and privacy are maintained. Only the print job's selected metadata are transferred to the cloud for management and reporting purposes via an encrypted channel. Document content remains secure because it never leaves your premises and thus never reaches cloud components. Data that are not present in the cloud cannot be externally compromised. #### When to use Gateway Gateways are optional. You only need them in the following scenarios: * Some printers/MFDs do not support pure cloud terminals yet. A local gateway allows you to install embedded terminals at your MFDs. * When you use local LDAP service (such as Active Directory, Novell eDirectory, IBM Domino), a gateway allows the primary server to access this local user database for authentication purposes. * You need to keep your print jobs local for security or regulatory purposes. * You wish to use mDNS printer discovery (Airprint). * Your Internet connection parameters cannot support the use of cloud terminals with cloud printing because of low bandwidth, high latency, etc. Gateway is NOT required for: * Direct print-only deployments (see Customer site A scenario above). * Direct or pull print with cloud terminal clients (see Customer site C scenario above). #### OMNI Bridge YSoft OMNI Bridge™ is a serverless Edge device, fully managed by Y Soft. It has been built to significantly simplify the deployment of the gateway. ![omni bridge.jpg](https://docs.ricoh-pmc.com/__attachments/a_cb4e8f8fc7d1946bed3b4bfddbb4b5521474ecec535723dc9b39e50a73f25129/omni%20bridge.jpg?cb=b77e0609d0d8860cf952af4dbca5ce2d) See [Setting up OMNI Bridge](https://docs.ricoh-pmc.com/docs/latest/pmc/setting-up-omni-bridge.md). #### Virtual Gateway The virtual software appliance is a pre-configured VM image, ready to run on a hypervisor such as VMWare ESX, Xen, Hyper-V or similar Infrastructure-as-a-Service solutions. Using virtual appliances allows for extremely rapid provisioning and cleanly decouples the operator from the consumer by encapsulating all knowledge of the application within the virtual appliance. Gateway can be installed as a software appliance such as a Virtual Machine (VM) running at any Infrastructure as a Service (IaaS) provider, e.g. Amazon EC2 or Microsoft Entra ID. See [Gateway on Software Appliance](https://docs.ricoh-pmc.com/docs/latest/pmc/gateway-on-software-appliance.md). #### Other HW Gateways See [Gateway on Hardware Appliance](https://docs.ricoh-pmc.com/docs/latest/pmc/gateway-on-hardware-appliance.md). #### Sizing **YSoft OMNI Bridge™** Based on internal testing, we recommend one OMNI Bridge for every 15 printers. However, the customer's print volume, print job mixture, and volume during peak periods may affect the job processing and authentication timeframes. We will refine the recommendation as we gather more information from customer environments. **Other** There are no universal rules for server scaling, as it all depends on the printing volume, and number of users. The following are general recommendations for most scenarios. | | 1-25 printers | 26-100 printers | 101-500 printers | 501-1000 printers | | CPU | 2 cores/CPU's | 4 cores/CPU's | 4 cores/CPU's | 8 cores/CPU's | | Memory | 4 GB | 16 GB | 16 GB | 16 GB | | Hard disk | SSD 64 GB | SSD 128 GB | SSD 256 GB | SSD 512 GB | |-----------|---------------|-----------------|------------------|-------------------| ## Hosting The platform can be installed in a Ricoh data center. As a partner, this gives you the ability to provide a hosted print solution without investing in a data center. You have full control of your customers and businesses through the PMC Web UI. **Regions** Y Soft's data center infrastructure is available in the USA, Canada, The European Union, the UK, Singapore, and Australia regions. ### Other options Refer to [this section](https://docs.ricoh-pmc.com/docs/latest/pmc/background.md#hosting) or contact Ricoh for more hosting options. ## User identity The following options are available: * LDAP authentication * Requires Gateway to enable the network communication * Microsoft Entra Authentication * Google Workspace Authentication * OKTA Authentication * Auth0 Authentication * PingID Authentication * External card provider API authentication See [Authentication providers](https://docs.ricoh-pmc.com/docs/latest/pmc/authentication-providers.md). ### Single Sign-on The following Single Sign-on options are available * Microsoft Entra Single Sign-On * Okta Single Sign-On * PingId Single Sign-On See [Single Sign-On](https://docs.ricoh-pmc.com/docs/latest/pmc/single-sign-on.md). ## Availability, security ### Security See [Security and privacy](https://docs.ricoh-pmc.com/docs/latest/pmc/security-and-privacy.md). ## Limitations * Scan Workflows * Only available with the new terminals. More terminals will be supported as they are replaced with the new ones. * Only available with PMC hosted by Ricoh. * When scan to email is used, the print job is delivered via 3rd party service from a pre-configured email address. Customers cannot change this email source nor use their own email service. * Modifying finishing options after the print job was sent is not available when the print job is downloaded to the pure cloud terminal. When cloud terminals are configured for cloud, it only works when local client storage is used. * Reporting accuracy - the solution only considers the attributes of a print job at the time of submission, whether it was overall sent as color vs mono, and the total number of pages sent to PMC. Changes in attributes at print time, print errors, or mixed color/mono jobs are not accounted for. ### General Limitations of the embedded terminals | Vendor | Notes / Limitations | Reference responsiveness (OMNI/EDGE: embedded in the local 1Gbps network. Cloud: public 100Mbps up/down stream network) | |----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| | Brother | * Always requires a gateway in the local network * GUI version 1 only * Doesn't support scan to my email or advanced scan workflows | * OMNI/EDGE: login to job list: \~3-4sec * OMNI/EDGE: pull print to first page: \~3sec | | Canon | * Always requires gateway in the local network * GUI version 1 only * Doesn't support scan to my email or advanced scan workflows | OMNI/EDGE: login to job list: \~4-5sec | | Epson | Direct print only | n/a | | FujiFilm | Requires a Windows PC with visibility to the printer for initial deployment | * Cloud: login to job list: \~4-5sec * Cloud: pull print to first page: \~10sec * OMNI/EDGE: login to job list: \~8sec | | HP | * OxPD variant: * Requires a gateway in the local network (not needed for WorkPath) * Has version 1 GUI only * * Doesn't support advanced scan workflows * WorkPath variant requires access credentials and deployment via the HP Command Center | * OxPD: OMNI/EDGE: login to job list: \~5-12sec * WorkPath: Cloud: login to job list: \~4-5sec | | Konica Minolta | * OpenAPI variant: * Requires a gateway in the local network * Has version 1 GUI only * * Doesn't support advanced scan workflows * IWS variant: * requires access credentials and deployment via KM Marketplace (or KM IWS deployment tool for Europe \& APAC) | * OpenAPI: OMNI/EDGE: login to job list: \~4-8sec * IWS: Cloud: login to job list: \~4-5sec * IWS: OMNI/EDGE: login to job list: \~5sec | | Kyocera | * Always requires a gateway in the local network * GUI version 1 only * Doesn't support advanced scan workflows | OMNI/EDGE: login to job list: \~4-5sec | | Lexmark | * Always requires a gateway in the local network * GUI version 1 only * Doesn't support advanced scan workflows | OMNI/EDGE: login to job list: \~4-5sec | | Ricoh | * GUI version 2 variant requires a local PC with visibility to the printer for initial deployment * GUI version 1 and Java variant always requires a gateway in the local network * GUI version 1 and Java variant doesn't support advanced scanworkflows | * version 1: OMNI/EDGE: login to job list: \~3-5sec * version 2: OMNI/EDGE: login to job list: \~3-5sec * version 2: Cloud: login to job list: \~4-5sec | | Sharp | * Always requires a gateway on the local network * GUI version 1 only * Doesn't support advanced scan workflows | OMNI/EDGE: login to job list: \~5-6sec | | Toshiba | Direct print only | n/a | | Xerox | * Always requires a gateway in the local network * GUI version 1 only * Doesn't support advanced scan workflows | OMNI/EDGE: login to job list: \~4-5sec | For more information, see [Known issues and limitations](https://docs.ricoh-pmc.com/docs/latest/pmc/known-issues-and-limitations.md). --- version: "2026.08.20" variant: "PMC" language: "en" --- # Asian fonts support for direct print This article explains how to fix documents that are unreadable after printing due to missing fonts (particularly Asian fonts). This may happen if a PDF is uploaded to PMC via public API. This solution is not applicable to the situation where a user submits the PDF document via the PMC Client and the document is flattened and converted to PDF/A. ## Background information Once a print job is submitted via public API, the Primary or Secondary servers convert it. The goal is to convert any print job to PDF format. If the submitted job is a PDF already, the conversion process will leave it as is and the file will be spooled in the original format. When the job is released using direct print, another service converts it to the Postscript format. Sometimes, the printed document lacks certain fonts. Typically if the original contains Asian languages. You can solve this issue by adding the fonts into the operating system for your Primary or Secondary server and providing a configuration file for the Xpdf converter. ## Solution for CentOS (RHEL) Due to many languages ​​and distributions, we only provide support for the most used platform - CentOS (RHEL). Packages and configuration can also be customized based on the customer's needs. 1. Check whether the CMap package is installed by running the following command: rpm -q poppler-data 2. If it isn't, install it. sudo yum install poppler-data 3. Install the required fonts, for example, Google Noto fonts. Note that the Xpdf converter does not support ttc (true type collections) such as google-noto-cjk. Use only otf or ttf format. Example: sudo yum install google-noto-sans-japanese-fonts sudo yum install google-noto-sans-korean-fonts sudo yum install google-noto-sans-traditional-chinese-fonts sudo yum install google-noto-sans-simplified-chinese-fonts 4. Prepare the xpdfrc configuration file for Xpdf converter. This file must have the following structure: #----- begin Japanese support package cidToUnicode Adobe-Japan1 /usr/share/poppler/cidToUnicode/Adobe-Japan1 unicodeMap ISO-2022-JP /usr/share/poppler/unicodeMap/ISO-2022-JP unicodeMap EUC-JP /usr/share/poppler/unicodeMap/EUC-JP unicodeMap Shift-JIS /usr/share/poppler/unicodeMap/Shift-JIS cMapDir Adobe-Japan1 /usr/share/poppler/cMap/Adobe-Japan1 toUnicodeDir /usr/share/poppler/cMap/Adobe-Japan1 fontFileCC Adobe-Japan1 /usr/share/fonts/google-noto/NotoSansJP-Regular.otf #----- end Japanese support package * You can download the file [here](https://docs.ricoh-pmc.com/__attachments/a_c0e2e527486810717d91650bb14eedf64ba26b10065cc1f9501d7e66841d81a5/xpdfrc.md?cb=bbd8a23e4e2a583e8451f160be147cad). * In this case, we use mapping to the poppler-data resources. As conversion fonts, we use installed NotoSans regular otf versions. 5. Place the xpdfrc file in the /etc/ folder. 6. Set the permissions for the file to 644 at minimum. sudo chmod 644 xpdfrc For Xpdf configuration in general, see . For Xpdf language support, see . --- version: "2026.08.20" variant: "PMC" language: "en" --- # Asian fonts support for MS Office documents converted to PDF This article explains how to fix documents that are unreadable after printing due to missing fonts (particularly Asian fonts). This may happen if an MS Office document is uploaded to PMC via public API. The solution is not applicable to the situation when a user submits the MS Office document via the PMC Client and the document is converted to PDF/A before the print job is uploaded to PMC. ## Background information Once a print job is submitted via public API, the Primary or Secondary servers convert it. The goal is to convert any MS Office document to PDF format. Sometimes, the printed document lacks certain fonts. Typically if the original contains Asian languages. You can solve this issue by adding the fonts into the operating system for your Primary or Secondary server. ## Solution for CentOS (RHEL) Due to many languages ​​and distributions, we only provide support for the most used platform - CentOS (RHEL). The list of installed fonts can be customized based on the customer's needs. 1. Install the required fonts in your Primary or Secondary server. We can recommend Google Noto fonts. If you wish to increase the success rate, install the MS core fonts as well. The converter works with common true type font formats such as ttf, otf and collection ttc. For basic Asian support, you can install the CJK (Chinese, Japanese, Korean) set: sudo yum install google-noto-cjk-fonts 2. Check whether the fontconfig library is already installed in your server by using the following command: rpm -q fontconfig 3. If it isn't, install it. sudo yum install fontconfig 4. Rebuild the font cache to include the newly installed fonts. sudo fc-cache -r -v --- version: "2026.08.20" variant: "PMC" language: "en" --- # Audit log file ## **⚠️ Important Cloud-managed configuration** The `application.conf` file is managed exclusively by the **operations/R\&D team** . Administrators cannot modify this file directly. To request a change to the audit log configuration (e.g., enabling the log file writer or changing retention settings), please contact **support**. ## Audit log documentation The Audit Log gives administrators the ability to see all actions made by a user during a selected period and all configurations and settings made on the system during a selected time period. It can be used for audit and compliance purposes. All configuration changes in PMC are logged. All higher-level operations are logged to audit log. So it should be possible to see *what* has been done *where* , *when* and by *whom*. ### Audit event log configuration The configuration of the event log happens in **application.conf** config file. event-log { file { is-enabled = false basename = "audit" directory = ${app.home}"/logs" retention-days = 30 } } The sub-node(s) under `event-log` are the output writers. Currently there is only a file writer. So the settings under `file` only apply to the file writer, or generally to the node under which they are present. Most settings are self-explanatory. * `is-enabled` switches the audit log file writing on/off. Changing this setting requires re-start of PMC. * `basename` is the base name of the audit log file. A date is automatically appended to the `basename`. * `directory` is the directory where the log files are created in. `${app.home}` is a variable that points to the root folder of PMC. * `retention-days` is unused ### Audit log writing #### File writer The audit log file is only written on primary servers. The log file name is simply: 'audit-YYYY-MMM-DD.log'. Every day a new log file is created with events that occured on that day. The 'audit' part is the `basename` of the configuration above. ### Events from secondary/gateway servers Under normal circumstances (secondary is online/connected to primary) *entity events* are not logged at all on secondary servers. Because entities are not modified on secondary servers. Action events and config update events are being raised on secondary servers, i.e. if a user authentication happens on an Authentication Service. So those kinds of events are being forwarded to primary servers and logged there. #### Log synchronization from offline secondary servers In case a secondary server looses connection to the primary and the offline-cache is enabled it will record any entity, action and config events locally and synchronize them to the primary when the connection is established again. The original `event-context` and `event-detail` of the event is maintained with original timestamps of when those operations did occur on the secondary server while offline. For this to work a temporary audit log file is written on the secondary where the audit entries are written to in an encoded format. ### The log structure An audit log entry current has the following structure. It is embedded into starting `{` and ending `}` as the first character of a line. For example: { event-context:{type:EventContext,source:test,traceId:"fabb825a-6fb6-4d25-96c2-f6482972319d",serverId:"f4911326-eb36-41e7-8fc5-bee01ca07ae5",datetime:"2020-05-11T15:37:24.627+02:00",request:{type:UnauthenticatedRequest,requesting-user:{type:RequestingUser,user-id:user-not-defined},requesting-domain:}}, event-detail:{type:DeleteEntityEvent,entity-type:Account,entity-to-delete:{type:Account,account-type:Container,id:1,name:Foo,domains:[]},result:{type:Account,account-type:Container,id:1,name:Foo,domains:[]}},datetime:"2020-05-11T15:37:24.630+02:00"} } There are two major parts of a log entry. The first one is `event-context`. The `event-context` transports the *when* , *where* and *who* . The same `event-context` may be part of multiple log entries. This happens when an operation triggered at a system boundary (i.e. API) or in the UI and consists of multiple configuration changes. Each configuration change is separately logged with the same `event-context` as they all group one operation. This is easily visible as the `traceId` value is static to multiple audit log entries. The `event-context` has the following parameters: * source: the source of where the event occurred. This can be i.e.: "web", or "api". * traceId: The trace ID combines multiple events into a single action. For example, an API request to upload a document may result in multiple audit log events that change some data but are all part of this higher-level operation. The value is generated as a UUID by default. If the OpenTelemetry (OTEL) feature is enabled, the value is generated by OpenTelemetry---32 hexadecimal characters without any dash or so. * serverId: the server ID where this event originated. * datetime: the date and time when the event first hit an PMC boundary system or was initiated otherwise. * request: distinguishes between an *authenticated request* and an *unauthenticated request* . An *authenticated request* contains an account-id and user details. This is used when a user could be identified as part of an API request or an UI operation. An *unauthenticated request* is used when a user could not be identified, for example because the API uses an ApiKey. In this case the *unauthenticated request* contains at least the domain that is the target of the request and any ApiKey, or email address that was additionally available. The second part is the `event-detail`. The `event-detail` is the *what*. There are the following different types of *what*: #### Domain model/entity based configuration changes The following operations on domain model/entities are recorded: * adding data, `AddEntityEvent` * updating data, `UpdateEntityEvent` * deleting data, `DeleteEntityEvent` * deleting all of something, `DeleteAllEntityEvent` * some custom operation on entities that cannot be easily catigorized on the above, `CustomEntityEvent` All of the above events record changes to entities. * `entity-type` logs the name/type of entity. * `result` log the operation result. Additionally each operation has special fields. I.e. `UpdateEntityEvent` logs a previous/old value and the new value as `result`. The `result` field can also contain an error like so: `result:{type:Error,error-code:9999,error-msg:Foo,cause:none}` The following entities may get recorded: Account, ApiKey, AuthProvider, AuthRole, Document, EncryptionKey, Group, InputPort, KeystoreData, LicenseAllocation, Location, MessagingConfig, MobilePrintConfig, MobilePrintWideArea, ObjectNode, OutputPort, Server, Service, Storage, TagGroup, TemplateConfig, TerminalConfig, Trigger, User, UserDetail #### Other configuration changes Log type: `ConfigUpdateEvent` Config updates are raised and written to log when configuration is changed that is stored in `application.conf` file. Here is an example of how this looks for a change to the log-level: { event-context:{type:EventContext,source:web,traceId:"19d09e6c-8d10-4390-9256-1dbb7d9002ba",serverId:"1e786aa7-d46a-473b-98e8-5c8cccb39fb5",datetime:"2020-05-26T15:06:31.055+02:00",request:{type:AuthenticatedRequest,executing-user:...,account-id:1}}, event-detail:{type:ConfigUpdateEvent,configType:app.logging,configData:{"loglevel":"DEBUG"}},datetime:"2020-05-26T15:06:31.066+02:00"} } #### Action based operations Log type: `IntentActionEvent` The `IntentActionEvent` events mark high-level operations. Those include things like user authentication, document upload, push or pull-print, etc. Those operations usually involve changes to multiple entities. To get those together the `IntentActionEvent`s mark a start and end block where multiple *entity events* may occur. The opening block event is usually marked with an `intent` similar like this: `event-detail:{type:IntentActionEvent,intent:{type:AddDocumentIntent...` Where the closing block is marked with an `intent-result` similar like this: `event-detail:{type:IntentActionEvent,intent-result:{type:AddDocumentIntentResult...` All events within this block have the same `event-context` and hence the same `traceId`. So the `traceId` can be used to filter for higher-level operations that contains multiple entity operations. Common to all is the `datetime` when events happened. The following `intent` types may get logged: AuthUserIntent, FindUsersIntent, FindGroupsIntent, TestAuthProviderIntent, PrintInputIntent, MobilePrintInputIntent, PrintOutputIntent, PrintAllIntent, CreateOutputPortIntent, UpdateOutputPortIntent, DeleteOutputPortIntent, DefaultConvertDocumentIntent, InternalConvertDocumentIntent, ScheduledConvertDocumentIntent, MoveStorageIntent, AddDocumentIntent, UpdateDocumentIntent, RetrieveDocumentIntent, UploadDocumentIntent, DownloadDocumentIntent, DeleteDocumentIntent, DeleteTemporaryDocumentIntent, GetDocumentUriIntent, AddDocumentFromServerIntent, UpdateDocumentFromServerIntent, ConfigureTerminalIntent, DeployTerminalIntent, UndeployTerminalIntent, LicenseCheckIntent, EmailMessageSendIntent, TestEmailMessageSendIntent --- version: "2026.08.20" variant: "PMC" language: "en" --- # Audit logs In the PMC Web UI navigation menu, expand **Reports** and click **Audit logs** sub menu item. The Audit logs feature flag is available only in the Y Soft-hosted cloud environment and a role with permission to view logs and view reports. If account privacy features are turned on the audit logs web access is not available. ![image-20260115-070256.png](https://docs.ricoh-pmc.com/__attachments/a_3e7922ea57647e7835ec9896126ab8a0a81736aec66b5fa4654e03fd68f1c09f/image-20260115-070256.png?cb=c502e1a6571430b9c269ee95642ea490) ## **Overview** * Audit logs list "who did what, where, and when" within the selected account, helping with security, troubleshooting, and compliance tracking. * The page only shows events for the currently selected account/vendor. ### **Page layout** * Select period: Choose the start and end date/time to define the time window for events to search; widening the window returns more events, narrowing returns fewer and can speed up queries. * Records: Sets how many log entries are returned per page for each search, up to 1000; use a smaller value for faster responses. * Filter: Enter text to match common fields (for example, user email, username, event name, or object name) to get better results. Use the full email/username to get desired data. * Search: Executes a query using the currently selected date/time range, record limit, filter and category; the table is empty on first load until Search is clicked. * Export: After running a search, click Export to download the currently displayed audit log results as a JSON file; only the data returned by your most recent search, including any selected filters, date/time range, record limit, will be included in the exported file. ### **Text Filter** The Audit logs text filter supports advanced matching to help refine search results: * **Multiple words:** When the filter contains two or more words separated by space (e.g., `user login`), results will include only audit logs that contain both words, in any order. * **Quoted text:** When the filter contains quoted text (e.g., `"user login"`), results will include only audit logs that exactly match the quoted phrase. * **Wildcard text:** Filter supports wildcards (`*`) to perform partial matches: * `Document*` matches any text starting with "Document" (e.g., `DocumentProcessing`) * `*Document` matches any text ending with "Document" (e.g., `ScanDocument`) * `*Document*` matches any text containing "Document" (e.g., `ScanDocument-506`). * **Mixed filter query:** When combining quoted text, normal words, and optional wildcards (e.g., `"user login" admin *failed*`), results will include audit logs that match the exact quoted phrase and also contain the other specified words or wildcard patterns. * *Note:* Wildcards inside quoted texts are not supported (e.g., `"user login *failed*"`). Filter does not validate or check for incomplete quotes or malformed wildcard expressions. ### **Categories** The Category filter groups audit log events by the product area they belong to. Selecting a category narrows the search to events from that group. All is not a real category --- it returns events from every category. * **Authentication** Sign-in related activity, including: * User logins and whether they succeeded or failed * Sign-in through an external identity provider (SSO/OAuth), and errors reported by that provider * An administrator testing a login provider * **Documents** What happens to stored documents --- uploading, updating, downloading, or deleting a document. *(Sending a print job or scanning is recorded under Print and Scan.)* * **Print** Print job activity --- a job being sent to the system (including from mobile), released at a device, released all at once, or cancelled. * **Scan** Scanning activity --- running a scan workflow, submitting a scan, and listing the scan workflows available to a user or device. *(Scan to Email is currently recorded under Others.)* * **Users** Searching for users and groups in a connected directory or identity provider. *(Creating, changing, or deleting users, groups, and roles is recorded under Settings.)* * **Settings** This is the main place to see who changed a setting. It covers configuration and administration changes across the system, grouped as: * **Identity \& access:** accounts, users, groups, roles, permissions, login providers * **Infrastructure:** devices, terminals, locations, servers, storage * **Feature configuration:** print, scan, and mobile settings * **Security** Access to sensitive areas --- someone opening or searching the audit logs, and a partner or administrator accessing a customer's account, along with the reason they entered for accessing it. * **Others** Anything that doesn't fit the categories above --- for example, Scan to Email, document conversion, card registration, directory synchronization, device configuration, credit and balance changes, licensing, certificates, and general preference changes. ### **Usage tips** * If expected events are missing, change the time window or increase the record limit, then click Search again to reload results for the new criteria. * Start broad (no filter, wider time range), then add a filter or category to drill down quickly; this mirrors common "filter‑then‑paginate" UX patterns for admin dashboards. * For identity lookups, search by the complete email or username to get desired data, then use Category to focus on Authentication, Authorization, or similar groups if available in the dataset. ### **Working with results** * Results table: Each row shows key fields such as Time (event timestamp), User (actor), Category (event group), Trace ID (request correlation), and Summary (human‑readable description) for quick scanning of activity. * Expand details: Click a row to expand and view full event payload details like request context, IP/user agent, result (success/failure), and object identifiers when present; use Trace ID to correlate with backend logs for incident investigations. * Copy to clipboard: In the expanded event payload, click the Copy to clipboard icon to copy the payload as pretty-printed JSON to your clipboard. * Incremental review: Raise the Records limit or adjust the time range to iterate through larger periods in manageable chunks ### **Behavior notes** * No automatic refresh: The page does not auto‑load data; click Search to fetch events for the chosen criteria. * Permissions and scope: Visibility depends on the enabled feature flag and user role; content is scoped to the selected account to avoid cross‑tenant exposure. --- version: "2026.08.20" variant: "PMC" language: "en" --- # Authentication providers ## Introduction To log in to PMC Web UI, submit print jobs, release print jobs on PMC terminals, use the Mobile app, etc, the users must be authenticated. Use the **Authentication providers** tab to configure how the users will be authenticated. PMC supports two main authentication types: * Local user authentication * Authentication to external directory via * OIDC * Service account (Service access) * Client-side authentication Users who have been authenticated from the external directory using either a card or a PIN will not be deleted from the PMC database if the external directory deletes the user. Such cleanup should be executed through the use of API functions. **Their card and/or PIN will also remain assigned to them, which may prevent reusing those credentials for other users (e.g., when companies attempt to reassign cards or PINs of former employees).** ## Local user authentication This is the simplest authentication type where the users are created and managed manually in the PMC server, under the built-in **Local authentication provider** . By default, there are few users predefined for each created account, including the **admin** user. We recommend keeping the local admin user as a fallback login in the case of failure of other authentication methods, such as provider misconfiguration, access token expiration, network issues, or a service disruption on the part of your external authentication provider. In settings of local provider you have options to change visibility of login form (you can hide username/password and leave only provider buttons) and local provider login button (redirects to login form specific to local provider users, e.g. guests). ## Authentication based on OpenID Connect (OIDC) This type of authentication enables connecting to an external authentication provider through OIDC. PMC supports the following authentication providers for OIDC: * Microsoft Entra ID * Google Workspace * Okta We recommend OIDC as the most secure authentication method. It enhances security by redirecting users Web UI and client workstations to the authentication provider's login page, ensuring that credentials are only entered at the provider's site. Furthermore, it eliminates the need for repeated credentials entries and supports multi-factor authentication (MFA). MFA is only supported for Web UI and client workstations. At the MFD terminal, username and password login works only if MFA is disabled. OIDC authentication doesn't allow synchronization of card IDs and PINs. If you have this information stored in your authentication provider (instead of directly in PMC), you may also want to configure service access for the same provider to allow users to log in at the MFD terminal using their company cards and PINs. ### Logging in using the OIDC authentication method When an authentication provider is configured with the OIDC authentication method, users can log in via such authentication provider in two ways: * Entering a username matching the authentication provider. * Clicking **Login via \** on the login page. When a user enters a username that matches the authentication provider with enabled OIDC authentication, they are redirected to the provider's login page, where they authenticate and then are redirected back to PMC. When the user clicks**Login via \**, they are also redirected to the provider's login page. When configuring the authentication, you will be able to choose whether to show the provider-branded **Login via \** button on the login page. User details are synchronized during every user login (either via PMC Web UI, PMC Client, MFD terminal, or the Mobile app), except for the user logging in within the lifespan of the existing OIDC Access Token (usually 60 minutes after the first login). ## Authentication based on the service access This authentication method requires you to create a service account in your external authentication provider. This account must have permission to search and retrieve users. PMC supports the following authentication providers for service access type: * Microsoft Entra ID * LDAP (including Active Directory) * Okta If you choose this authentication method, you must enter the service account details (e.g., username and password) in the authentication provider settings in PMC. Users can authenticate against the PMC server using all available login types: username/password, card ID, and PIN. We do not recommend using the service access authentication method for authentication providers that support OIDC. Set up OIDC for user login to PMC Web UI and PMC Client, and if you need users to log in via company cards or PINs stored in your authentication provider, set up the service access authentication in conjunction with OIDC. Microsoft Entra ID and LDAP do not support multi-factor authentication (MFA). Also, the Okta MFA support is very limited when using service access authentication only. In these cases, we strongly recommend using OIDC authentication. ## Client-side authentication This type of authentication requires PMC Client software, which uses interactive browser-based authentication provided by the external authentication provider. You don't need to create service access. MFA is fully supported. The limitation of this authentication type is that users cannot log in at PMC terminals via username and password, card IDs, and PINs stored in the authentication provider. Only local card ID and PIN logins are supported. However, users can log in via the one-time passwords (OTPs) functionality. This is useful, for example, for local card registration. You can generate OTPs manually in the Web UI or automatically by setting up triggers. See the section on [My profile](https://docs.ricoh-pmc.com/docs/latest/pmc/my-profile.md) for more information. The PMC Client automatically refreshes information about users from external authentication providers at periodic intervals. After a successful refresh, the user can log in at the MFD for a time defined in the user expiration policy in the authentication provider. If the PMC Client is offline (or hasn't successfully refreshed information from the external authentication provider), and the time defined in the user expiration policy has passed, the user won't be able to log in at the MFD. ## Authentication configuration ![image-2024-12-9_15-4-0.png](https://docs.ricoh-pmc.com/__attachments/a_5c9baf0e33c2234e3c225c185ead1a1d25bbd117634d138a7fe48c7c29526406/image-2024-12-9_15-4-0.png?cb=5d622571d6675c5dc10026988943da5e) The following authentication provider types are available: * **Local** -- Local authentication provider. It will authenticate users against the internal user database in PMC. * **LDAP**-- LDAP authentication provider enables authentication using LDAP/LDAPS against Active Directory, Novell eDirectory, and IBM Domino. * **Microsoft Entra ID** -- Microsoft Entra authentication enables authentication against Microsoft Entra ID. See [Microsoft Entra authentication](https://docs.ricoh-pmc.com/docs/latest/pmc/microsoft-entra-authentication.md). * **OKTA** -- OKTA authentication enables integration with the OKTA authentication service. See [OKTA Authentication](https://docs.ricoh-pmc.com/docs/latest/pmc/okta-authentication.md). * **Client** -- Client authentication is a special type of authentication performed by the PMC Client on the client side. See [Client authentication](https://docs.ricoh-pmc.com/docs/latest/pmc/client-authentication.md). * **External** -- PMC supports external authentication providers where external authentication service such as External Card Repository is used to identify users from different authentication providers. A newly created vendor or customer accounts always has the **Local Authentication Provider** added by default. It cannot be removed. There is no limit to the number of authentication providers you can add. You can define a priority number for every provider (a higher number means higher priority), which is used for every logical operation where the order of providers matters. Warning: In a production environment where numerous users are enrolled in the system, deleting an Authentication Provider will result in users' information not being available anymore for authentication, retrieving card numbers, PINs, etc., as user records are bound to the Authentication provider ID that was used when adding them to the database. See additional instructions for configuring specific authentication providers: * [LDAP authentication](https://docs.ricoh-pmc.com/docs/latest/pmc/ldap-authentication.md) * [Microsoft Entra ID authentication](https://docs.ricoh-pmc.com/docs/latest/pmc/microsoft-entra-authentication.md) * [OKTA authentication](https://docs.ricoh-pmc.com/docs/latest/pmc/okta-authentication.md) * [Client authentication](https://docs.ricoh-pmc.com/docs/latest/pmc/client-authentication.md) * [External authentication](https://docs.ricoh-pmc.com/docs/latest/pmc/external-authentication.md) --- version: "2026.08.20" variant: "PMC" language: "en" --- # Background As business models change, customers are moving away from existing, often complex, IT infrastructures. They're getting ready to modernize their print infrastructure and source future-proof solutions to take their print to the cloud. With new technology trends, IT is moving away from traditional on-premise data center hosting and towards cloud-native solutions; similar to other cloud services adopted internally (such as Microsoft, Amazon, or Salesforce), customers want to use "pay as you go" services in their print infrastructure. A cloud solution allows them to simplify their IT infrastructure and get rid of the complexities associated with traditional print, including multiple print servers, additional infrastructure components, and a user setup that is difficult to support and maintain due to the nature of the print driver configuration and device setup. It also gives them the opportunity to unify and centrally manage all printers across an entire fleet, in multiple locations, so they don't have to suffer under the complications traditionally prevalent with legacy systems in large businesses with a broad presence and a need for a distributed infrastructure, resulting in substantial costs in terms of infrastructure investments and IT administration. Imagine a solution where this administrative hassle and investment are significantly reduced by allowing customers to move the entire print infrastructure to the cloud. By utilizing a highly scalable Linux Server platform, we have developed a new solution to minimizing, or even removing, customer print servers and introducing an easy-to-use single print driver capability that enables customers to reduce or eliminate their print administration and support overhead. Moving the entire print management solution to the cloud enables the customers to capitalize on the benefit of a "pay as you go" OPEX transaction instead of a CAPEX investment. ## What is PMC PMC is a true-cloud software platform that takes print infrastructures to the cloud and makes printing easier and more secure -- for IT as well as the end users. It is a cloud-native full-stack platform, capable of providing organizations with full-fledged flexibility and all benefits of a Software as a Service (SaaS) offering while accommodating users with all the features of a traditional print management solution. PMC is designed for elasticity, meaning it easily scales and fits into complex architectures. The solution meets customers wherever they are in their cloud journey, and scales up or down with them--at their pace. The solution offers simplicity, automated workflows, zero-trust security, serverless printing, and a smooth user experience. PMC is not only a SaaS offering but also a cloud-native print platform intended to enable solution providers to become a SaaS Print Management provider. RICOH PMC is designed as a white-label product that enables service providers to offer and maintain their entire customer and reseller portfolio in the same highly scalable multi-tenancy cloud solution. This means that PMC enables solution providers to become SaaS providers and offer their customers all the benefits of a cloud-based print infrastructure solution. ## Why PMC PMC is a cost-effective shortcut for you to become a cloud-first service provider almost instantly and enables you to offer your customers all the benefits of a subscription-based service while eliminating the recurring cost of operating a dedicated Print Management environment. You will benefit from the same highly scalable Linux technology, be able to reduce or even eliminate print servers, dramatically reduce TCO or CAPEX for your customers, and become the messenger of a strong business case to your customers. Being able to administer your entire customer portfolio from one centralized administration portal will optimize your support efficiency and improve the service level and "time to solution" for your customers. By selecting PMC as your print services platform, organizations and service providers will benefit from all the advantages of the newest cloud business models while having all the necessary features available in traditional on-premise print management solutions at their disposal. --- version: "2026.08.20" variant: "PMC" language: "en" --- # Brother Gen 1 Terminal ## MFD Prerequisites The default administrator password on the MFD has been set. The MFD supports the Brother Solution Interface(BSI). 'Scan to Email' must be enabled on the MFD ## Brother Solutions Interface BSI Supported devices list can be found in Ricoh PMC Support Site. ## Installing ### Installing Terminal Application 1. Make sure your secondary gateway is configured according to [Secondary Gateway mapping](https://docs.ricoh-pmc.com/docs/latest/pmc/secondary-gateway-mapping.md). 2. Push the Embedded configuration from embedded screen in PMC. ![embedded_templates_detail.png](https://docs.ricoh-pmc.com/__attachments/a_deeebce996f10857be0df8e2252ca70f398a538d8dcde794266d66812d9a34b5/embedded_templates_detail.png?cb=d369cbc82e53cb6ef106efa49e873de3) **Up until 3.27** , the server address had to be a hostname that the printer could verify to make a proper secure connection. If an IP-setup was used configure the embedded client, the user would have to access the webpage of the printer and manually change it to using non-secure HTTP and port 8704 to be able to use the Brother client. ***Starting from 3.27, this is now done automatically, if it is detected during installation that an IP is used.*** This means that, if an IP setup is used, for some instances of communication with PMC and local communication on the printer, non-secure HTTP and port 8704 is used. For PMC, this includes installation and uninstallation. Locally on the printer, this occurs whenever the Brother system initiates a redirect; on login, logout and when the embedded app is accessed through the solutions app on the printer. To see (or change this setting), access the webpage of the printer -\> login -\> Administrator -\> Solutions -\> Solutions Application Entry -\> press Login / Logout /Menu1. ### Deploying CA Certificate To enable communication between the gateway and the MFD, install the CA certificate that signed the gateway certificate on the MFD. 1. First, obtain the CA certificate. You can either: * Use a CA certificate signed by a trusted authority * Generate a self-signed certificate (only if you understand and accept the security risks) 2. Then import the CA certificate to: 1. SQC server certificate trust store (see [Certificates](https://docs.ricoh-pmc.com/docs/latest/pmc/certificates.md)) 2. MFD certificate trust store: * ![ca-certificate.png](/__attachments/a_db840267ffd5eb0b7f178d8ecebd0261099491cde3cabfd99e3c05157d03ceda/ca-certificate.png?cb=76e49295afcac544b0b5855bf285435e) * Some MFDs have a limit of 4 certificates. You may need to delete existing certificates before installing new ones. This can also be an issue if multiple leaf certificates must be installed. ## Uninstalling Uninstalling the Brother client is straight-forward (as in using the uninstall-button through PMC). However, **a currently running embedded instance must be exited after uninstallation** , either manually or through waiting for the automatic timeout on the printer to trigger, or they will still be able to use the embedded client. Also, If a user was logged while the uninstallation took place, **they must manually logout**. ## Troubleshooting ### **BSI** If BSI is missing, then you have to request access to development resources at the link below: [Enable BSI](https://online.brother.co.uk/developer/bsi) Once BSI is enabled, the "Solutions" (or "Solutions Settings") section will appear in the MFD web interface, and you should be able to set "Solutions" to "On." Please note manual change is not required for the installation to complete, as the installer can enable it automatically. #### **Customize login message** The printer has the option to customize the login message from the printer web page. Under Administrator -\> Solutions you can change Login Portal Message to the message you want, the default english text is "Login Requested" #### **Scan to email** Verify that there is an entry 'Scan to email-server' in the scan-menu. The scan menu can be reached, on the printers display, from the main screen. If the 'Scan to email-server' is not present, you'll need to install a firmware addition. #### **Card readers** As standard only a few card readers are supported on the Brother devices. Remember to enable USB card reader support. To add support for additional readers you have to set up External Card reader on the printer web page. ![external-cardreader.png](https://docs.ricoh-pmc.com/__attachments/a_7b040f7a6d4750d7bf82a36cce08541804c6898a72208a22d5be0a388a7abf17/external-cardreader.png?cb=39434fe3e180d89229bebcbbe54ea2af) #### **Solutions Application Entry** There needs to be 3 entries, Login, Logout and a menu. For **login** URL should be https://\[SERVER\]:8703/WebClientBrother/login/start, leave arguments empty ![login-application-entry.png](https://docs.ricoh-pmc.com/__attachments/a_b551922fe54c796cc1eb59e0128d98197a9ba64de7c93525179fe9f1e0b067dc/login-application-entry.png?cb=e3fb3f248e004bf32daa5e4873442f3f) For **Logout** URL should be https://\[SERVER\]:8703/WebClientBrother/main/logout For **MenuX** URL should be https://\[SERVER\]:8703/WebClientBrother/login/start #### **Error codes** Refer to the following chart to check and solve the error code displayed on the LCD of the Brother device [Error codes](https://support.brother.com/g/b/faqendbranchprintable.aspx?c=de&lang=de&prod=ads2600w_eu_as_cn&ftype3=1964&faqid=faq00002845_003&ot=eu_ot&printable=true) #### **Error configuring terminal (HBT-5347)** webclientBrother.log shows: 09:22:09.475 [1-862] {DEBUG } headers - http-outgoing-1 >> GET /home/status.html HTTP/1.1 09:22:09.506 [1-862] {DEBUG } wire - http-outgoing-1 << "HTTP/1.1 404 Not Found[\r][\n]" 09:22:09.544 [1-862] {ERROR } Configurator - Configure failed org.apache.hc.client5.http.HttpResponseException: status code: 404, reason phrase: Not Found To resolve issue go to MFD administrative interface → Network → Protocol → Web Based Management (Web Server) → HTTP Server Settings and: * Enable "HTTP (Port 80)" * Disable "Always redirect to HTTPS" #### **Error configuring terminal (SNMP)** webclientBrother.log shows: 10:04:08.217 [1-860] {WARN } SnmpUtility - SNMP request timeout: 10.0.10.109 10:04:08.217 [1-860] {ERROR } Configurator - SNMP failed to setup Could not enable BSI 10:04:08.217 [1-860] {ERROR } Configurator - Configure failed com.ubiquitech.brother.exceptions.Http4xxException To resolve issue go to MFD administrative interface → Network → Protocol → SNMP → Advanced Settings and: * Enable "SNMP v1/v2c read-write access" * Configure "Community name" "Set" to "internal" --- version: "2026.08.20" variant: "PMC" language: "en" --- # Brother Terminal --- version: "2026.08.20" variant: "PMC" language: "en" --- # Canon Gen 1 Terminal ## Limitations Canon Terminal can be installed only on MFDs in Europe. Other regions are not approved by Canon yet. ## Prerequisites * A custom login application will be installed on the MFD. This requires obtaining the necessary files from the PMC folder: ***/opt/*** ***hcp*** ***/conf/canon*** Required files are: * * a Java package file (YSoft SAFEQ Embedded Terminal_1.6.0.jar) * an accompanying text file (A1_YSoftSAFEQEmbe_160_20230905085252_0001.txt). The text file contains a License Access Number that will be used to generate the license file (.lic). * The "Web Access" browser/software must be installed on the Canon MFD. When this web browser is installed on the MFD, it can be verified on the printer homepage (RUI) under Status Monitor/Cancel: Device Features -- Other. * You have configured your secondary gateway according to [Secondary Gateway mapping](https://docs.ricoh-pmc.com/docs/latest/pmc/secondary-gateway-mapping.md). ## License file generation Beforehand, it is recommended that you gather the Device Serial Number for all the MFDs you need to install the application on. To generate the license file, we need to follow the steps and instructions available on the Canon website for the License Management System. * Open this a web browser and go to this address: * Enter the License Access Number provided in the downloaded text file, then press 'Next': ![canon1.png](https://docs.ricoh-pmc.com/__attachments/a_e1775676488b142fb9d12187f130558d322311efe78021a9f676971f59135a63/canon1.png?cb=226e89e82f166279e099ca6ba7d0f684) * Review the information on the Product Check page, then press 'Apply to Issue a License': ![canon2.png](https://docs.ricoh-pmc.com/__attachments/a_b8613414648ecf67c966885fc5f77b499f87c35cbd248217bdc106c34945a053/canon2.png?cb=701c2716c5bf1d9a8415ec055a0a7b96) * On the 'Serial Number Registration' page enter the Device Serial Number(s) for the impacted MFDs: ![canon3.png](https://docs.ricoh-pmc.com/__attachments/a_7a4818e98e094ad6818d74d1d3ed225c6568d4f32bab0b3a3c810f4cf538c961/canon3.png?cb=b3c2b33ad57ecad007b81c927668e630) * On the following pages confirm the information provided and retrieve the issued license file. ## Install Login application On a Canon device, an embedded login application must be installed in order to make the Browser client work. To install the Login app, follow these steps: * Open the following page in a web browser and enter the MEAP admin password to login. The default password is '*MeapSmsLogin* ' http://\[PrinterIpAddress\]:8000/sms/ ![canon4.jpg](https://docs.ricoh-pmc.com/__attachments/a_f8d29fffc694661567827197bce337d6eceec2ecf20c2b21b86243fe1dfaa3bf/canon4.jpg?cb=6717301ab75d8a9ef6a08218d9e8be1a) * Click on 'Enhanced System Application Management', and then inside the 'Install Enhanced System Application/License' section: - For the 'Enhanced System Application File Path' select 'Browse...' and point to the downloaded .jar file - For the 'License File Path' select 'Browse...' and point to the downloaded .lic file ![canon10.jpg](https://docs.ricoh-pmc.com/__attachments/a_6a6701c820b1cf6b254654a378e6c92aa7417cb0b253b589d80462695dbf5d5b/canon10.jpg?cb=9dc743c29e6e305ee0afee624387bd0e) * Click 'Install' * Click 'Yes' if a confirmation page is displayed. * In the list of Login Service applications, the page should look like this: ![canon11.png](https://docs.ricoh-pmc.com/__attachments/a_4136ef53cc5bea46d4797ec64ad7bbe1e523c048e5f9246e4631db24d0630279/canon11.png?cb=fcf5d1ebfb2ba13427cf4753529adb69) * Reboot the device to complete the installation (Reboot can be done remotely by pushing "To portal" and then "Restart Device" under "Settings/Registration") * After the Printer is restarted push the Embedded configuration from embedded screen in PMC ## Setup browser * On the device, open "Web Access" browser and enter the following address (take care as it is case sensitive), and afterwards click "OK": https://\[SERVER-ADDRESS\]:8703/WebClientCanon/client or https://\[SERVER-ADDRESS\]:8703/WebClientCanon/client?addr=hostname for the DNS setup ![enter-client-address.png](https://docs.ricoh-pmc.com/__attachments/a_d5ae786c1f76c863ffce7babb5cfb65310ed70287baabf7289f4a8562c6b0fa4/enter-client-address.png?cb=fe7cc32b9b1b5e98fbd2511bb6b9cad6) * After the web page is loaded, hit the "Favorite" button ( ![canonbrowser12.jpg](https://docs.ricoh-pmc.com/__attachments/a_f0d964d9b346ea2d1d6b67abfa33ff1129f6478583c700ff803890400d7b5d2d/canonbrowser12.jpg?cb=0575dbcfe9d5018ccfb556b3feced2f6) ), then select "Register to Quick Menu" and choose the first "Not Registered" slot. ![add-to-favorite.png](https://docs.ricoh-pmc.com/__attachments/a_c51a49b9ec53798d12fe37cbc8cd201220f0a9899d084ac2ae0d447c2c1906da/add-to-favorite.png?cb=7e1dc94b7035bdacc2359b75440c5143) * Give the button a name and choose "OK" ![register-home.png](https://docs.ricoh-pmc.com/__attachments/a_83730874e29147c0223a9a15edb596da79d52de4d8b2f16f7735037e93001ec3/register-home.png?cb=ef74c0342aa450a1eac7ec528320968d) * Now the button is added in "Shared" functions in the "Quick Menu" ![home.png](https://docs.ricoh-pmc.com/__attachments/a_1f9e649836c98d14d1187b5bf8486ecdafc67ca9b4cca3ed0dd9ea7db7914092/home.png?cb=94292839f034c440623c599441c3ef88) Notes: * For changing the default menus and buttons, refer to the Canon manual * To use a card reader on the device, you need to enable the card reader within the menu of the Canon device. Go to: "Settings" -- "Preferences" -- "External Interface" -- "USB Settings", and then change "Use MEAP Driver for USB Device" to "On". Remember that the card reader needs to be configured as Keyboard emulated. ## Uninstall login application * Open the following page in a web browser. The default setting for both the System Manager ID and System PIN is '*7654321*': https://\[PrinterIpAddress\]:8443/sms/rls * Push the "Switch" beside the "User authentication." ![canon20.png](https://docs.ricoh-pmc.com/__attachments/a_12565f0b5d069817af7f28dea3d153a4ff63dd21b3d56823d688c15323d36ecd/canon20.png?cb=69cca7c9ecbf6627b919ecc6f22274ad) * Then the screen should look like this: ![canon21.png](https://docs.ricoh-pmc.com/__attachments/a_c9b93f8f91140846965a063425650cfb80012cc9a8f415b04d27695ffa7f9c22/canon21.png?cb=e45a0aba166bfb84ef61ccd67ca5af1c) * Reboot the device * After reboot, log in by using the administrator's username and password for the Canon Device. The default user name for the administrator is "*Administrator* " and the default password is "*7654321*" ![canon13.jpg](https://docs.ricoh-pmc.com/__attachments/a_6af44c6ef0cb7b75130e54c89a697e0eb931bd076ada501e0895736ab062df82/canon13.jpg?cb=d3f225fce886133a47d52ce941794c7c) * Browse to "Service Management Service" * Push the "Uninstall" beside the "YSoft SAFEQ Embedded Terminal." If the uninstall button is disabled, you may have to disable and delete the license file. * Push "Yes" to uninstall YSoft SAFEQ Embedded Terminal. ![canon22.png](https://docs.ricoh-pmc.com/__attachments/a_a8a8f555b6dff0baf622df59e5352db259686ddfbc90ed4bd18c4a27716b222f/canon22.png?cb=f2ddf5f115b93798781d16dbd8c6a618) * Reboot device, and then the uninstall of the "YSoft SAFEQ Embedded Terminal" should be finalized. --- version: "2026.08.20" variant: "PMC" language: "en" --- # Canon Gen 2 Cloud Terminal --- version: "2026.08.20" variant: "PMC" language: "en" --- # Canon Gen 2 Cloud Terminal Release Notes **Legend:** ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Added feature** ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Improved/changed feature** ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Bug fixed** ## Version 2026.08.18 ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Basic quota support** The terminal now supports user print quotas for jobs released through the SAFEQ Cloud print application. (HCP-17103) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Detailed print progress** The terminal now shows detailed progress while a job is being printed instead of a generic waiting state. The implementation also removes the few-second gap between consecutive jobs, so printing several small jobs in a row is noticeably faster. (HCP-16962) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Fixed stuck "Please wait" screen on older device lines - added new HTTP client** Older Canon device lines could remain stuck on the "Please wait" screen because the terminal relied on an HTTP client that is not working on those models. The terminal now fallbacks to a new client supported across the older device lines, so the terminal loads and operates as expected on the full range of supported devices. (HCP-16804) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Fixed print jobs failing with unsupported data error** Print jobs submitted through the PC Client could fail with the message "Could not execute because the file contains unsupported data", leaving the job unprinted. Jobs are now generated in a format the device accepts and print reliably on affected models, including imageRUNNER ADVANCE C3520, C5860 and C5550. (HBT-6505) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Fixed print jobs from a custom driver failing to execute** Jobs sent to SafeQ Cloud through a custom driver failed when released at the terminal. Such jobs now print correctly, and the finishing-options icon is shown only for jobs that actually carry finishing metadata. (HBT-6597) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Fixed admin credentials change not persisting when only the password is changed** When an administrator changed only the password of the terminal admin credentials and left the user name unchanged, the new password was not stored and the previous one remained in effect. Credential changes are now saved reliably regardless of which fields are modified. (HBT-6465) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Fixed incorrect scan resolution for some values** Some entries in the Scan resolution list (Low, Normal, Fine, High, Highest/Super) produced scans at a different DPI than selected. The DPI values now match those used by the other terminals. (HBT-6584) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Fixed administrator seeing the previous user's Quick actions screen** After a regular user logged out, an administrator opening the Print and Scan app was shown the Quick actions screen of the previously logged-in user. The administrator now gets an empty Quick actions screen instead. (HBT-6596) ## Version 2026.06.04 ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Fixed broken density setting** The density setting under scan settings is now displayed correctly and is reliably applied to scans. Previously, the setting could appear incorrectly or fail to take effect, leading to unexpected scan results. (HBT-6370) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Fixed scan to JPEG format** When scanning with the JPEG format selected, an empty document is no longer created. Users now receive the expected output, ensuring scans complete as intended without invalid files. (HBT-6369) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Fixed translations containing broken variables** Translated text that previously displayed broken or unresolved variables now renders correctly. This ensures users see clear, properly localised messages throughout the interface. (HBT-6384) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Fixed language selector selecting language when scrolling** The language selector no longer unintentionally changes the selected language while the user is scrolling through the list. Languages are now only selected on a deliberate choice, preventing accidental changes. ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Fixed duplicated endpoint screen when retry button is used** Using the retry button no longer results in a duplicated endpoint screen. The interface now handles retries cleanly, providing a consistent and uncluttered user experience. (HBT-6347) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Fixed scan paper size selection dropdown size** The paper size selection dropdown under scan settings is now displayed at the correct size, making it easier for users to view and select the appropriate paper size. (HBT-6369) ## Version 2026.05.20 ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Scan workflows support** Users can now access and run scan workflows from the terminal interface. Scan workflows enable users to scan documents into predefined destinations and formats, supporting common business processes such as scanning to email, network folders or cloud storage. The terminal provides a simple and consistent workflow selection experience, helping users complete document digitisation tasks quickly and securely. (HCP-16221) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Improved terminal security with token signing and replay protection** Token signing has been introduced alongside replay protection. This ensures terminals remain secure and that device code flow does not need to be re-run. (HCP-15394) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Custom logo upload has no longer 10 kB size restriction** Custom logo uploads were limited to a 10 kB file size, preventing administrators from uploading standard-sized logo files and resulting in missing logo on the terminal. (HCP-15585) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Pull print now supports all finishing options** Users can now pull and print jobs with the full set of finishing options originally defined within our driver, such as stapling, hole punching, and folding. This ensures finishing settings are correctly transferred and applied when printing from the cloud, so output matches the intended job configuration. (HCP-15861) Users can now also set or modify basic finishing options directly on the terminal, such as number of copies, colour, or duplex. ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Users are notified when print job finishing options are not supported** When a print job contains finishing options the target device does not support, the user is now clearly informed before or during printing. This prevents silent failures and gives users the opportunity to adjust settings or select a different device, ensuring a predictable printing experience. (HCP-15862) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Support for custom public CA-signed certificates** Administrators can now configure the terminal to trust custom public CA-signed certificates for their SAFEQ Cloud tenant, rather than relying solely on the default certificate chain. (HCP-15977) ![warning](https://docs.ricoh-pmc.com/__attachments/a_8350dbf1492fc70f7bcf35e3e84340ebb109c1317b4f657645641b3d00058430/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **Fixed Canon device copy operation causing terminal instability** When using the Canon device copy functionality, device-specific data was incorrectly included in the copy operation. This could cause a newly provisioned or reset terminal to break. (HCP-15981) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Support for proxy with basic authentication** The terminal now supports connectivity through proxy servers that require basic authentication credentials. (HCP-15992) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **PIN code auto-submits when the OK key is pressed** Users can now confirm their PIN entry by pressing the OK key on the device, which automatically submits the PIN without requiring an additional step. (HCP-16050) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Terminal settings secured with MFD admin credentials** Terminal configuration settings are now protected by MFD administrator credentials, preventing unauthorised access to the terminal setup. Additionally, administrators can now unlock the MFD directly from the terminal interface. This enhances overall security and gives administrators reliable control over both terminal configuration and device access. (HCP-16178) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Terminal can be configured using the Terminal Deployment Tool (TDT)** The terminal can now be remotely configured using the Terminal Deployment Tool, enabling centralised and automated configuration management across device fleets. This reduces the need for manual on-device configuration and supports efficient, consistent deployments at scale. (HCP-16179) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Stored device token and API key are now encrypted with a device-specific compound key** Device tokens and API keys were stored without device-specific encryption, posing a potential security risk if stored credentials were exported with weak password and the export decrypted. Both credentials are now encrypted using a compound key derived from device-specific secrets. This binds the credentials to the originating device, preventing unauthorised reuse or extraction on a different device. (HCP-16180) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Push print features now at parity with Canon Gen 1 Embedded Terminal** The push print functionality has been extended to match the full feature set of the Canon Gen 1 Embedded Terminal. Existing users migrating from the first-generation Canon ET will benefit from a consistent and complete push print experience, ensuring a smooth transition with no loss of functionality. (HCP-16180) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Installation automation** Terminal installation can now be automated, significantly reducing the manual effort required during large-scale deployments. IT administrators can streamline rollouts across device fleets, ensuring consistent and repeatable installations. (HCP-16363) ## Version 2026.02.13 ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Terminal self-registration** The terminal can now register itself and obtain a device token autonomously, without requiring manual printer creation for each device. (HCP-14967) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Terminal configuration persisted across device restarts** Terminal configuration is now saved and retained across machine restarts and power cycles. Administrators no longer need to reconfigure the terminal after a restart, ensuring consistent operation and reducing post-maintenance overhead. (HCP-15043) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Endpoint registration** The terminal now supports full endpoint registration with the SAFEQ Cloud infrastructure. This enables the device to be recognised and centrally managed as a registered endpoint within the SAFEQ Cloud environment. (HCP-15057) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Administrators can add output port and embedded client** Administrators are now able to configure the required output port and embedded client for the Canon Gen 2 Cloud Terminal directly within the Web User Interface. (HCP-15062) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Automated embedded terminal onboarding** The terminal now supports automated onboarding, including automatic creation of the output port and embedded terminal configuration. This significantly reduces manual setup steps and enables a faster, more reliable deployment process for new installations. (HCP-15314) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **PIN and username/password authentication** Users can now authenticate at the terminal using either a PIN code or a username and password combination. This provides flexible authentication options to accommodate a range of organisational security policies and user preferences. (HCP-15396) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Quick actions available on the terminal** A set of quick actions is now available directly on the terminal interface, allowing users to perform common tasks in fewer steps. This improves workflow efficiency and delivers a more intuitive experience at the device. (HCP-15397) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Job list -- users can view their print jobs** Users can now see a list of their queued print jobs directly on the terminal before releasing them. This gives users full visibility into their pending jobs, enabling informed decisions about which jobs to print or discard. (HCP-15398) ![info](https://docs.ricoh-pmc.com/__attachments/a_430e00bcc0a158daaf4bc8dad3147fa981f731d5e21fe88723ca06efc69e8d59/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) **Application icon and name updated** The application icon and display name have been updated to reflect the current product branding.(HCP-15569) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Users can pull print jobs from the cloud** Users can now release and print their jobs from the cloud using pull print directly at the terminal. Jobs are held securely in the cloud until the user authenticates at the device and chooses to release them, enabling a flexible and secure printing workflow. (HCP-15581) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Custom logo support** Administrators can now upload a custom logo to be displayed on the terminal interface. This allows organisations to brand the terminal with their own identity, providing a consistent visual experience across deployed devices. Note that some limitations apply in this release. (HCP-15582) ![check mark](https://docs.ricoh-pmc.com/__attachments/a_054d61962f28ecc3d9e7af4b6f389adcd4202659ae2f84400ec68d5466657586/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Card authentication** Users can now authenticate at the terminal using their access card. Card-based authentication provides a fast and contactless login experience, supporting common card formats used in enterprise environments. (HCP-15583) [Next Page](https://docs.ricoh-pmc.com/llms-full.txt/1)