LightBeam Documentation
Installer GuidesData SourcesPlaybooksInsightsPrivacyOpsGovernance
  • 💡What is LightBeam?
  • 🚀Getting Started
    • ⚙️Installer Guides
      • Pre-Requisites / Security Configurations
        • Firewall Requirements
        • Securing LightBeam on EKS with AWS Certificate Manager on Elastic Load Balancer
        • Configure HTTPS for LightBeam Endpoint FQDN Standalone deployment
        • Using Custom Certificates with LightBeam
        • Securing LightBeam on GKE with Google Certificate Manager and GCE Ingress
      • Core
        • LightBeam Deployment Instructions
        • LightBeam Installer
        • Web App Deployment
        • LightBeam Diagnostics
        • LightBeam Cluster Backup & Restore using Velero
      • Platform Specific
        • AWS
        • Microsoft Azure
        • Google Cloud (GKE)
        • Standalone Virtual Machine
        • Deployment on an Existing Managed Kubernetes Cluster
        • Azure Marketplace Deployment
      • Integration and Setup
        • Setting Up AWS PrivateLink for RDS-EKS Interaction
        • Twingate and LightBeam Integration Guide
        • Data Subject Request Web Application Server
        • Generate CSR for LightBeam
  • 🧠Core Features
    • 🔦Spectra AI
      • 🔗Data Sources
        • Cloud Platforms
          • AWS Auto Discovery
          • GCP Auto Discovery
        • Databases and Datalakes
          • PostgreSQL
          • Aurora (PostgreSQL)
          • Snowflake
          • MS SQL
          • MySQL
          • Aurora (MySQL)
          • BigQuery
          • AWS Redshift
          • Oracle
          • DynamoDB
          • MongoDB
          • CosmosDB (PostgreSQL)
          • CosmosDB (MongoDB)
          • CosmosDB (NoSQL)
          • Looker
          • AWS Glue
          • Databricks
          • SAP HANA
          • CSV Files as a Datasource
        • Messaging
          • Gmail
          • Slack
          • MS Teams
          • MS Outlook
        • Developer Tools
          • Zendesk
          • ServiceNow
          • Jira
          • GitHub
          • Confluence
        • File Repositories
          • NetDocuments
          • AWS S3
          • Azure Blob
          • Google Drive
          • OneDrive
          • SharePoint
          • Viva Engage
          • Dropbox
          • Box
          • SMB
        • CRM
          • Hubspot
          • Salesforce
          • Automated Data Processing (ADP)
          • Marketo
          • Iterable
          • MS Dynamics 365 Sales
          • Salesforce Marketing Cloud
      • 🔔PlayBooks
        • What is LightBeam Playbooks?
        • Policy and Alerts
          • Types of Policies
          • How to create a rule set
            • File Extension Filter
          • Configuring Retention Policies
          • Viewing Alerts
          • Sub Alerts
            • Reassigning Sub-Alerts
            • Sub-alert States
          • Levels of Actions on Alerts
          • User Roles and Permissions
            • Admin View
            • Alert Owner View
            • Onboarding New Users
              • User Management
              • Okta Integration
              • Alert Assignment Settings
              • Email Notifications
            • Planned Enhancements
          • Audit Logs
          • No Scan List
          • Permit List
          • Policy in read-only mode
      • 📊Insights
        • Entity Workflow
        • Document Classification
        • Attribute Management Overview
          • Attributes Page View
          • Attribute Sets
          • Creating Custom Attribute
          • Attributes List
        • Template Builder
        • Label Management
          • MIP Integration
          • Google Labels Integration
      • 🗃️Reporting
        • Delta Reporting
        • Executive Report
        • LightBeam Lens
      • Scanning and Redaction of Files
        • On-demand scanning
      • How-to Guides
        • Leveraging LightBeam insights for structured data sources
      • LightBeam Dashboard Outlay
      • Risk Score
    • 🏛️PrivacyOps
      • Data Subject Request (DSR)
        • What is DSR?
        • Accessing the DSR Module
        • DSR Form Builder (DPO View)
          • Creating a New DSR Form
            • Using a Predefined Template
            • Creating a Custom Form
          • Form Configuration
          • Form Preview and Publishing
          • Multi-Form Management
          • Messaging Templates
        • Form Submission & Email Verification (Data Subject View)
        • DSR Management Dashboard (DPO View)
        • Processing DSR Requests
          • Data Protection Officer (DPO) Workflow
          • Self Service Workflow (Direct Validation)
          • Data Source Owner (DSO) Workflow
        • DSR Report
      • 🚧Consent Management
        • Overview
        • Consent Logs
        • Preference Centre
        • Settings
      • 🍪Cookie Consent
        • Dashboard
        • Banners
        • Domains
        • Settings
        • CMP Deployment Guide for Google Tag Manager
        • FAQs
      • 🔏Privacy Impact Assessment (PIA)
        • PIA Templates
        • PIA Assessment Workflow
        • Collaborator View
        • Process Owner Login View (With Collaborator)
        • Filling questionnaire without collaborator
        • Submitting the assessment for DPO review
        • DPO review process
        • Marking the assessment as reviewed
        • Editing and resubmitting assessments after DPO review
        • Revoke review request
        • Edit Reviewer
        • PIA Reports
      • ⏺️Records of Processing Activity (RoPA)
        • Creating a RoPA Template
          • How to clone a template
          • How to use a template
        • How to create a process
          • Adding Process Details
          • Adding Data Elements
          • Adding Data Subjects
          • Adding Data Retention
          • Adding Safeguards
          • Adding Transfers
          • Adding a Custom Section
          • Setting a Review Schedule
          • Data Flow Diagram
        • How to add a collaborator
        • Overview Section
        • Generating a RoPA Report Using LightBeam
        • Collaborator working on a ticket
    • 🛡️Governance
      • Access
        • Dashboard
        • Users
        • Groups
        • Objects
        • Active Directory Settings
        • Access Governance at a Data Source Level
        • Policies and Alerting
        • Access Governance Statistics
        • Governance Module Dashboard
      • Privacy At Partners
  • 📊Tools & Resources
    • 🔀API Documentation
      • API to Create Reports for Structured Datasource
    • ❓Onboarding Assessments
      • Structured Datasource Onboarding Questionnaire
        • MongoDB/CosmosDB Questionnaire
        • Oracle Datasource Questionnaire
      • SMB Questionnaire
    • 🛠️Administration
      • Audit Logs
      • SMTP
        • Basic and oAuth Configuration
      • User Management
        • SAML Identity Providers
          • Okta
            • LightBeam Okta SAML Configuration Guide
          • Azure
            • Azure AD SAML Configuration for LightBeam
          • Google
            • Google IDP
        • Local User Management
          • Adding a User to the LightBeam Dashboard
          • Reset Default Admin Password
  • 📚Support & Reference
    • 📅Release Notes
      • LightBeam v2.2.0
      • Reporting Release Notes
      • Q1 2024 Key Enhancements
      • Q2 2024 Key Enhancements
      • Q3 2024 Key Enhancements
      • Q4 2024 Key Enhancements
    • 📖Glossary
Powered by GitBook
On this page
  • 1. Introduction to Google Labels
  • 2. Google Labels Overview
  • 3. LightBeam Integration with Google Labels
  • 4. Onboarding Google Labels
  • 5. Google Labels Integration Configuration
  • 6. Creating Policies with Google Labels
  • 7. Viewing and Filtering Google Labels
  • 8. Service Account and Permissions
  • 9. Important Considerations and Limitations
  • About LightBeam
  1. Core Features
  2. Spectra AI
  3. Insights
  4. Label Management

Google Labels Integration

PreviousMIP IntegrationNextReporting

Last updated 10 months ago


1. Introduction to Google Labels

Google Labels is a feature in Google Workspace that allows organizations to classify and categorize their documents and files. LightBeam Spectra now supports integration with Google Labels, enabling users to leverage these classifications within the LightBeam ecosystem.

2. Google Labels Overview

2.1 Types of Labels

Google Labels consist of two primary types:

  1. Badged Label:

    • A badged label is the most critical label that your entire organization can use, and there's a restriction allowing only one badged label for the entire organization.

    • It appears at the top of a file when opened.

    • It contains a single field of selection type.

  2. Standard Labels:

    • Standard labels are either simple or descriptive labels that have structured fields added to them.

    • A simple label could be a tag, such as Client Name. Once created in the Label Manager, you can apply this simple label.

    • A more complex, structured label could be Content Status, which includes fields like Assigned to, Due Date, and Status.

    • There can be multiple standard labels used by an organization.

Important: In cases where an organization has multiple Google Workspace domains or uses multiple service accounts, each label set will be onboarded using separate service accounts. This approach ensures that label sets from different domains or organizational units are properly segregated and managed within LightBeam. When onboarding label sets from multiple domains, you'll need to repeat this process for each service account, using the appropriate credentials for each.

2.2 Label Structure

Labels in Google are structured like forms with multiple fields:

  • Field types include: integer, string, user, date, single selection, multiple selection

  • Example fields for a standard label:

    • Client (User type)

    • Department (Selection type)

    • Due Date (Date type)

    • Status (Selection type)

Note: While standard labels can have multiple fields of various types, only fields with single selection options are used to create label sets in LightBeam.

2.3 Label Priority

In Google Labels, lower numbers indicate higher priority. This is crucial for automated policy application.

3. LightBeam Integration with Google Labels

3.1 Label Set Creation

  • LightBeam creates a label set for each Google label field with single selection options.

  • The choices in the Google label field become individual labels within the LightBeam label set.

  • Multiple label sets may be created from a single Google Label if it has multiple qualifying fields.

    For example, if a Google Label named "Contract" has a field called "Department" with options like "Finance," "Legal," and "HR," LightBeam will create a label set named "Contract_Department" with labels for each of these options.

3.2 Priority Mapping

LightBeam reverses the priority mapping to maintain consistency with its interface:

  • Google Labels: Lower number = Higher priority

  • LightBeam: Higher number = Higher priority

  • For example, if a Google Label has options numbered , with 1 being the highest priority, LightBeam will display these as priorities , with 4 being the highest priority.


4. Onboarding Google Labels

4.1 Accessing the Integration

To begin the onboarding process for Google Labels:

  1. In the LightBeam console, click on the INSIGHTS header in the top navigation menu.

  1. In the left sidebar, click on Label Management.

  1. On the Label Management page, click on “3rd-party Integration”.

  1. Select "Google" from the dropdown menu of available integrations.

4.2 Configuring the Integration

During the onboarding process, you will need to:

  1. Provide a prefix for naming the label sets. This prefix will be used to create unique names for each label set derived from Google Labels.

  2. Click on Next.

Enter the necessary credentials for accessing your Google Workspace account. This includes:

  • Delegated Credentials

  • Account JSON

Click on Test Connection.

Once the Test Connection is successful, click on Onboard Label Set.

Click on Okay.

Once the connection is established, Lightbeam synchronizes the labels from Google Labels. Users can review the synchronized labels and their associated Lightbeam labels in the Label Management interface.

LightBeam uses a standardized naming convention for label sets created from Google Labels:

[Prefix][Google Label Name][Field Name]

For example, if you provide the prefix "GLS" and have a Google Label named "Contract" with a field "Department," the resulting label set in LightBeam would be named "GLS_Contract_Department."

This naming convention helps to organize and identify the source of each label set within the LightBeam system.

Note: When entering the credentials for your Google Workspace account, ensure that the service account you're using has all the necessary permissions as outlined in section 8.1 of this document. Additionally, verify that the Drive Labels API has been enabled for this service account. These permissions and API access are crucial for the proper functioning of the Google Labels integration with LightBeam.

5. Google Labels Integration Configuration

  • Locate the label sets with the prefix you specified during onboarding.

  • Click on a label set to view its details.

Click View Details.

5.2 Editing Label Definitions

  • Users can provide or edit definitions for Google labels in Lightbeam.

  • Label Name and Priority cannot be modified as they come from Google.

Click on Select Atttribute to edit the field.

Select all Attributes that are applicable.

Click Save.

6. Creating Policies with Google Labels

To create a labeling policy using Google Labels:

  1. Navigate to the Policies section in LightBeam Spectra.

  2. Click "Create New" within "Labeling Policy."

Enter a Rule Set Name such a Google Labeling.

Choose a Rule Set Criteria and then click on Next.

After selecting the necessary Datasources, click on Save & Close.

If a rule set has been already created in the Policies page, you can proceed with selecting the Google Labeling policy.

In the policy creation interface, you can now directly select Google label sets.

Click on Save & Close.

Once the policy is active, LightBeam will apply the Google Labels based on the conditions specified in your policy.


7. Viewing and Filtering Google Labels

7.1 Labels Tab Overview

The Labels tab in LightBeam provides an overview of all labels, including those from Google:

  • Displays cards for each label, including those from Google

  • Shows label name and number of labeled objects

  • Enhanced performance for quicker loading

7.3 Object Viewer Label Display

When viewing individual objects:

  1. Open an object's details page.

  2. In the metadata section, you'll see any Google Labels applied to the object.

  3. These labels are displayed alongside any other LightBeam or third-party labels.

7.4 Filtering Objects by Labels

You can use Google Labels to filter objects in LightBeam:

  1. Click on the object to go to the Object Viewer.

  2. Use the filter options to select labels, including those from Google.

  3. The view will update to show only objects with the selected labels.

  4. Users can filter objects based on Google labels in the third-party label sets.

  • It will show third party label sets, but because they are not supported from the UI, it will be greyed out. LightBeam label sets can be updated from here


8. Service Account and Permissions

8.1 Required Permissions

To integrate Google Labels with LightBeam, ensure your Google Workspace service account has the following permissions:

  • For label modification, one of the following:

    • https://www.googleapis.com/auth/drive

    • https://www.googleapis.com/auth/drive.file

    • https://www.googleapis.com/auth/drive.metadata

  • For listing labels, one of the following OAuth scopes:

    • https://www.googleapis.com/auth/drive.labels

    • https://www.googleapis.com/auth/drive.labels.readonly

    • https://www.googleapis.com/auth/drive.admin.labels

    • https://www.googleapis.com/auth/drive.admin.labels.readonly

Additionally, ensure that the "Drive Labels API" is enabled for the service account.

8.2 Service Account Configuration

You have two options for configuring the service account:

  1. Use the same service account as your Google Drive integration:

    • Add the required permissions for Google Labels to your existing Drive service account.

    • Ensure the Drive Labels API is enabled for this service account.

  2. Create a separate service account for Labels:

    • Set up a new service account with the necessary permissions for both Drive and Labels.

    • Ensure the Drive Labels API is enabled for this service account.

For both options, make sure to include the permissions listed in section 8.1.

Consult your Google Workspace administrator to ensure the correct permissions are applied and the necessary API is enabled.


9. Important Considerations and Limitations

9.1 Metadata Nature of Google Labels

Unlike some other labeling systems, Google Labels are metadata that reside in Google's systems:

  • Labels do not travel with the document if it's downloaded.

  • If a labeled file is downloaded and re-uploaded, it will lose its label.

9.2 Synchronization Limitations

Currently, there is no automatic synchronization between Google Labels and LightBeam:

  • Changes made to labels in Google after onboarding are not automatically reflected in LightBeam.

  • Regular re-onboarding may be necessary to keep labels up to date.

9.3 Snapshot-based Functionality

LightBeam's integration with Google Labels operates on a snapshot basis:

  • The label structure and definitions are captured at the time of onboarding.

  • Subsequent changes in Google Labels are not automatically propagated to LightBeam.

9.4 Permission and API Requirements

  • The integration between LightBeam and Google Labels requires specific permissions and API access.

  • Ensure that the service account used for integration has all necessary permissions as outlined in section 8.1.

  • The Drive Labels API must be enabled for the service account for the integration to function properly.

  • Regularly review and update permissions as needed to maintain the integration's functionality.

By leveraging LightBeam's integration with Google Labels, organizations can extend their labeling and classification capabilities beyond Google's native functionality, providing a more comprehensive data governance solution


About LightBeam

LightBeam automates Privacy, Security, and AI Governance, so businesses can accelerate their growth in new markets. Leveraging generative AI, LightBeam has rapidly gained customers’ trust by pioneering a unique privacy-centric and automation-first approach to security. Unlike siloed solutions, LightBeam ties together sensitive data cataloging, control, and compliance across structured and unstructured data applications providing 360-visibility, redaction, self-service DSRs, and automated ROPA reporting ensuring ultimate protection against ransomware and accidental exposures while meeting data privacy obligations efficiently. LightBeam is on a mission to create a secure privacy-first world helping customers automate compliance against a patchwork of existing and emerging regulations.

You can click on View/Update option to update the Rule Set Criteria or Data Sources.

For any questions or suggestions, please get in touch with us at: .

🧠
🔦
📊
✏️
support@lightbeam.ai
Figure 1: Types of Labels
Figure 2: Google Label priority settings
Figure 3: Click on INSIGHTS header
Figure 4: Label Management sidebar
Figure 16: 3rd-party Integration button