Connect an AI client and verify the first read

This procedure verifies the complete path: AI client identity, Stackyapper workspace authorization, tool permission, provider connection, result, and audit record.

Connect the client

Choose the guide for ChatGPT, Claude, Codex, or another MCP client.

During OAuth authorization:

Sign in with the same company identity used in Stackyapper.
Read the workspace name on the Stackyapper consent page.
Confirm that it is the workspace containing the app you just connected.
Approve the connection and return to the AI client.

Stop if the consent page shows the wrong workspace. Return to the portal, select the intended workspace, and start the client connection again.

Run a bounded read

Adapt this request to the app and record selected during preparation:

1234Using Stackyapper, find a read-only tool for [app] that can list [record type].
Retrieve no more than five records. Do not create, update, delete, execute, or
otherwise change provider data. Tell me which Stackyapper tool you used and
whether the request succeeded.

The exact tool depends on the connected app and your grants. A successful result should contain recognizable provider data and should not request confirmation for a write operation.

Verify the audit record

An owner or administrator should:

Open Audit
In the Stackyapper portal, confirm the same workspace is selected and open Audit.
Find the call
Locate the recent event using its time, app, tool, user, client, or successful status.
Compare the evidence
Confirm that the app, tool, actor, MCP client, risk class, result status, and approximate duration match the test.

Stackyapper audit records contain operational metadata. Tool arguments and provider response bodies are not stored in the tool-call audit log.

If the test fails

Result	Check
Client cannot connect	Confirm the client-specific Stackyapper URL and repeat OAuth.
Wrong workspace appears	Select the intended workspace in the portal and reconnect the client.
App is missing	Confirm app availability and workspace enablement.
Tool is missing	Confirm the user or group has a grant for that read tool.
App needs attention	Reconnect or repair the provider credential.
Permission denied	Check the workspace risk ceiling, app policy, group grants, user grants, and explicit deny rules.
Provider error	Confirm the provider URL, region, scopes, credential, and service availability.

See Troubleshooting for additional connection guidance.

Completion checklist

The client is connected to the intended Stackyapper workspace.
The read returned expected provider data.
No provider data was changed.
The matching successful audit event is visible.
The user has no unnecessary tool grants.

Invite your team

Move from a single-user test to controlled team access.