What ChatGPT can access
Your Crewvana connection belongs to you. Each tenant has a separate grant. Tool access requires a valid OAuth sign-in, the correct linked account and tenant, active membership and the applicable current Crewvana permissions, assignment and plan. A saved tenant scope restriction can further limit access.
Read scopes allow authorized record retrieval. Change scopes allow requests for supported actions. A scope does not grant permissions you lack in Crewvana. Consequential changes retain exact preview and confirmation, current access checks and replay protection.
Profile > Connected Apps > ChatGPT shows your current tenant grant and linked Crewvana identity. When available, it also shows the historical scopes from the verified sign-in last confirmed during linking. That snapshot is not a live view of the token stored by ChatGPT; later consent or revocation may differ. Existing connections without a snapshot retain their access.
Administrators prepare and govern tenant access in Settings > Integrations > ChatGPT with applicable integration permissions. Owning a personal connection does not grant administrator powers.
Monitoring and usage
Profile > Connected Apps > ChatGPT also shows your personal subscriptions, delivery status and My usage & activity for this tenant. Monitoring requires a supported ChatGPT host, an explicit subscription, active connection access and enabled tenant event sharing. A connection alone does not start monitoring. Pause or stop a subscription here to block future Crewvana delivery; already accepted events and running ChatGPT tasks may continue. Stop ChatGPT schedules separately. Automatic replies remain unavailable without a separately approved policy.
Usage totals describe Crewvana calls and deliveries, not ChatGPT tokens or billing. They use UTC and the displayed retention window. Signing in again does not reset usage limits. Authorized administrators manage tenant usage and allowances with both integration view and update permissions. Event sharing requires the separate ChatGPT event administration permission. Deployment readiness and tenant policy may keep monitoring inactive.
Disconnect from one tenant
In that tenant's Profile > Connected Apps > ChatGPT, choose Disconnect from this tenant and confirm. This revokes only your grant for that tenant. Your other grants, your account link and other users' connections remain unchanged.
Disconnect all Crewvana access
In Profile > Connected Apps > ChatGPT, choose Disconnect all Crewvana access and confirm. This revokes your account link and all its tenant grants. The all-access disconnect after the Crewvana linking confirmation has the same effect. Other users remain connected.
Crewvana checks revocation before later authorized tool calls. Disconnecting in ChatGPT is a separate provider-owned action. Use Crewvana's disconnect control to revoke local Crewvana access immediately.
Connect again
Select Crewvana in ChatGPT and ask it to connect your account. Confirm a fresh Crewvana link with the same intended account and tenant. Use provider reconnect only if the host also needs valid OAuth sign-in. Administrator restrictions remain in force after reconnection.
Privacy and deliberate actions
Keep passwords and connection links private. Tool calls are audited, including failed calls. Connecting does not start monitoring or enable automatic replies. Data access and exact consequential-action confirmation remain separate.
Help remains readable without signing in so you can use it when the connection is broken.