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. Complete the connection in your company's active workspace.

Understand the three separate decisions

An app is usable only when all required conditions are satisfied:
  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. Likewise, 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. Select your company workspace before continuing.
  2. Find the app
    Open Apps. Search for the provider or select All apps to browse the catalog. Review its availability and credential ownership before enabling it.
  3. Enable the app if required
    If the app is available but disabled, an owner can select Enable. Some apps require an access request or remain unavailable until approved.
  4. Connect the provider
    Select Connect, Configure, or Configure OAuth, depending on the app. Enter only the fields requested in the Connection tab. Complete provider authorization when redirected.
  5. Check the connection state
    Return to Apps and verify that the app reports a configured or verified connection without a needs-attention warning.
  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 administrator 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.
  • The required credential shows as connected or verified.
  • Your test user or group has at least one read-tool grant.
  • 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.
Powered byHolocron