Skip to main content
OAuth is the simplest option when your client supports it. Your client handles the credentials while Nimt asks you which workspace it may access.
1

Start from your client

Add the server using the connection guide, then start the client’s sign-in or authentication flow. Let the client discover Nimt’s OAuth settings; you do not need to create an OAuth application manually.
2

Sign in to Nimt

Use your normal Nimt account in the browser. Check that it is the account with access to the workspace you intend to connect.
3

Review and approve

Check the requesting client’s name and identifier, select one workspace, and review the permissions. Choose Allow access only if you trust the application. You can decline instead.
4

Return to your client

Complete the return to your client and ask it to list your Nimt projects. The approval is tied to the workspace you selected. Approving it does not change your active workspace in the Nimt app.

Staying connected

Access tokens currently last five minutes. With offline_access, a compatible client can renew them using rotating refresh tokens, which expire after 30 days. The client handles renewal; do not copy access tokens out of the sign-in flow. You may need to sign in again after authorization expires, a connection is disconnected, or the client loses its saved credentials. Workspace membership and the approval are still checked while a token is valid.

Disconnect an app

When available for your account, open Settings → Connected apps in Nimt. Find the client and workspace you want to disconnect, then choose Disconnect and confirm. Disconnecting revokes that approval, including its refresh access and already issued access tokens. Other approvals and PATs are separate. Reconnecting creates a new approval; it does not restore the old credentials.
The settings entry may be unavailable during pre-release. If you need to review or remove a connection and cannot find it, contact support@nimt.ai.
For a different workspace, start a new authorization and select it explicitly. See authentication and access for the shared permission rules, or troubleshooting if sign-in fails.