Security
Understand the reporting access, workspace permissions and separate authorizations behind a cost review. Each source and product domain has a defined purpose.
Cost sources use reviewed, source-specific billing and usage access. Google Cloud reads an existing detailed billing export; AWS reads manifest-listed CUR reports; Azure uses Cost Details or Cost Management Exports. Platform and direct-AI sources use their own reporting records.
This access supports financial review rather than control of provider resources. The source catalog explains reporting scope and setup availability.
Customer and staff identities use separate authentication boundaries. Reporting is scoped to the authorized workspace and connection before it is served.
Workspace membership uses the role needed for the task. Individual features can add their own role restrictions; a visible link does not grant data access.
Credentials belong to the approved product connection flow, not marketing or contact pages. Stored credentials are not returned to the browser for display.
Sales and support requests should contain only safe context, with no secrets or raw customer billing records.
Developer Productivity has its own entitlement, owner/admin authorization, responsible-use context and connection consent. Purpose-specific reuse of an eligible cost connection requires separate consent and a capability check; it does not expand cost access automatically.
Its content-free reporting excludes prompts, responses, source code, patches, comments, commit messages and filenames. Activity retention is at most 90 rolling days.
Use public support and select Security. Describe the affected surface and safe reproduction context without including credentials or customer data.
Contact public support