Console

The Console is the browser Surface. It lets a member work in one Workspace.

Set up access

Sign in to the Console. Select the Workspace where you need to work. Check the Workspace name before you change an item. The Console checks your membership and permission before it opens an action. If an action is absent, ask an administrator to check your role. Do not try a different URL.

How the Console works

The Console is for work in the browser. Choose a Capability, give the action its input, and read the result in that Workspace. A control is not its own contract. Its operation name, permission, and readback stay with the admitted API method.

Use the Capability page to learn the object. Use the exact API method to see whether the Console can run an action.

First call

Open Runs and lineage. Follow its Console destination and inspect one Run. Note the Run id in the page address. This invokes dataPipelines.runs.get. Compare the status with the visible Console result. Use that shared readback before you choose another action. The Console gives you the readback. It does not copy the Run contract.

When it fails

Access denied

Cause: your member cannot reach the Workspace or lacks the permission. Recovery: check the Workspace picker. Ask an administrator to grant the Capability permission. A Console control is not proof of permission.

Operation unavailable

Cause: the action has no Console exposure. Recovery: inspect the exact API method and choose a listed Surface.

Reference

• Runs and lineage explains the Run readback. The method above gives its contract.
• Administer workspace access explains Console access recovery.