Guide: revoke a client’s access

Retire the exact credential path used by an application.

Practical procedure

1. Identify the client and the authority that provisioned its credential or device access. Confirm which integration will be affected.
2. Use that supported revocation workflow and remove the credential from the client’s own trusted storage.
3. Verify that new requests no longer establish the retired identity and review any outstanding task state separately.

Separate the external system from GoCux authority

A named external tool in a workflow does not establish a native GoCux integration. Start with an authorized export, an already configured connector, or a separately implemented adapter. Keep external account credentials in the owning system. In GoCux, inspect the available connector and its grants; the fact that a connector is registered does not itself authorize a task to use it.

Contract example

Developer examples below describe routes on an authorized, configured GoCux control-plane base URL. They are request shapes or operation references, not claims that a particular public hostname exposes the API. Use the workspace for the corresponding human workflow; availability and permissions depend on the actual deployment.

Operation reference for this workflow

GET /me

Inspect the result

The useful outcome is an explicit boundary: what information enters GoCux, which task can access it, and what result leaves. Start with a read-only sample and verify its source context. A local client or adapter owns the external invocation and its error handling unless an actual deployed connector provides that behavior.

What to keep explicit

Deleting a local configuration value is not proof of server-side revocation. No generic customer API-key DELETE endpoint is implied by this guide.

Handle incomplete and refused work

Authentication with the external system is separate from GoCux authentication. Missing grants, revoked permissions or unavailable connectors must remain visible; do not replace them with invented data. Publishing a marketplace listing, creating a paid external resource or sending messages is a separate action from preparing an integration guide.

Continue with related guides

• Choose a developer integration path
• Understand authentication boundaries
• Understand company authority and permissions
• Choose a GoCux workflow