Feature access

Identify whether a missing or refused action needs an organization, permission, entitlement, or interface change.

A missing screen and a refused request can look like the same access problem, but need different repairs. An action can depend separately on organization membership, permission, plan entitlement, and whether the interface exposes it.

Start with the message from the actual request and confirm the selected organization. A visible control does not guarantee authority, and a hidden control does not define every backend access rule.

Identify the failed condition #

ObservationInspect
A section is absent or returns not-found.Organization selection and UI feature availability.
The feature names an entitlement requirement.Current billing state and that feature's gate.
A write names a missing permission.Effective role and additive resource grants.
One Inbox source appears empty.Filters, pagination, provider entitlement, and source access.
A credential stopped working after a change.Membership, key type and scope, RBAC entitlement, and revocation.

Retries do not supply a missing permission or enable a feature. Identify the condition before changing account access.

Check the rule for the specific feature #

Radar's events and measurements require organization membership. Its overview report tiles and Explore also require the reports entitlement, and say so on screen when the plan lacks it. A hidden screen does not prove that every related API is inaccessible, and a visible screen does not grant permission.

The analytics API lets organization members read translation volume; the other analytics reads and saved reports require the reports entitlement. Access to workload volume does not grant access to quality reports. Follow the selected report reference.

Starting new human-review work depends on the plan features available to the engine's pipeline. Existing document reviews remain accessible to authorized reviewers after a plan downgrade. Reading or deciding them requires access to the organization and permission to review the engine's translations; decisions also require a user identity. Check those permissions and the Inbox filters before concluding there is no pending work.

Decision pools have separate management and review requirements. Organization members can see pools, while creating, editing, or archiving them requires Manage decision pools. Pool membership controls notifications and does not grant review permission.

Service keys are available on every plan; giving one a role or localization-engine scope requires RBAC. Audit logs require membership, audit-log entitlement, RBAC, and org:view_audit_logs. Custom-role management requires RBAC and team-management authority. These combinations are more precise than a general “paid feature” label.

Repair the missing condition #

Ask an Owner to assign the required authority when permission is missing. Check Billing for entitlement, and verify the caller's organization and resource scope when the account otherwise appears correct.

An RBAC entitlement transition in either direction resets members and pending invitations to Owner. Review access afterward rather than assuming restrictive roles survive. Roles and permissions explains that consequence.

Use current pricing and billing for commercial availability instead of deriving a plan matrix from code. Keep the original translation or measurement task in view: the goal is to establish the exact access it needs, without unnecessarily broadening the account.