Before you enable the Box-Jive connection, you'll need to set up a Box integration
user on the Box side that can post information to Box on behalf of Jive. This user will be
used to create the connection to Jive.
The Box Integration User exists only for the integration, and should never be used
for any other actions. It should never be logged in for any reason as either a
Box user or a Jive user. In the Box admin console, make sure you have enabled
auto-accept for the enterprise. This user needs to be provisioned to handle
unlimited storage, or at the highest level possible.
Note: Other Box Enterprise Admins will have access to this user: you should ensure that they don't change the settings.
To set up the Box integration user on the Box side:
Log in as the Box enterprise administrator.
In Box, browse to Admin Console > Users.
Create a Box user named Box Integration User. Make sure that Storage allocation (GB) is set to Unlimited. If that isn't possible, set it to the maximum allowed storage allocation.
Click Add User.
Select the newly created Box Integration User.
Under Edit User Access permissions > Co-Admin, make sure the User is granted administrative
privileges check box is selected.
Under User is granted administrative privileges , make sure you also select the following check boxes: Manage users, Manage groups, Log in to users' accounts, and Run new reports and access existing reports.
Log out and log in again as Box Integration User.
Browse to Account Settings.
On the Account tab, make sure that Account Information - Account type is set to Enterprise.
Navigate to the Content and Sharing tab and modify your settings as
Set Enable external links to Nothing, restrict sharing.
Set Let link viewers to Preview and download the shared item.
Navigate to Collaborating on Content > Incoming Invitations and make sure the Automatically accept
incoming collaboration invitations check box is checked.
This ensures that as soon as a user joins the Jive group, the user is
also added as a collaborator to the linked Box folder without needing to
take further action.
Note: If you're using an SSO solution such as Okta with Box, make sure the integration user is defined as an admin. Otherwise, the IdP could remove the integration user's administrative privileges from Box, breaking the integration.