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

Connect your first app

Start with an app that contains a small, recognizable record you can retrieve safely. An app is usable only when three separate decisions are all in place:
  1. Available: Stackyapper makes the app available to the workspace.
  2. Connected: The required organization or personal provider credential is configured and healthy.
  3. Granted: The user or one of their groups is allowed to use the required tool.
A credential does not automatically grant tool access, and a tool grant cannot operate without a valid provider connection.
  1. Confirm the active workspace
    Check the workspace selector at the top of the portal sidebar and select your company workspace. See the workspace caution.
  2. Find the app
    Open Apps → Add app → Browse apps. Search for the provider, or choose All catalog apps in the Category filter. Review its availability and credential ownership before enabling it.
  3. Enable the app if required
    If the app is available but disabled, an owner or admin can select Enable. Some apps show Approval required; select Request access and wait for Stackyapper to approve the request before you can enable the app.
  4. Connect the provider
    The button depends on the app:
    App typeButton
    OAuth apps whose OAuth app details are not yet savedConfigure OAuth
    OAuth apps ready for provider sign-inAuthorize
    Apps that support several connected accountsConnect account
    Other organization appsConfigure
    Other personal appsSet up your connection
    After the first connection, the button changes to Manage or Manage accounts. Enter only the fields requested in the Connection tab and complete provider authorization when redirected.
  5. Check the connection state
    Return to Apps and verify that the app reports Configured or Connected without a Needs attention warning. If it shows Ready to configure (or Admin setup required for non-admins), the organization connection still needs setup.
  6. Grant narrow read access
    Open the app’s Permissions tab or go to Users & Groups. Grant your test user or test group only the read tools needed for the first request. Avoid write, destructive, and credential-sensitive tools during onboarding.

Organization and personal connections

  • Organization connection: one workspace-managed credential is used for authorized users in that workspace.
  • Personal connection: each user authorizes their own provider account.
For a personal app, an admin can enable the app and grant its tools, but the individual user must still complete their own connection.

Verify before continuing

  • The correct workspace remains selected.
  • The app is enabled, its connection is healthy, and the read grant is in place (steps above).
  • No broader access was granted accidentally.
Beta identifies the app’s support and verification stage. It does not bypass workspace policy, credential requirements, or confirmation controls.
Connect an AI client and verify the result
Continue after the app and read permission are ready.