Google Workspace Integration

Securely connect Asset Panda to your Google Admin console to automatically import employee records into the Asset Panda directory and sync Google-managed devices for tracking. This integration keeps your employee and device data current, streamlines asset management, and eliminates the need for manual updates.

The process of integrating the Google Workspace account with Asset Panda to fetch data includes:

1. Connecting Google Workspace.

2. Setting up and configuring the Google Workspace integration in Asset Panda.

3. Mapping the fields from Google Workspace to Asset Panda.

Here’s how to connect Google Workspace with Asset Panda and take full advantage of both platforms:

1. Enable Google Workspace Integration: Start by linking your Google Workspace account to Asset Panda. This will allow you to pull in device and user data automatically.

2. Set Up Google Device Management: Once connected, you can easily add and manage all your Google Chrome devices in Asset Panda. You’ll have control to activate, deactivate, or de-provision devices when necessary.

3. Sync Mobile Devices: With Google Mobile Management, sync mobile assets in real-time to Asset Panda. This ensures that your mobile devices are always up to date, and you can even manage them remotely if needed.

Prerequisites

Before starting the integration, ensure you have the following:

• An active Google Workspace account.

• An active Asset Panda subscription.

• Administrative access to both Google Workspace and Asset Panda.

• Google Directory is configured for user management.

• Necessary permissions to configure integrations in both Google Workspace and Asset Panda.

---

Setting Up Google Workspace

Set Up Google Workspace OAuth

To connect Asset Panda with Google Workspace, you need to create OAuth 2.0 credentials in the Google Cloud Console. These credentials specifically a client ID and client secret allow Asset Panda to securely access directory information from your Google Workspace account. Follow the steps below to configure the required access.

1. Go to the Google Cloud Console and sign in with your Google Workspace admin account.

2. Create a new project.

   1. In the top navigation bar, select the project dropdown and choose New Project.

      • Enter a project name, such as Asset Panda Integration.

      • Select your organization (if applicable), then choose Create.

3. Enable the necessary APIs.

   1. In the left navigation, go to APIs & Services > Library.

      • Search for and enable Admin SDK.

      • (Optional) Enable People API if Asset Panda will access contact or user profile data.

4. Configure the OAuth consent screen.

   1. Go to APIs & Services > OAuth consent screen.

   2. Choose Internal (recommended for internal use) or External.

   3. Enter the required app details, such as:

      • App name: Asset Panda Integration

      • User support email

      • Developer contact information

      • Save and continue through the remaining screens.

5. Create OAuth credentials.

   1. Go to APIs & Services > Credentials.

   2. Click + Create Credentials > OAuth client ID.

   3. For the application type, choose Web application.

   4. Enter a name, such as Asset Panda OAuth Client.

   5. Under Authorized redirect URI, enter the following URIs:

      • https://www.assetpanda.app

      • https://assetpanda.app

      • If you are using a domain-specific URL to log in, add https://<domain>.assetpanda.app

   6. Click Create.

6. Copy the client ID and client secret. After the OAuth client is created, a dialog appears with the client ID and client secret.

   • Copy both values and store them securely. You’ll need them when configuring the integration in Asset Panda.

---

Asset Panda Tasks

Setup Google Workspace Integration in Asset Panda

1. Log in to Asset Panda. Go to Settings > Account Management.

2. For the respective module, Click Manage under Integrations.

3. Open the Integrations Store for the desired account.

4. Go to the Google Workspace tile and click Add from the Asset Panda Integration Store.

5. Switch to the Integrations in this module tab.

6. Go to the Google Workspace tile and click Configure.

7. Enter the Client ID and Client Secret you created in the Google Cloud Console.

Note: These values are generated when you create an OAuth 2.0 client under APIs & Services > Credentials in the Google Cloud Console. The Client ID is a public identifier for your application. The Client Secret is a confidential string used to authorize the secure connection. You can retrieve both after creating the OAuth client by selecting your credential name from the Credentials list.

1. Select Authorize to begin the authentication process. You're redirected to a Google sign-in page.

   • Sign in using a Google Workspace admin account.

   • Review and approve the access permissions requested by Asset Panda.

2. After authorization, Google redirects you back to Asset Panda and confirms the connection.

   • A green check mark appears next to the authentication section when the connection is successful.

3. Click Test and save connection to verify the setup and confirm that the credentials are valid.

4. Click Continue with mapping to start the user data mapping process.

5. Click Add mapping option. The Mapping Option window appears on the screen.

---

Choose your Mapping Type

After authorization, you’ll be asked to select a mapping path:

Option 1: Create Asset Panda user from Google Workspace with login access

• Use this to create users that will log in to Asset Panda and actively use the platform.

Option 2: Create Google Workspace users as collection records without login access

• Use this to import user or device records into Asset Panda for tracking, but without login access.

The flow changes based on your selection.

Create Users with Login Access

1. On the Mapping Option screen, select Create Asset Panda user from Google Workspace with login access.

2. Enter a Mapping Name (e.g., "G1").

3. Select the Organizational Unit from which users will be imported.

4. Assign a User Role to apply access permissions within Asset Panda (e.g., Collaborator, Admin, etc.).

5. In the mapping section, map fields such as:

   • First name

   • Last name

   • Email (required for login)

   • Any other relevant user metadata

6. Click Save to complete mapping.

7. Users will be created in Asset Panda with login access and assigned roles.

Unique Identifiers for Login-Access Users

Asset Panda uses a unique identifier to match users across systems and avoid duplication. In this mapping flow, Email is the most common and recommended unique field.

Field	Description	Unique?
Email	User’s primary login email address	Yes
User ID	Google-generated internal ID (via API)	Yes (API only)
First name, Last name	For display/reference only	No

Info: Always map the Email field to ensure proper identity matching and login provisioning.

User Deprovisioning & Status Handling (Login Users Only)

This section applies to users created in Asset Panda with login access via the Google Workspace integration. Asset Panda manages user deactivation based on the user’s status in Google Workspace and the availability of user data through Google APIs.

1. Deactivated / archived users: If a user is archived or otherwise deactivated in Google Workspace, the user information remains accessible via APIs and the corresponding Asset Panda login user is deactivated during the next sync.

2. Deleted users: If a user is permanently deleted from Google Workspace, Google does not expose the user data via APIs. In such cases, Asset Panda cannot retrieve or deactivate the user record.

Note: Asset Panda does not independently delete users. All deprovisioning actions depend on the user data exposed by Google Workspace.

Create Collection records (without login access)

1. On the Mapping Option screen, select Create Google Workspace users as collection records without login access.

2. Enter a Mapping Name (e.g., "G2").

3. Choose the External Entity from Google Workspace to import:

   • Users

   • Mobile Devices

   • Chrome OS Devices

4. Select the Asset Panda Collection to store the imported records (e.g., People, Hardware, Devices).

Tip: The field you select must be marked as unique in both systems. Only these fields will appear in the Unique Identifier dropdown.

1. Select a Unique Identifier from the dropdown. Example: Device ID, Email, Serial Number Confirm the corresponding Object ID in Asset Panda.

2. Click Add more mapping columns to define additional fields like: Name, Status, IMEI, OS version, Last Login, etc.

3. Click Save to complete the mapping.

Asset Panda now pull in collection records based on your configuration.

Info: Setting up an automation ensures data stays up to date by syncing records at scheduled intervals.

Unique Identifiers

Before mapping, you must select a Unique Identifier field from Google Workspace that ensures each record is imported uniquely. This varies based on the selected External Entity:

For Users:

Field	Description
Email	Primary email address
Customer ID	Organization-wide ID (not per user)
User ID	Google system-generated ID (API only)

For Mobile Devices:

Field	Description
Device ID	Unique Google-assigned ID
Serial Number	Manufacturer serial number
IMEI	Device IMEI
WiFi MAC	Network MAC address

For Chrome OS Devices:

Field	Description
Serial Number	Chrome OS device serial
Asset ID	Custom admin-assigned ID
Directory API ID	Internal device ID via Admin SDK

Permissions for managing devices and users

Device Management

These permissions are used to access and manage metadata for devices and organizational structure relevant to devices:

Permission	Description
admin.directory.device.chromeos	View and manage metadata for Chrome OS devices.
admin.directory.device.mobile	View and manage metadata for mobile devices.
admin.directory.customer	View and manage customer-level configuration details.
admin.directory.orgunit	View and manage organizational units.

User Management

These permissions allow access to manage users, groups, and related structures:

Permission	Description
admin.directory.user	View and manage user accounts.
admin.directory.userschema	View and manage custom user schema fields.
admin.directory.group	View and manage groups and their memberships.
admin.directory.orgunit	View and manage organizational units.
admin.directory.customer	View and manage customer-level settings.