Apps
Review and revoke applications connected to an rstream account.
An App acts on behalf of an rstream user through OAuth. The application directs the user to rstream, where the user signs in and reviews the permissions and project access being requested.
The Apps page in account settings shows the applications that have access. A backend, CI runner, or device that needs access independent of any one user's membership can use a workspace Token.
Connect an application
- Start the connection from the application.
- On the rstream consent page, check the signed-in account, application name, and requested access.
- Review the project boundary. A request can cover all accessible projects, selected workspaces, or selected projects. An application that requests a narrower boundary cannot be given broader access through consent.
- Approve the request to return to the application, or reject it without granting access.
The grant is limited to the permissions and resources approved during consent. rstream also checks the user's current membership and permissions whenever the application uses the grant.
Apps request permissions from the same catalog as personal Tokens. The rstream OpenAPI descriptions and MCP tools identify the scopes required for each operation. Operations such as profile changes and release package management are account-wide. Each Personal Agent Protocol client must be registered with rstream before it can request consent.
For workspace changes, member and invitation APIs, and project creation, select the whole workspace rather than individual projects. See workspace-wide operations for the required permissions and boundaries.
An App can read Token metadata with account.credentials.read-only. Personal Token metadata requires account-wide access. Workspace Token metadata requires access to the entire workspace and a current owner or admin role. The metadata contains the Token configuration and access summary. See Token metadata for the applicable boundaries.
With account.credentials.read-write, an App can create, update, rotate, or delete Tokens within those same boundaries. Creation and rotation return the new secret once and are limited to the App's current authority. The resulting Tokens have their own lifecycle and are managed on the Tokens page.
Review and disconnect
The Apps page in account settings groups connections and their access summaries by application.
Disconnecting an application revokes its connections for the current account, including any approved sign-in that has yet to finish. The application must request new consent before connecting again.
Project changes and checkouts already accepted have their own lifecycle. Use the project's cancellation or deletion workflow to remove the corresponding resource.
Disconnection also invalidates temporary tokens derived from the grant. Established streams follow their own lifecycle.
Expiration and renewal
Poppy access tokens last at most one hour. An application can renew them with a rotating refresh token within the approved connection's lifetime, which is at most 90 days. Renewal cannot expand the approved permissions, project boundary, or absolute lifetime. Current account restrictions can shorten access further.
The historical /api/mcp account-linking flow is managed through the personal rstream MCP OAuth Token on the account's Tokens page. See API authentication for that flow.
Apps and application keys
An application key (APP) is one of the Token types. A backend uses its Client ID and Client Secret to sign short-lived tokens. Application keys are managed on the Tokens page of the owning account or workspace.