Bitrix24 Self-hosted administration

This limit works as follows:

A unique pair of User+Document is registered. There can be no more than 10 of such unique pairs.

A user receives the message on reaching the limit when attempting to open any document, if, for example:

• Single user have already opened 10 various documents.
• 10 various users has opened a single document.
• Five users have opened a single document and simultaneously the same 5 users have opened another document.

When users exit the document or when document is closed, the limit is reset.

To avoid critical errors (for example, when customer account responded incorrectly to Bitrix24.Docs queries after opening a document), current session is automatically closed after 8-hour period.

One of the advantages of Bitrix24 Self-hosted (Difference between Cloud & Self-hosted (On-Premise)) is the option to install a hoster on the selected server or in the local intranet. However, Google Docs - is an online server (cloud service, SaaS). It is available from the Internet, that's why its security policy is continuously corrected and becomes more stringent. Due to this, you can receive a request for verification of your application (Bitrix24 account) when configuring external authorization.

There are two options for resolving this situation:

• Variant 1. You may skip verification procedure. Then, each time you'll have to go via the link Additional settings and grant permission for access.
• Variant 2. Verify your application. The following is required:
  • complete the verification at the tab OAuth consent screen. Indicate your application (Bitrix24 account) data inside the form - name, logo, techsupport URL.
  • Always indicate Scopes API Google.
  • List of scopes.
    It's recommended to include the following scopes (See Full list of Google scopes):

    - https://www.googleapis.com/auth/userinfo.email and https://www.googleapis.com/auth/userinfo.profile - used for basic authentication and Google account association with Bitrix24 account

    - https://www.googleapis.com/auth/calendar - used for Bitrix24 calendar integration with Google Calendar

    - https://www.googleapis.com/auth/drive - used for uploading Google Drive files to Bitrix24 and for editing Bitrix24 documents in Google Docs.

    - https://mail.google.com/ и email - used for handling email web interface inside Bitrix24.

  • Even if you aren't using the abovelisted features and options at the Bitrix24 On premise account, it's recommended to indicate all options to avoid repeated verification. In case you have your own custom Google API-based extras for Bitrix24 On-premise, they must be included and described in this list as well.
  • After the from was completed, please wait for the Google tech support response. It usually takes 2-3 business days. Google tech support can send you instructions about what must be modified or configured at the site to enable use of your OAuth-application.
    
    

    Example of Google tech support manual

    Dear Developer, Thank you for submitting an OAuth App Verification request. It appears that your homepage URL https://mysite.com/ is a login screen, which restricts public access to your app's information and intent. Google requires that your homepage accurately represents your app’s identity to users. If your app requires a log in, we recommend that you place the limited access sign-in procedure on a separate web page. If your app is meant to be available to the public, please make sure that your app’s homepage URL features content associated with your brand, accurately represents your true identity, and clearly describes the functionality of your app. If you need to update the homepage URL linked to your OAuth Consent Screen, you can do the following: Sign-in to Google Cloud Console Select the project ID: my_site_com Go to Credentials on OAuth consent screen Enter the homepage URL Click Submit If your app is meant to be internal, please let us know by replying to this email. We will then close your case so that you are able to update your project from public to internal. To update your project fr om public to internal: Sign-in to Google Cloud Console Select the project ID: my_site_com Go to Credentials on OAuth consent screen Go to Application Type Select Internal Click Save In addition, you will need to associate your project with your organization: If you have not already done so, create an Organization by following the Quickstart Using Organizations instructions. Migrate the project into the organization you created as shown in Migrating Existing Projects into the Organization. Once you have associated your project with your organization, you and the project users in your organization can use the app to directly access OAuth scopes. No verification will be required. Please reply to this email once you have made the appropriate updates to your site and/or your OAuth Consent Screen so that we may continue with the verification process. Note that any new email sent to api-oauth-dev-verification@google.com will not be received by our team. You can find more information in the OAuth Application Verification FAQ. If you have additional questions, please respond to this email.

  • If Google tech support start strongly require to transition from the scope https://mail.google.com/ to https://www.googleapis.com/auth/gmail.readonly, you can respond that such option is unavailable to you, because web interface operates using IMAP protocol only, which requires token with scope https://mail.google.com/.
  • After confirmation all must be operational; however, a repeated verification may be required in the future, if Google will update the app settings, or if Bitrix24 will issue new Google integration features. That's why it's better to save data for completed form, to avoid composing them again in the future.

Option Activate document editing via external services (Google Docs, MS Office Web Apps and others) located in the Document Library module settings (Settings > System Settings > Module Settings > Document Library).