Removed mentions of implicit grant

docs/basics/api-index.md

@@ -9855,7 +9855,7 @@ In case the feature is available for the current user, <code>"available": true</
 	      <td class="t">string</td>
 	      <td class="d"></td>
 	      <td class="r">True</td>
-	      <td class="de">Determines authorization flow: **code** - Authorization Code, **token** - Implicit Grant</td>
+	      <td class="de">Determines authorization flow: **code** - Authorization Code</td>
             </tr>
 <tr>
 	      <td class="n">scope</td>

docs/basics/your-first-steps.md

@@ -61,12 +61,16 @@ Selecting permissions you may not actually need can impede access to production
 
 ## Choosing the right authentication scheme
 
-RingCentral supports a number of authentication schemes depending upon the type of app you are creating. The authentication schemes available to your app will depend largely upon the following:
+**Does your app have a user interface, and will each of your users need to connect to RingCentral?**
 
-* **Platform Type** - different types of apps will have different technical requirements for auth, for example "browser-based apps" have access to Implicit Grant flows which other apps do not, and password-based auth is only allowed for "Server/No UI" apps. 
+If the users of your app will need to independently log into RingCentral, then the best auth method for you is the [Auth Code with PKCE Flow](./auth-code-pkce-flow). However, some apps may elect to use the simpler, older and less secure [Auth Code Flow](./auth-code-flow).
 
-!!! hint "Recommended Auth Scheme: OAuth"
-    The vast majority of applications on RingCentral should be using the [3-legged authentication auth code flow](../../authentication/auth-code-flow/) as it is the most secure and conforms to Internet best practices with regards to authorization, transparency and security. 
+!!! hint "Use refresh tokens"
+    When the auth code flow is used to obtain an access token for a specific user, it is highly recommended that you also implement the [refresh flow](./refresh-tokens/) in order to keep access tokens fresh and valid. If you do not, they will eventually expire, and your users will be required to re-authenticate via a user interface. 
+
+**Does your app lack a user interface, and/or does it act on behalf of all users within an organization?**
+
+Apps that lack a user interface, or are run from the command line are typically utility apps that act on behalf of all users within an organization simultaneously. These apps often utilize a "service user" account that possesses administrative priveleges that allow it to act on behalf of all or any user in the organization. For these types of apps, we recommend the [JWT auth flow](./jwt-flow/).
 
 [Learn more about Authentication on RingCentral »](../../authentication/)
 

tutorials.json

@@ -245,24 +245,6 @@
             }
         ]
     },
-    {
-        "title": "OAuth Implicit Grant Flow in web page",
-        "description": "<p>In this tutorial, you will learn how to use RingCentral OAuth Implicit grant flow in web page with javascript SDK by a quick demo.</p>",
-        "tags": [
-            "Auth"
-        ],
-        "defaults": {
-            "githubUri": "https://github.com/ringcentral-tutorials/oauth-implicit-js-demo",
-            "tutorialUri": "https://ringcentral-tutorials.github.io/oauth-implicit-js-demo/"
-        },
-        "languages": [
-            {
-                "name": "JavaScript",
-                "githubUri": "https://github.com/ringcentral-tutorials/oauth-implicit-js-demo",
-                "tutorialUri": "https://ringcentral-tutorials.github.io/oauth-implicit-js-demo/"
-            }
-        ]
-    },
     {
         "title": "Call Log Visualization",
         "description": "<p>In this tutorial, you will learn how to access your RingCentral call log database by using the call-log API and the RingCentral Node JS SDK. You will learn how to parse the response, process the data and display the information on Google charts.</p>",