Applying for and Enabling the Box for G Suite Integration

The Box for G Suite integration provides access to Google Suite’s complete array of content creation features – creating, modifying, and auto-saving documents in Google Docs, Sheets, or Slides – seamlessly, from directly within Box. 


There are several significant improvements in this integration, compared to the earlier Box-Google integration: 


  1. First and foremost, using Box for G Suite now essentially bypasses Google Drive. You can create, edit, and save Google documents all from within Box as the secure content layer.  In the earlier integration, G Suite created a copy of your file in Google Drive, which created security risks and user confusion.
  2. You can now work with Slides as well as Docs and Sheets. Slides was unavailable in the earlier integration.
  3. You cannot connect your personal G Drive to Box; you must have paid enterprise accounts in both Box and Google to connect them. (This is a significant security enhancement.)

As an admin, you must complete two tasks:

  1. Sign your organization up for the Box for G Suite integration beta by completing 3 forms
  2. Enable the integration for your organization on your assigned day.


1.  Signing up for the Integration Beta

To be eligible for this beta program, your organization:

  • must have a paid G Suite enterprise account (any paid G Suite SKU)
  • must deploy the integration for the entire enterprise (that is, not limited to specific groups or individual users)  

You can deploy in either a production or a sandbox environment, but the Box and G Suite user logins must match – for example. if the Box login is, the G Suite login/alias must also be  Also, only admins or co-admins with specific permission to edit enterprise settings can sign their enterprise up for the beta.


To sign up for the Box for G Suite integration:

  1. From your Admin Console, in the lefthand navigation, click Enterprise Settings.
  2. When the Enterprise Settings page displays, in the top navigation click Apps.
  3. In the Productivity Integrations section, toward the bottom, click Sign up for Box & G Suite Public Beta.
Admin console -- sign up for G Suite beta.png


  1. At the prompt, accept the Box terms and conditions (this completes one form) and click Next.
  2. Follow the prompts to complete two additional forms.
  3. When you have completed all 3 forms, click I certify I have completed all agreements, and then click Submit Request.
Submit beta request.png
  1. Wait until the next beta enablement period opens. (You cannot enable the beta at any time after signup. You can only enable on designated signup dates).

IMPORTANT   Box needs to ensure each cohort has the desired mix of organizations (number, size, and so on).  As a result, signing up for the beta does not guarantee acceptance.  Even when you're accepted it's possible you may not be admitted into the next available cohort date, but instead must wait for a later date.


Sign up for the beta on or before this date…

…and if you are approved, enable the beta on this date:

September 18

September 26

October 2

October 10

October 9

October 17

October 23

October 31


During your waiting period, Box approves your enterprise ID (EID) number and Google approves your G Suite domain.  Approval is not guaranteed; the Box and Google product teams vet applicants to ensure a balance of cohort sizes and also that the system can scale efficiently.

IMPORTANT   We are unable to notify beta applicants directly whether they’ve been accepted into the beta program.  If you’ve been accepted, a check box displays in your admin console, on the Enterprise Settings page, on the next enablement date.  Check this check box to enable the G suite beta.


2.   Installing and enabling G Suite for your organization

When your beta enablement date arrives, you can turn on the beta for your entire organization via a new option in your Admin Console.


To install and enable the G Suite integration

  1. From your admin console, in the lefthand navigation, click Enterprise Settings. The Enterprise Settings page displays.
  2. In the top navigation, click Apps. Scroll down to the G Suite beta section.
  3. Check Enable Box for G Suite. (If you do not see this option, then most likely you have not been accepted into the beta program. Please contact your Customer Success Manager.)

The G Suite integration is now on for everyone in your organization.  You can also set G Suite as the default editing suite for your entire enterprise.


To set G Suite as the default editing suite for MS Office files in your organization

  1. From your admin console, in the lefthand navigation, click Enterprise Settings.  The Enterprise Settings page displays.
  2. In the top navigation, click Apps.  Scroll down to the Default editors section.
  3. Click Default Editor for Opening Office Files, and in the menu that displays click Google docs.

Any managed user in your Box Enterprise can override this enterprise-wide setting on an individual basis.  To do this, a managed user can go to his or her Account Settings page and then click Integrations.

Note   The Google editor saves a new version of the file being edited in the Google Docs / Sheets / Slides editors back to Box at least every three minutes, as well as one final save when the editing session ends.


Moving existing files from Google (G Drive) into Box

Box provides migration services via Box Shuttle partners.  However, this method downloads all Google files as Office files, and then re-uploads those into Box, which results in the loss of Google file formats.


As of Q3 2018, you cannot migrate Google doc file formats directly into Box. 


Box for G Suite and mobile devices

You can preview Docs, Sheets, and Slides on mobile devices.  However, as of Q3 2018, you cannot edit or open these files in Google editors.



Please help us improve the G Suite integration by providing your feedback about the experience.  Please -- be as descriptive and honest as possible.  We really do value, and very much want, your input.



For technical support, please visit


Related Links

Version history
Revision #:
12 of 12
Last update:
‎10-01-2018 12:32 PM
Updated by:

More in this guide:

Go to Guide