Authorized applications

The Integration, Authorized applications page lists applications granted access to your account through the Raims authorization flow. The same authorization supports MCP clients and other compatible applications, including platform and service integrations.

Each connection identifies the application, who authorized it, its environments, and its granted permissions. The application remains subject to the current permissions of the person who authorized it and to the account's rules.

The Authorized by column shows the identifier of the person who granted access. Check this identifier to distinguish connections to the same application.

Installing an application on another platform and authorizing access to Raims are separate steps. Complete the flow presented by the application and check the account on the Raims page before granting access.

Authorize an application

1. Start the Raims connection in the compatible application.
2. Sign in on the Raims page opened in your browser.
3. Check the application and select its access under Permissions.
4. Select Review to check the application, account, environments, return destination, and permissions.
5. Choose Authorize access and complete the security confirmation when requested.
6. Return to the application to continue.

Sign-in preserves the account's security controls, including MFA when requested. You do not need to share your Raims password with the application. The connection uses OAuth, so you do not need to create or enter an API key for the application.

The name and icon help identify who is requesting access, but they are not a verification or partnership badge. If you do not recognize the request or do not want to grant the permissions, close the page without authorizing it.

Permissions and environments

Each operation has its own selection. Allowing charge creation does not grant viewing, updating, revoking, or refunding. Groups organize the matrix; they do not replace the individual operation choices. Suggested profiles fill a selection that you can review before authorizing.

Use Learn more below an operation to check what it allows, its effects, and supported environments. For example, customer registration by tax ID can update an existing customer with the same tax ID.

A new connection includes the environments permitted for your account and access. The selected permissions apply to those environments. Changing the Dashboard environment does not change an existing connection's scope. Renewing authorization does not expand its permissions or environments either. Editing lets you restore access included in the original authorization; other access requires a new connection started by the application.

Consent authorizes the connection once. Granted operations can run without another approval screen for each task, while remaining subject to current permissions, limits, and Raims validation.

If access or environments change while connecting, check the summary again before completing it. Authorization is not repeated automatically.

View access

Open Integration, Authorized applications to view applications, who authorized them, their environments, and their expiration. Members can view their own connections. View company applications extends the list to connections authorized by the owner and team. Revoke team connections also allows this viewing and revocation of other employees' connections, but not the owner's connections.

To review a connection's permissions, select Edit permissions in its action menu, when available. Opening the editor, searching, and expanding groups does not change access. The application's row remains highlighted while the editor is open.

Viewing company connections does not allow editing or revoking other people's access. Session and device permissions do not grant application management. An authorized administrator must grant these permissions; existing members do not receive them automatically.

API keys have their own management page under

Integration, API keys.

Edit permissions

Select Edit permissions in the connection's action menu, when available. Use Search permissions... to find access. Choose one of the Suggested profiles or expand the groups to adjust individual permissions. Select Save changes and complete the security confirmation.

The profiles shown depend on the access already authorized for the application. Current profile reflects your selection, and each group shows how many permissions are selected. Searching filters the display without changing the selection. Check the groups before saving.

Each item shows the operation's name and a description. Learn more opens its full explanation in this documentation without changing the selection.

The person who authorized the connection and the account owner can edit its access, subject to both people's current permissions. Permission to view or revoke team connections does not automatically allow editing them.

Editing lets you remove and restore permissions from the original authorization. Access that is no longer available can remain selected or be removed, but it can only be restored once it becomes available again. The selection does not override current permissions. To grant other access, start a new connection in the application.

The environments, expiration, and credential stay the same. Removing a permission prevents its use in subsequent calls without undoing completed operations or deleting data the application already received.

If another change makes the edit outdated, select Discard changes and reload and check the access before saving again. If saving fails, your selection is kept so you can check the message and try again.

Revoke a connection

1. Find the application under Authorized applications and check the identifier in Authorized by and its environments.
2. Select Revoke access in its action menu.
3. Check the application and the authorizing person's identifier in the confirmation, then complete the action.

Revocation prevents new calls authorized by that connection. It does not undo completed operations or delete data the external application already received. Signing out of the Dashboard does not replace revocation.

To use a revoked application again, start a new connection in that application and review its permissions again.

Track activity

Open Account, Activity log to track accepted or declined authorizations, permission changes, revocations, and expirations. A security revocation caused by credential reuse also appears in the history. Automatic events are identified as System.

Members can view their own activity. View full audit log allows viewing activity across the company. Recorded actions performed by an employee through an application preserve that employee's identity in the history. Viewing a connection or opening the editor without saving does not change its permissions.

When a connection cannot be completed

• If the request expired, was already used, or is unavailable, return to the application and start another connection. Reopening the same link does not renew the request.
• If a temporary failure prevents loading the request, wait for the page's automatic retries. Only the query is repeated; authorization still requires your confirmation.
• If access is denied, check the account and your current permissions.
• If the application requests authentication again, start the connection and check the consent page presented by Raims.
• If an operation's result is uncertain, check the resource before requesting another creation.

Authorized operations

The operations below can be selected individually when available for the account and the person authorizing access. The connection allows only those included in consent, and editing cannot add operations outside the original authorization. Selecting an environment does not replace this authorization.

The descriptions preserve each public operation's rules; the OAuth connection supplies its credential. You do not need to create or enter an API key.