Agent-readable docs index: /llms.txt. Full docs in one file: /llms-full.txt. Download /docs.zip to grep all markdown files locally.

Apps and credentials

Connecting an Organization connection requires the owner or admin role; members connect only their own Personal connections. Each Stackyapper app uses one of two connection ownership models.

Organization connections

An Organization connection is shared inside one workspace. Admins typically use this model for PSA, RMM, security, and documentation systems that provide a workspace-level API account.

Personal connections

A Personal connection belongs to one Stackyapper user. Apps that represent an individual account ask each user to complete their own authorization. An admin enabling the app does not create that personal authorization for everyone.

Availability and rollout state

An app can be generally available or in beta rollout, and carries a separate maturity badge (Alpha, Beta, or Certified). Beta apps remain visible while their provider coverage is being verified.

Connect an organization app

  1. Create or select a provider identity limited to the intended tenant, role, and scopes.
  2. Select the intended Stackyapper workspace.
  3. Open Apps and review the app's status and credential owner.
  4. Enter or authorize the provider credential for that workspace's provider tenant.
  5. Save the connection.
  6. Run the smallest available read and verify it in Audit.
Do not test a new credential with a write operation. Verify with the smallest available read first.

Rotate a shared credential

  1. Create the replacement credential in the provider, preserving the same provider tenant and least-privilege scope.
  2. Update the app in Stackyapper.
  3. Run a small read and verify it in Audit.
  4. Revoke the old provider credential.

Reconnect or disconnect

Reconnect when the provider credential expires, is revoked, or no longer has the required provider scope. Preserve the same provider tenant unless the original connection was incorrect.
Before disconnecting an Organization connection:
  1. Identify users and workflows that depend on it.
  2. Revoke or update related Stackyapper grants.
  3. Disconnect the app.
  4. Revoke the old credential at the provider when appropriate.
  5. Confirm new calls no longer use the connection.

Review credential ownership and scope

Review a connection when its owner changes, a user leaves, the provider changes its permissions, or a workflow no longer needs the same access. For every Organization connection, verify:
  • The provider identity still belongs to the intended tenant.
  • Its provider-side role and scopes are no broader than the current workflows need.
  • The person responsible for rotating or revoking it is still known.
  • The related Stackyapper app and tool grants still match current job duties.
Stackyapper permissions cannot narrow what someone does by signing directly into the provider account. Keep the provider credential itself least-privileged.

App needs attention

Use the status shown on the app in Apps to pick the right fix:
  • Platform setup required: the app is waiting on a Stackyapper-side setup requirement; a new credential does not fix it.
  • Ready to configure: an app without its Organization connection, shown to a user who can configure it.
  • Admin setup required: the same unconnected app, shown to a user who cannot configure it—ask an owner or admin.
  • Your connection required: the app uses Personal connections and you have not authorized your own account yet.
  • Needs attention: the existing connection is unhealthy; review the displayed error and reconnect if it is credential-related.
  • Configured: the connection is saved and healthy.
Reconnect only when the issue is credential-related. A provider outage, platform-setup requirement, or pending approval is not fixed by repeatedly replacing a valid user credential.
Provider credentials grant transport access; Stackyapper policy still decides which tools a user or AI client can discover and execute.
Powered byHolocron