When you connect an AI client to DevStride with OAuth 2.1 (see Setting Up Your Connection), you approve it on a consent page and DevStride issues it tokens that act as you in one organization. Connected Apps is where you see those grants and take them back.
Open My Account → Connected Apps. The page is personal: it lists the apps you authorized, across all your organizations. Administrators do not see other members' apps here.
| Column | Meaning |
|---|---|
| App | The name the app registered with DevStride (for example Claude, Cursor). This is the verified name shown on the consent page, not whatever the app's URL claimed. |
| Scopes | What the grant covers. Today every grant uses the single api scope — full access as you, within the permissions you hold. |
| Authorized | When you clicked Allow. |
| Last Used | The last time the app refreshed its access. |
If nothing is listed you see No Connected Apps — apps you authorize appear here after their first sign-in.
An app renews its access on its own while you keep using it, but a connection lasts at most 90 days from when you approved it; after that the app asks you to approve it again. Each renewal also checks that you are still an active member of the organization, that you have not been signed out since you approved it, and that the organization still allows the way you signed in when you approved it (for example, an organization that switches to requiring single sign-on stops renewing apps approved from a password sign-in). If any check fails, the app asks you to approve it again.
Connections approved before 13 October 2026 start their 90 days at their first renewal after that date.
The app can no longer refresh its sign-in, so it stops working the next time it needs a new token. An access token it already holds stays valid for up to one hour; after that the app has to ask you to sign in again, and you can refuse.