> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/global-settings/security/connected-apps/editing-a-connected-app.md). # Editing a Connected App {% hint style="success" %} #### Required User Credentials \[**Flosum User**] - **SystemAdministrator** Role {% endhint %} ## ![](https://579543750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsEk2hU5IMh3HEY5dJZjR%2Fuploads%2FSxcnKlaJKPzDqONWoDNv%2FSummary2-Small-Icon.svg?alt=media\&token=5e3253d0-a069-4ba5-9c06-83c70bd0b21d)Overview A Connected App lets you link your applications to Flosum Cloud Apps using OAuth 2.0 tokens. Once connected, your applications will have access to your users, data, attributes, and other resources. You can manage the connection and authentication settings by editing a Connected App. This article describes each setting available for a Connected App. {% hint style="info" %} For specific instructions on using a Connected App to connect to Flosum's Apps in Salesforce, see the following article. * [Enable Access to Flosum Backup & Archive Data](/global-settings/security/connected-apps/enable-access-to-flosum-backup-and-archive-data.md) {% endhint %} ## Editing A Connected App {% stepper %} {% step %} ### Access Global Settings 1. From any **Flosum Cloud App**, click the **App Switcher** icon at the top of the left sidebar menu.

2. Click **Global Settings**.

3. The **Global Settings** app will open in a new tab. {% hint style="info" %} Global Settings can also be accessed by logging in directly via the Flosum Cloud Apps Login URL. See the following article for login instructions. * [Log In To Global Settings](/global-settings/getting-started/log-in-to-global-settings.md) {% endhint %} {% endstep %} {% step %} ### Select a Connected App 1. Click **Connected Apps** from the sidebar menu. 2. Click the **Name** of the Connected App to edit.

3. Click **Edit**.

{% endstep %} {% step %} ### Basic Information

Setting	Description
Name	The Name field lets you modify the name of the Connected App. This name is specific to your Global Settings tenant, and changing it won't impact your app connections.
Multi-Tenant Mode	Enable the Multi-tenant mode checkbox to grant access to all users, including those from other tenants. Only enable this if you plan to share your service across multiple tenants.
Authentication Flows	The Authentication Flows dropdown lets you choose which flows your app will support. You can select one or more flows, and each is detailed below. `Authorization Code` - In this flow, the client app obtains an authorization code following user authentication at the authorization server. The client app then exchanges this code for an access token, enabling access to protected resources. `Refresh Token` - In this flow, upon successful user authentication and authorization, a Refresh Token is issued alongside the access token. The Refresh Token allows the client app to obtain a new access token after the current one expires, without requiring the user to reauthenticate. This simplifies the token renewal process by eliminating the need for user intervention.
Authorization Scopes	The Authorization Scopes dropdown lets you choose which scopes your app will support. You can select one or more scopes, and each is detailed below. `Offline Access` - This is a special OAuth 2.0 permission that allows a client app to receive updated access tokens without requiring direct user interaction.

{% endstep %} {% step %} ### Authorization Policy

Setting	Description
Refresh Token Lifetime	A Refresh Token Lifetime determines how long a refresh token remains valid, enabling clients to acquire new access tokens without needing user re-authentication.
Access Token Lifetime	An Access Token Lifetime determines how long an access token remains valid, granting clients access to protected resources for that duration before requiring the user to re-authenticate.

{% endstep %} {% step %} ### Authorized URLs

Setting Description

Setting	Description
Allowed Callback URLs	You can add URLs to the list of Allowed Callback URLs that the authorization server redirects the user to after successful authentication and authorization. Example: `https://backup.com/api/v1/oauth/callback`
Allowed Sign-Out URLs	You can add URLs to the list of Allowed Sign-Out URLs that the user can be redirected to after successfully signing out of an app or identity provider. Example: `https://backup.com/api/v1/oauth/login`

Allowed Callback URLs

You can add URLs to the list of Allowed Callback URLs that the authorization server redirects the user to after successful authentication and authorization.

Example: https://backup.com/api/v1/oauth/callback

Allowed Sign-Out URLs

You can add URLs to the list of Allowed Sign-Out URLs that the user can be redirected to after successfully signing out of an app or identity provider.

Example: https://backup.com/api/v1/oauth/login

{% endstep %} {% step %} ### Save Changes 1. Click **Save.**

2. Changes to the Connected App are applied immediately. {% endstep %} {% endstepper %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.flosum.com/global-settings/security/connected-apps/editing-a-connected-app.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.