App Credentials provide secure, application-level authentication for external systems that need to access your Yeeflow application.

Unlike user authentication, App Credentials are designed for machine-to-machine communication. They allow backend services, automation platforms, custom applications, and AI-powered services to securely call Yeeflow APIs without requiring a user to sign in.

Each App Credential is scoped to a single application, allowing administrators to control exactly which resources an external system can access while keeping permissions isolated from other applications.

With App Credentials, you can:

App Credentials provide a secure foundation for integrating business systems, automation platforms, and AI services with Yeeflow applications.

Before creating an App Credential, ensure that:

The creation wizard consists of three steps.

The Basic information page defines the identity of the App Credential.

Provide the following information:

The Access scopes page defines which application resources the credential can access.

Depending on your application, supported resource types include:

For each resource type, choose one of the following permission levels:

This enables fine-grained permission control and helps follow the principle of least privilege by exposing only the resources required by the integration.

After configuring the required permissions, click Next step.

The Token settings page determines how long the App Credential remains valid.

Selecting an appropriate expiration period helps improve security by ensuring credentials are reviewed and rotated regularly.

Available options include:

Recommended only for trusted internal integrations that require long-term access and are managed under strict security controls.

Suitable for testing environments, temporary integrations, or scenarios requiring frequent credential rotation.

Recommended for most production integrations that follow regular security policies.

Suitable for long-running integrations where less frequent credential rotation is acceptable.

After selecting an expiration policy, click Create Credential.

Yeeflow generates:

After an App Credential is created, open it to view its configuration and management options.

The details page includes:

Each App Credential includes a Primary Client Secret and supports an optional Secondary Client Secret.

Using two client secrets allows credentials to be rotated without interrupting production integrations.

Available actions include:

If a client secret is approaching expiration or needs to be replaced:

Regular secret rotation is recommended to improve security.

Administrators can manage the lifecycle of an App Credential directly from its details page.

Available actions include:

Use the Enabled toggle to temporarily enable or disable the credential.

When disabled, authentication requests using the credential will be rejected until it is enabled again.

Select Edit settings to update:

If a credential is approaching its expiration date, click Extend to configure a new expiration period without creating a new credential.

Delete an App Credential when it is no longer required.

Deleting a credential permanently revokes all associated client secrets, and external applications can no longer authenticate using that credential.

Each App Credential includes built-in monitoring and auditing capabilities.

The Access scopes tab provides a summary of the resources and permissions granted to the credential.

Review this information regularly to ensure the credential has only the permissions it requires.

The Call Log records API requests made using the credential.

Information may include:

Use the Call Log to troubleshoot integration issues and verify successful API activity.

The Audit Log records administrative actions performed on the App Credential, including:

This provides a complete audit trail for security, governance, and compliance.