SS1 Cloud

Integration Specifications

Prerequisites

Checking your company code

When you register for SS1 Cloud, you receive a login URL. The {company_code} portion of that URL is your company code.

SS1 Cloud login URL, where the company_code portion is the company code

In addition to your company code, prepare the username and password you use to log in to SS1 Cloud.

If you use the overseas environment management option, the domain portion of the login URL (mgr.ss1-cloud-gl.com) differs.

Setting up the integration

On the integration screen, search for SS1 Cloud.
Select a region: “Japan (mgr.ss1-cloud.com)” or “Global (mgr.ss1-cloud-gl.com)”. Then enter your domain code (your company code), username, and password, and click Connect.
Once the integration with SS1 Cloud succeeds, registered user information appears in the account list. If it doesn’t complete successfully, first try the steps in Troubleshooting failed SaaS integrations. If that doesn’t resolve it, check Information to provide and contact support.

MDM Integration

If you are using the device management feature, you can synchronize devices with SS1 Cloud. For details, see 4-0. Sync MDM-Compatible SaaS with Your Device Ledger.

The SS1 Cloud device API provides information for Windows PCs, as well as Mac and mobile devices.Also, the serial number is not included in the SS1 Cloud API response, so it cannot be retrieved. It therefore cannot act as a merge key. Devices are always registered as new rather than merged with an existing device.

Synchronized Fields

This-Service Field	Sync Pattern	SS1 Cloud	Notes
Asset number	(2) This-service-based	`<mdmname>_<pc_name>`	A prefix is added to avoid duplicates.
Serial number (IMEI)	(1) MDM-based	Not available	Not included in the SS1 Cloud API response, so it cannot be retrieved.
Email	(2) This-service-based	Logon user record, via `logon_user`	Logon users have no email, so linkage is done by matching username.
Type	(2) This-service-based	`instrument_type_name`	”デスクトップパソコン” (desktop PC) → Desktop PC; “ノートパソコン” (notebook PC) → Laptop PC.
Status	(2) This-service-based	`work_status_name`	Set to “In Use” if the value is “社内作業” (in-office work). Handling of other values is still being reviewed.
Location 1 / 2	(2) This-service-based	`department` (Location 1 only)	Location 1 is synchronized from the department the device belongs to. Location 2 is not synchronized.
Purchase date	(2) This-service-based	`purchase_date`	May be empty.
Memory	(1) MDM-based	`memory_size`	In MB.
HDD/SSD	(1) MDM-based	`sysdrive_size`	Total capacity (in MB). Free space is kept separately as `sysdrive_free_size`.
OS	(1) MDM-based	`os_name`	Example: “Windows 11 Home”
Version	(1) MDM-based	`release_id`	Release ID (example: “25H2”).
Hostname	(1) MDM-based	`pc_name`	The computer name.
Last used (MDM)	(1) MDM-based	`last_survive_date`	The last SS1 agent heartbeat (check-in).
MDM link	(1) MDM-based	`https://mgr.ss1-cloud.com/mgr/instrument/detail/index/{id}/instrument`	The “Open in MDM” link goes to the device detail screen in SS1.
Managed	(1) MDM-based	`is_installed`	The SS1 agent install status.
Managed	(3) MDM field	(always Managed)

Introduction

Integration

Integration Guides

Integration Specifications

Prerequisites

Checking your company code

Setting up the integration

MDM Integration

Synchronized Fields

​Integration Specifications

​Prerequisites

​Checking your company code

​Setting up the integration

​MDM Integration

​Synchronized Fields

Integration Specifications

Prerequisites

Checking your company code

Setting up the integration

MDM Integration

Synchronized Fields