Manage organization apps

The organization Apps page shows applications provided to the selected organization. Open the organization section in the left navigation and select Apps. The organization name in the page header confirms the scope you are viewing.

Every member can discover organization apps and review connection status. Credentials, provider account identifiers, bucket locations, tokens, and private configuration are not exposed on this member-facing page. Organization owners use Manage organization apps to open the protected settings surface for connection changes.

Review organization apps

Select the intended organization in the organization switcher.
Open Apps under the organization section of the left navigation.
Use All apps to review the organization catalog and connected custom applications.
Use Connected to limit the view to active organization connections.
Select Google Drive, Custom S3, or GitHub to review organization-specific capabilities and current status.

Changing organizations changes this page’s inventory. A connection displayed for one organization never grants access to another organization.

Owner management

Organization owners can select Manage organization apps in the page header. This opens Organization settings → Apps & integrations, where protected operations remain available:

connect or remove organization Google Drive;
add, test, name, and remove Custom S3 connections;
manage organization OAuth authorizations and lifecycle state;
install GitHub organizations and map selected repositories to RIIW projects;
allow or block members from using supported personal connections inside the organization.

The Apps page is the discovery and usage surface. Organization settings is the administrative surface. Keeping these responsibilities separate lets members understand what is available without exposing configuration or granting management capability.

Personal connection access

Users connect their own accounts once from My apps. A personal connection is not copied into every organization and its credentials are never shown to organization managers.

To change whether members can use a supported personal app:

Open Organization settings → Organization Apps.
Find Personal connection access.
Select Allowed or Blocked for Google Drive, GitHub, or another supported provider.

Allowed lets current organization members use their own connection subject to their existing RIIW role and the permissions of their external account. Blocked stops personal app operations in this organization. It does not disconnect the member's account from My apps or affect another organization.

Google Drive and GitHub personal use is allowed by default. Providers that do not support personal ownership, such as the current Custom S3 connection, remain organization-managed.

Organization Google Drive

An organization Drive connection creates and maintains the organization-owned root used by authorized RIIW workflows. Owners can later select that connection as the default under Organization Storage. Changing the default affects new uploads only and does not move existing files.

The organization Drive connection does not provide personal connected search. A member who wants private Drive search and personal commands must connect Google Drive separately from My apps.

Custom S3 and custom applications

Custom S3 is organization-scoped in the current catalog. Owners can add more than one named bucket connection and select the default independently. Members can see that Custom S3 is available or connected, but credentials and external bucket details remain restricted.

Custom OAuth applications appear after an eligible organization administrator completes authorization. Suspending or removing an organization authorization affects that organization’s grant, principals, tokens, and dependent webhooks; it does not remove the developer’s application registration.

GitHub development integration

GitHub uses an organization installation for repository access and project mappings. Members can see connection status and task development activity, while users with Manage integrations install the GitHub App and change mappings. A separate personal GitHub connection supplies user identity; it never replaces or inherits the organization installation. Read Connect GitHub to RIIW projects for setup and task-key conventions.

Permissions

Members can view the Apps page and use organization-provided capabilities allowed by their role. Organization mutations are checked again by the backend and require the appropriate owner or management capability. Visibility of an app card is never treated as permission to change credentials.

Personal and organization ownership are independent. Removing an organization connection does not disconnect a member’s personal account, and removing a personal connection does not change organization storage.

Troubleshooting

If Apps is empty, confirm the selected organization and switch back to All apps. If Manage organization apps is missing, your current organization role is not the owner role required by that management entry. If a connection is shown but cannot be used, ask an owner to review its health, policy, enabled modules, and default-storage selection.

For private account connections, read Manage your personal apps. For the shared catalog model, read Understand App Center.