Cloudability SaaS Connect Dropbox to Cloudability SaaS

What data is used by Cloudability SaaS from Dropbox?

Dropbox is integrated with Cloudability SaaS using the Dropbox API.

For more information, refer to https://www.dropbox.com/developers/documentation/http/documentation .

Cloudability SaaS uses user and expense data from the Dropbox API. The data is analyzed and displayed as useful insights in Cloudability SaaS .

The list of fields that are retrieved by the connector can be quite long and detailed. It's therefore in a drop-down so that it's easier to read through this intro if you're not wanting the detail:

View the data fields that are used by Cloudability SaaS from Dropbox

Cloudability SaaS uses six API calls to retrieve data from Dropbox.

users/get_current_account

For more information, refer to https://www.dropbox.com/developers/documentation/http/documentation#users-get_current_account

The following retrieved fields are used by Cloudability SaaS :

account_id

name

given_name

surname

familiar_name

display_name

abbreviated_name

email

email_verified

disabled

locale

referral_link

is_paired

account_type

country

team

id

name

sharing_policies

shared_folder_member_policy

shared_folder_join_policy

shared_link_create_policy

office_addin_policy

team_member_id

team_log/get_events

For more information, refer to https://www.dropbox.com/developers/documentation/http/teams#team_log-get_events

The following retrieved fields are used by Cloudability SaaS :

events

timestamp

event_type

tag

description

details

shared_content_download_details

shared_content_link

shared_content_access_level

shared_content_owner.tag

shared_content_owner.account_id

shared_content_owner.email

actor

actor.user (tag, account_id, display_name, email)

involve_non_team_member (context)

account_id

display_name

email

team_member_id

member_external_id

team.display_name

cursor

has_more

team_log/get_events/continue

For more information, refer to https://www.dropbox.com/developers/documentation/http/teams#team_log-get_events-continue

The following retrieved fields are used by Cloudability SaaS :

events

timestamp

event_type

tag

description

details

shared_content_download_details

shared_content_link

shared_content_access_level

shared_content_owner.tag

shared_content_owner.account_id

shared_content_owner.email

actor

actor.user ( tag , account_id , display_name , email )

involve_non_team_member ( context )

account_id

display_name

email

team_member_id

member_external_id

team.display_name

cursor

has_more

groups/members/list

For more information, refer to https://www.dropbox.com/developers/documentation/http/teams#team-groups-members-list

The following retrieved fields are used by Cloudability SaaS :

members

cursor

has_more

data point

team_member_id

email

email_verified

status

name

membership_type

external_id

account_id

joined_on

groups/members/list/continue

For more information, refer to https://www.dropbox.com/developers/documentation/http/teams#team-groups-members-list-continue

The following retrieved fields are used by Cloudability SaaS :

members

cursor

has_more

data point

team_member_id

email

email_verified

status

name

membership_type

external_id

account_id

joined_on

oauth2/token

For more information, refer to https://www.dropbox.com/developers/documentation/http/documentation

The following retrieved fields are used by Cloudability SaaS :

access_token

token_type

scope

account_id

Calculated fields

Last login date

The last login date is set for a user based on the timestamp value returned from the team_log-get_events and team_log-get_events-continue API calls

If there is information under the actor in the response then the timestamp value is set as the last login date for that user.

If there is no information under actor then the user is identified by the email address value within details if the response. The timestamp value is set as the last login date for that the associated user

If there are no events related to a user then the date is set to null.

Activity status

The last login date is used to determine when the user was last active; see Last login date .

If there is no last login date, then the user is marked as inactive.

Purchased license count

This value is set manually.

Used license count

The used license count is based on the number of users found.

Connect to Dropbox

Before you start

Prerequisites, supported versions, , decisions you need to make (might XREFto a "best practice" topic or HREF to Community page)

Before you can integrate Dropbox with Cloudability SaaS , you must have the following:

An Administrator account on, at a minimum, a Standard Business account subscription.

For more information, refer to https://www.dropbox.com/business/plans-comparison.

The account must have Team admin or Security admin rights.

For more information, refer to https://help.dropbox.com/teams-admins/admin/change-admin-rights .

Steps to connect

Connect Dropbox to Cloudability SaaS .

Find the Dropbox tile and select Connect .

Login to Dropbox.

Select Continue .

Complete the steps in the License Wizard to add your Dropbox license to Cloudability SaaS .

Confirm success

Use the wording below as a guide when describing a single connector. For example, a single application connected using an API connection.

Confirm that Dropbox has been integrated with Cloudability SaaS correctly.

Confirm that the Cloudability SaaS Dashboard displays the Dropbox tile under Your Connected Applications .

Select the Dropbox tile and confirm that data from Dropbox can be viewed in the application details page.

Compare the data in Dropbox to data in Cloudability SaaS to confirm success.

Log into Dropbox.

Navigate to your team directory. Refer to https://help.dropbox.com/files-folders/share/team-directory for more information.

Use the list of Members to compare to the list of users that are in the Cloudability SaaS connected application.

Troubleshooting

Troubleshooting questions can be listed here using the drop-down. Copy the following Madcap dropdown and replace the text for each common issue.

Common Issue short description

Common issue longer description (if required)

Issue solution or workaround