DEVELOPERS
Understand App Center
Understand personal connections, organization apps, and protected app administration.
RIIW uses one application catalog with separate ownership scopes. The navigation and connection records make ownership explicit instead of combining personal and organization credentials in one tabbed page.
Use My apps for connections that belong to the signed-in user. Use the selected organization’s Apps page for applications provided to that organization. Use Organization settings → Apps & integrations for protected organization administration.
Choose the correct destination
| Destination | Purpose | Typical access |
|---|---|---|
| My apps | Discover, connect, and remove private user accounts | Signed-in user |
| Organization → Apps | Discover and use apps provided to the selected organization | Organization members |
| Organization settings → Apps & integrations | Connect, remove, configure, and govern organization apps | Organization owner or authorized manager |
| Developer Settings | Register and maintain a custom OAuth application | Application developer |
| API & Webhooks | Manage organization service credentials and event delivery | Authorized organization manager |
These destinations can show the same catalog application without sharing a connection. Google Drive can have one personal connection for a user and a separate organization connection for shared storage. Tokens, permissions, lifecycle state, and removal remain independent.
GitHub follows the same ownership boundary with different responsibilities: the organization GitHub App installation selects repositories and creates task development links, while the personal GitHub connection supplies identity and user-authorized actions. See Connect GitHub to RIIW projects.
Shared catalog, separate connections
An app definition supplies its name, icon, category, supported scopes, and feature description. Personal and organization connection records reference that same definition. This avoids duplicated product listings while preserving clear ownership and backend authorization boundaries.
An app that supports only organization ownership appears only on the organization Apps page. An app that supports personal ownership appears in My apps. When both are supported, the app appears in both destinations with wording and actions appropriate to that scope.
Personal ownership
Personal connections are private to the signed-in user. A personal provider token is never presented as an organization credential. Personal search results and commands use only resources the connected provider account can already access.
Switching the active organization does not create or switch the personal connection. An organization can still restrict whether a personal app may be used with its data, but policy enforcement does not transfer ownership of the external account.
Read Manage your personal apps for connection and removal steps.
Organization ownership
Organization connections belong to one organization. Members can review the available inventory without receiving configuration access. Owners manage credentials and connection lifecycle from protected organization settings. Backend permission checks remain authoritative even when a card or status is visible to every member.
Organization Google Drive, Custom S3, Slack installations, GitHub organization apps, and custom OAuth authorizations can follow this model. A connection in one organization does not grant access to another.
Read Manage organization apps for member and owner workflows.
Storage and OAuth differences
Storage connectors and OAuth applications appear in the same catalog because users discover them as apps, but their runtime responsibilities remain separate. Organization Storage selects the default location for new uploads. API & Webhooks manages service credentials and event delivery. Developer Settings registers custom OAuth applications before an organization authorizes them.
Removing a storage connection does not automatically move existing files. Removing or revoking an OAuth authorization can invalidate tokens, principals, and dependent webhook delivery for that organization. Review the app detail and affected workflows before removal.
Existing links
The former /connected-apps account URL now redirects to My apps because it represents user-owned connections. Existing organization Apps URLs remain organization-scoped. Redirecting an old URL does not recreate, duplicate, or disconnect credentials.
Troubleshooting
If an app appears in the wrong destination, first identify who owns the external account and which RIIW record is expected. If My apps cannot load, verify the personal Apps API and provider configuration. If organization inventory cannot load, verify membership and the organization connection endpoint. If an administrative action is missing, confirm the organization role and required management capability.
For default upload selection and external storage details, read Connect external storage. For custom authorization lifecycle, read Manage OAuth installations.