Console guide

Workspaces and access

Understand why pages, records and actions differ between workspaces and between people.

The workspace selector determines which working context you’re viewing. Your permissions determine which records and actions are available within it. Check both when information seems missing.

Membership, content and administration

Permission	What it determines
Workspace membership	Which workspaces you can enter.
Content access	Which labeled records and evidence you can read.
Action permissions	Which review, import or administration controls you can use.

Membership doesn’t mean every record is visible. Seeing an administrative page doesn’t mean unrestricted access to its workspace’s content. A platform administrator manages service-wide controls; a workspace administrator manages the controls available within a workspace. Some people have several roles.

Use the roles and access information shown by your organization. A hidden page may reflect your role. An unavailable page may instead mean its service isn’t available. Those are different problems.

Before changing access

Review the person or agent, the requested area, the scope of access and any stated expiry. Confirm only the access intended for that request. An agent’s connection doesn’t replace the permissions governing the information it can use.

Where Check access is available, use it to inspect the proposed access question. A check doesn’t grant access. Use the separate authorized request or administration action to change permissions, then verify the result.

Labels on imported information

Access labels describe how information is governed. Choose from the options offered for your current workspace and clearance. Don’t choose a broader readership simply to make a missing record appear.

If the intended label isn’t available, ask a workspace administrator to review your access and the document’s destination. See Labels and information flow for the underlying model.

For applications and agents, use the connection instructions issued to your organization. Coding harnesses and the MCP guide describe the supported integration patterns. Keep credentials out of support messages and screenshots.