Dropsuite Users and Accounts - Version 1.2

Overview

The Dropsuite Users and Accounts collector retrieves user and account data from the Dropsuite email backup and archiving platform via its REST API, providing visibility into backup seat usage and protected user accounts across managed organizations.

This collector produces two types of records: one representing the number of backup seats used per organization (with the Product Identifier reflecting whether the organization has archiving enabled), and one representing each individual protected user account within an organization.

The collector retrieves unrated allocation data, meaning no monetary values are supplied by the source system. Pricing and billing calculations are applied within Varibill based on configured contracts and pricing rules.

This is a point-in-time collector, meaning each execution retrieves the current state of users and accounts at the time of collection. The data reflects the active organizations and user accounts present in the Dropsuite platform when the collector runs.

For general instructions on creating and running Source Collectors, see: Configuring a New Cloud Source Collector

Collector Summary

About Dropsuite

Dropsuite is a cloud-based email backup, archiving, and compliance platform that protects business email data across Microsoft 365, Google Workspace, and other email platforms. Dropsuite provides automated daily backups, granular recovery, and long-term archiving with search and eDiscovery capabilities.

Dropsuite’s reseller platform enables managed service providers (MSPs) and resellers to manage email backup and archiving services across multiple customer organizations from a centralized console. The platform provides per-organization visibility into seat usage, archiving status, and protected user accounts.

The Dropsuite API provides programmatic access to user and account data across the managed customer base, enabling resellers to retrieve organization-level seat usage and individual user account details.

Data Collected

The Dropsuite Users and Accounts - Version 1.2 collector retrieves unrated user and account data from the Dropsuite reseller platform. The collector makes two API calls and produces two types of records:

Seats Used (Per Organization)

For each organization (user) returned by the Dropsuite API: - A record representing the number of backup seats currently in use, with a quantity equal to the seats_used value from the API

The Product Identifier for this record is determined by the organization’s archiving status: - If archiving is enabled, the Product Identifier uses the configured Product Identifier Backup And Archive Code - If archiving is not enabled, the Product Identifier uses the configured Product Identifier Backup Code

Protected Users (Per Account)

For each account (individual user) within an organization: - A record with a quantity of 1, representing that the user is protected by Dropsuite

The Product Identifier for this record uses the configured Product Identifier User Code.

The identifiers submitted to Varibill for each record are constructed as follows:

• Client Identifier — the organization’s numeric ID from the Dropsuite API
• Product Identifier — one of the three configured product identifier codes (Backup, Backup And Archive, or User), depending on the record type and archiving status
• Record Identifier — a description of the record: Seats Used - Per user active license utilized for seat records, or The user {email} is protected for account records
• Unique Identifier — the organization’s numeric ID (for seat records) or the account’s numeric ID (for user records)
• Tag — Organization Name: {name} for both record types

Prerequisites

Before configuring this collector, ensure that:

• You have a Dropsuite reseller account with API access
• You have obtained your Dropsuite Access Token and Reseller Token
• You know the Dropsuite API host URL for your region
• You have access to the Varibill Source Collector configuration screen

Configuration Parameters

The parameters below are entered when configuring the collector in Varibill. They are grouped by function.

Connection Parameters

These parameters identify and authenticate against the Dropsuite API using token-based authentication.

Product Identifier Parameters

These parameters define the product codes used to identify each record type in Varibill.

Operational Parameters

These parameters control file management behavior.

Configuration Steps

Step 1: Obtain Your Dropsuite API Credentials

1. Contact your Dropsuite account manager or reseller support to obtain API access.
2. Note the Access Token, Reseller Token, and the API host URL for your region.

Step 2: Configure the Collector in Varibill

1. In the Varibill User Interface, open the Source Collector configuration screen.

2. Enter the required field values under the Details tab:

   • Hosting Provider: Select Varibill Cloud
   • Source Collector Name: Select Dropsuite Users and Accounts - Version 1.2

3. Enter the connection parameters:

   • Dropsuite Host: The Dropsuite API host URL for your region
   • Dropsuite Access Token: The access token from Dropsuite
   • Dropsuite Reseller Token: The reseller token from Dropsuite

4. Configure the product identifier parameters:

   • Product Identifier Backup Code: The code for backup-only seat records (for example, dsBackup)
   • Product Identifier Backup And Archive Code: The code for backup-and-archive seat records (for example, dsBackupAndArchive)
   • Product Identifier User Code: The code for protected user records (for example, dsUser)

5. Save the collector configuration.

Step 3: Run the Collector

Run or schedule the collector according to your standard Source Collector execution process.

For detailed instructions, see: Configuring a New Cloud Source Collector

Troubleshooting

If the collector fails to connect to Dropsuite, verify that:

• The Dropsuite Host URL is correct for your region.
• The Dropsuite Access Token is valid and has not been revoked.
• The Dropsuite Reseller Token is valid and matches your reseller account.
• Your Dropsuite reseller account has API access enabled.

If the collector connects successfully but returns no data, verify that:

• There are active organizations with backup seats provisioned in your Dropsuite reseller account.
• The organizations have users with active accounts.
• Your API credentials have sufficient permissions to access user and account data.

Dropsuite References

The following resources may assist with locating values or configuring your Dropsuite API access.

Dropsuite Documentation (External)

• Dropsuite Website