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

App status and ownership

Each app shows two independent labels. The connection chip is automatic and specific to your workspace: it reflects whether a credential is configured and whether calls on it are succeeding. The maturity badge (Alpha, Beta, or Certified) is manual and global: it records how much evidence Stackyapper has for the integration itself, regardless of your workspace's connection.

Connection states

Four app rows in the portal: Hudu, Certified, Connected; Microsoft 365, Beta, Your connection required; NinjaOne, Beta, Needs attention; Slide, Alpha, Approval required.
The two labels are independent. Hudu is Certified and connected, while Microsoft 365 is Beta and still waiting on a personal connection. A Certified badge says nothing about whether your workspace has connected the app, and Slide shows Approval required on its action rather than as a connection state.
StateMeaningNext action
ConnectedA call succeeded on the saved connectionGrant the required tools and test a read
ConfiguredCredentials are saved, but the provider has not produced a complete verification signalRun a safe read and review Audit
Needs attentionA previously configured connection cannot currently be used reliablyOpen the app and repair or reauthorize it
Ready to configureA workspace administrator can provide the required shared setupOpen the app and complete the fields
Admin setup requiredYour role cannot configure the organization connectionAsk a workspace owner or admin
Your connection requiredA personal connection has not been authorizedConnect your own account
Platform setup requiredStackyapper cannot complete the provider-level setup yetContact Stackyapper support; changing user credentials will not fix it
Separately from the connection chip, an app that a workspace owner has not yet approved shows Approval required on its action. This is an availability state, not a connection state: the app cannot be enabled until the owner approves it.

Organization and personal connections

An Organization connection uses credentials managed for the workspace; owners and admins normally configure it. Use a service identity only when the provider supports it and the account is governed by your company.
A Personal connection requires each user to authorize their own provider account. One user's authorization is not reused for another user.

Maturity badges

The maturity badge describes the evidence behind the Stackyapper integration, not the security of your provider account:
  • Certified means Stackyapper has recorded live provider evidence for the app and it is ready for normal use.
  • Beta means the app is available for evaluation while its provider coverage is being verified; begin with a small set of read-only tools.
  • Alpha means the integration is early and may change significantly; treat it as experimental.
The badge is separate from rollout: a Certified app can still sit behind an approval gate. Coverage can change, so check the current badge in the portal.