Apps

Apps connect Stackyapper to the systems your company already operates. Each app defines its authentication method, available tools, access model, and current support level.

Which apps are supported

The Apps page in the portal is the live catalog for your workspace, covering PSA, RMM, documentation, and the other systems an MSP runs. The default list contains apps already enabled, connected, or available to you; search or use the category and access filters to find more. Each entry shows availability, a maturity badge (Alpha, Beta, or Certified), and connection requirements. If a system you need is not listed, see Request an app.

Start with one useful system

Choose an app that can answer a small, read-only question your team already asks. Connect it, grant only the required read tools, and confirm the result in Audit before expanding access.

Before connecting, confirm:

Whether the app uses an organization connection or a personal connection, and which account should own the credential.
Whether the credential is limited to the intended company, tenant, or site.
Which read tools are needed for the first workflow.
Who will respond if the connection later needs attention.

What connection does not do

Connecting an app supplies the credential or authorization Stackyapper needs. It does not automatically grant every user every tool. App availability, workspace policy, groups, user grants, and restrictions determine effective access.

Understand access

Learn how app availability and user policy combine.

Find the reference for an app

Open Apps, search for the provider, and open its connection details. Configuration guidance appears alongside the fields that require it, together with the app's authentication method, required fields and prerequisites, tenant boundaries, available tools and their risk classification, confirmation requirements, and known setup limitations.

Request an app

If an app is not present, use Request an app from the empty search result. Include the provider name, the business workflow, the tenant boundary, and the smallest set of operations required. Do not send credentials or API keys in the request.

Support information to collect

When reporting an app problem, include the app name, its visible connection state, the approximate time of the failed attempt, the tool name if known, the Audit outcome and request identifier, and whether the connection is organization-owned or personal. Never include secret values, authorization codes, or full provider responses. For the escalation path, see Troubleshooting.