Authenticate to Box by using a Control Room managed OAuth2 connection and create a reusable session for later Box actions.

Settings

  • In the OAuth connection field, click Pick to choose from available Control Room-managed OAuth2 credentials.​
    Note: Ensure the OAuth2 connection is valid and active in the Control Room.​
  • Click the Provider type drop-down menu to select an available or custom provider.

    For information in creating a custom provider, see Configure OAuth 2.0 connection in Control Room.

  • In the Connection name field, select the specific OAuth connection object Control Room admin for Microsoft Teams.

    This field is disabled until a Provider type is selected.

  • In the Token type field, select one of the following options depending on the token that will be used at run time.
    • Shared: for a global token.

      An access token of shared type is created when a connection is established to the Control Room. This access token is stored as a credential. When you run your automation, the access token is referenced in the automation using the enterprise application provider type set up in the Control Room.

    • User-specific: for a token that is specific to a user.
      If you select this option, ensure that you log in to your Microsoft Teams account to authenticate and generate a user-specific token. Perform the following steps to use this option:
      1. Log in to Control Room and navigate to My settings > OAuth connections in your profile.
      2. Under the OAuth connections tab, click Login to authenticate.
      3. Sign in to your Microsoft 365 account and select Continue.
      4. Verify the services you have access to and click Continue.

        If the connection is succeeded, it will display the status as Active under the OAuth connections > Connections table.

  • In the Box session field, use one of the following tabs for creating a session:
    • Local session: to specify a session name that can be used only in the current bot.
    • Global session: to specify a session name that can be used across multiple bots, such as parent bots, child bots, and all other child bots of the parent bot.

      Recommendation: The parent and child bots should have the same package version.

    • Variable: to specify a session variable.