DEVELOPERS
Find connections after the Apps navigation update
Find personal and organization connections in their new destinations.
RIIW now separates personal connections from organization apps in navigation. The former combined experience used ownership tabs inside an organization page, which made a user-owned token appear dependent on the active organization. The new model places each connection in its actual ownership boundary.
The change does not migrate, duplicate, reconnect, or remove credentials. It changes where you discover and manage each record.
Find a personal connection
Open My apps in the personal section of the left navigation. The account-level route is /apps. Use All apps to discover supported personal providers or Connected to review existing authorizations.
Personal Google Drive appears here. Its connection belongs to the signed-in RIIW user and remains the same when the active organization changes. Search results, provider account details, and commands are not exposed as organization credentials.
The old /connected-apps URL redirects directly to /apps. This redirect is safe for bookmarks because the former URL represented the user’s account-level connection list.
Find an organization connection
Select the organization, then open Apps under the organization section of the left navigation. The route includes the organization slug. This page lists organization storage connectors and completed organization application authorizations without exposing credentials.
Organization owners can use Manage organization apps in the page header to open Organization settings → Apps & integrations. Members can view the organization’s inventory but cannot gain mutation access merely by opening the page.
Apps that support both scopes
Google Drive can appear in both destinations:
- My apps → Google Drive is the user’s private provider authorization for search, imports, previews, and commands.
- Organization → Apps → Google Drive is the organization-owned storage connection for shared workflows and default upload selection.
These connections have separate tokens, ownership, status, removal, and permissions. Disconnecting one does not disconnect the other.
Future Slack, GitHub, and other providers can use the same catalog definition while keeping user and organization authorization records separate. A provider’s product name does not determine ownership; the destination and connection scope do.
Find a custom OAuth authorization
A developer creates an application under Developer Settings. After an eligible organization administrator completes authorization, the resulting organization connection appears in that organization’s Apps inventory. Application registration and organization authorization remain separate lifecycle records.
Use organization settings for suspension, revocation, and other protected lifecycle actions. These actions can affect tokens, principals, and dependent webhooks for the selected organization.
Troubleshooting
If /connected-apps does not open My apps, refresh after the current frontend deployment and confirm that the route is served by the frontend rather than the API. If a personal connection is missing, verify the signed-in user and provider authorization. If an organization app is missing, verify the selected organization and use All apps rather than Connected.
If an organization management button is missing, confirm that the user is the organization owner or has the required management capability. Page visibility is intentionally broader than mutation permission.
For personal workflows, read Manage your personal apps. For organization workflows, read Manage organization apps. For the complete ownership model, read Understand App Center.