Know who can read your reports, and for how long.

An invited owner or administrator approves the requesting client on Tilden's consent screen. Check the app name, intended workspace and read-only scope before allowing access. Only connect the workspace and sources agreed during onboarding.

MCP returns four report types: spend, projects, briefing and budget settings. It does not change budgets, enforce provider limits, refresh provider records or upload machine activity. Source credentials and browser cookies are not MCP login credentials.

The current approval grants read-only access for seven days. OAuth refresh can renew a short-lived access token while that grant remains valid; it does not extend the grant's lifetime.

1. Before the next review, open Settings → Apps and check the connection's recorded status.
2. If the grant has expired, return through the client's sign-in and Tilden consent flow. Confirm the workspace and permissions again.
3. Read one scoped report to confirm access. A saved configuration or a successful sign-in is not evidence that the report succeeded.

Client behavior varies. If renewal loops or fails, stop and contact your onboarding owner with the client/version and error, without credentials. Do not repeatedly create connections to work around an uncertain state.

Use Settings → Apps to review connections and remove the selected app's access. If the result is uncertain, inspect the recorded connection and ask your onboarding contact to confirm removal before reconnecting. A new connection may also require resetting the client's saved sign-in consent.

Removal is intended to stop future authorized reads. It cannot erase reports the client already received. Test removal and denied future reads for the partner's setup during onboarding rather than assuming a founder demonstration validates every client.

Hosted Workspace retains the supported records you connect or explicitly share. MCP sends requested report results to the authorized client; those results then follow that client's data policy. A local-first statement about the CLI does not describe hosted Workspace.

Review the privacy policy and source boundaries. For retention, deletion or procurement questions, contact contact@asktilden.com before providing access. Do not include keys or sensitive report contents in a support email.

• Access denied: confirm the invited account, current owner/admin membership, enabled workspace and grant status.
• Wrong workspace: stop the review and confirm the consented workspace with your onboarding contact.
• Report unavailable: inspect the dates and source coverage. Reconnecting cannot create missing historical records.

Return to the first-review checklist →