Connected App
Overview
Connected App — Business Overview
Connected App is used to formally register and manage external applications that need to securely interact with Dafater. From a business perspective, it acts as a controlled gateway that allows approved third-party tools—such as payment providers, reporting platforms, mobile apps, or partner systems—to exchange data with Dafater in a safe and accountable way.
It ensures that only trusted applications can access business data, and only for approved purposes.
Purpose in Business Operations
The Connected App document helps organizations:
- Enable integration with external systems without manual data entry
- Maintain control over which apps can access business information
- Support digital automation and partner collaboration
- Improve efficiency by allowing systems to “talk to each other” securely
In short, it supports growth, automation, and digital transformation while maintaining governance and oversight.
Prerequisites and Setup Requirements
Before using Connected App, businesses should ensure:
- A clear business need for integrating with an external application
- Management approval for data sharing with that application
- Defined scope of what information the external app is allowed to use
- Identified internal owner responsible for the connected application
This preparation ensures integrations are intentional, secure, and aligned with business goals.
Typical Workflow and Business Process Fit
Identify Integration Need
A department (finance, operations, sales, etc.) identifies the need to connect Dafater with an external system.Create Connected App Record
The business registers the external application in Dafater using Connected App, defining its purpose and access level.Review and Approval
Authorized users review the request to ensure it complies with company policies and data governance rules.Activate the Connection
Once approved, the Connected App becomes active and can exchange data as defined.Ongoing Monitoring
The app’s usage and relevance are periodically reviewed to ensure it still serves a valid business purpose.
This workflow ensures integrations are structured, approved, and auditable.
Key Business Scenarios Where Connected App Is Essential
Payment and Banking Integrations
Allowing external payment platforms to update transaction statuses in Dafater.Mobile or Customer Portals
Enabling customer-facing apps to securely view or submit information.Reporting and Analytics Tools
Connecting business intelligence tools for automated reporting.Partner or Vendor Systems
Allowing controlled data exchange with logistics providers, insurers, or service partners.Automation and Digital Services
Supporting modern digital services that depend on real-time data flow.
Important Considerations for Users
Data Responsibility
Only grant access that is truly required—avoid overexposing sensitive information.Ownership and Accountability
Each Connected App should have a clearly defined business owner.Regular Review
Periodically review active Connected Apps and disable those no longer needed.Compliance and Trust
Ensure external applications meet internal compliance, security, and contractual standards.Business Continuity
Understand the business impact if a connected application becomes unavailable.
Summary
Connected App is a critical business control tool that enables secure, approved integrations between Dafater and external applications. It supports automation, efficiency, and collaboration while ensuring data access remains governed, transparent, and aligned with organizational objectives.
Basic Information
- Module: Integrations
- Document Type: Document
Fields
| Field Name | Label | Type | Required | Options | Description |
|---|---|---|---|---|---|
| provider_name | Provider Name | Data | ✓ | - | OAuth provider name configured for Dafater integration |
| openid_configuration | OpenID Configuration | Data | - | OpenID configuration endpoint used by Dafater for authentication | |
| client_id | Client Id | Data | - | Client identifier issued by provider for Dafater application | |
| redirect_uri | Redirect URI | Data | - | Authorized callback URL where provider redirects users to Dafater | |
| client_secret | Client Secret | Password | - | Confidential secret for secure OAuth communication with Dafater | |
| scopes | Scopes | Table | OAuth Scope | Permissions requested by Dafater from connected provider | |
| authorization_uri | Authorization URI | Small Text | - | Provider endpoint initiating user authorization flow for Dafater | |
| token_uri | Token URI | Data | - | Provider endpoint issuing access tokens to Dafater | |
| revocation_uri | Revocation URI | Data | - | Endpoint to revoke issued tokens used by Dafater | |
| userinfo_uri | Userinfo URI | Data | - | Endpoint returning authenticated user details to Dafater | |
| introspection_uri | Introspection URI | Data | - | Endpoint validating token status for Dafater integrations | |
| query_parameters | Query Parameters | Table | Query Parameters | Additional parameters sent by Dafater during OAuth requests |
Child Tables
Scopes (OAuth Scope)
| Field Name | Label | Type | Required | Options | Description |
|---|---|---|---|---|---|
| scope | Scope | Data | - | Defines OAuth permission scope used by Dafater integrations |
Query Parameters (Query Parameters)
| Field Name | Label | Type | Required | Options | Description |
|---|---|---|---|---|---|
| key | Key | Data | ✓ | - | Parameter name used in Dafater query or API request |
| value | Value | Data | ✓ | - | Corresponding parameter value passed to Dafater query or API |
Permissions
| Role | Read | Write | Create | Delete | Submit | Cancel |
|---|---|---|---|---|---|---|
| System Manager | ✓ | ✓ | ✓ | ✓ | ||
| All | ✓ |
Related DocTypes
| DocType | Relationship | Module |
|---|---|---|
| Email Account | Linked from | |
| Token Cache | Linked from | Integrations |