---
title: "Scope access to the job."
description: "Console credentials bind agent access to an organization, approved channels, a defined scope and spending controls. Result-use permissions apply after execution too."
canonical: "https://altss.com/console/security-and-permissions"
last-updated: "2026-11-17"
---

# Scope access to the job.

Console credentials bind agent access to an organization, approved channels, a defined scope and spending controls. Result-use permissions apply after execution too.

Last modified: 2026-11-17

## Separate the permission checks

| Control | Question it answers |
| --- | --- |
| Identity and organization | Which authorized organization does this machine principal represent? |
| Channel | May this credential use the REST API, MCP or its specifically approved channel? |
| Scope | Which catalog and operations can this principal request? |
| Spending limits | May this request reserve the quoted maximum within the approved ceilings? |
| Execution consent | Has the purchaser accepted this exact quote and its use terms? |
| Source and output rights | May these fields be delivered and used for the requested purpose? |


## Choose the supported authorization method

A Console-issued scoped machine key can connect through its approved channel. A user-claimed service authorization flow lets an agent request a credential that a verified human approves. MCP clients can also use the advertised authorization-code flow with S256 proof and a public client metadata document. Discover the current metadata and follow the method’s exact resource binding.

A human account token is not a machine credential. Keep keys and proof material in a server-side secret store or an appropriate local credential store, never in public URLs, shared examples or browser-delivered marketing code. Revoke an unnecessary credential through the supported Console controls.

## Source permission follows the result

Altss combines independently collected public-source business information, Altss-developed research and derived analysis, and commercially licensed contact enrichment. Public facts carry source references, collection dates and relevant evidence; known source restrictions remain applicable. Licensed enrichment follows recorded provider or dataset permissions for the intended use and delivery. Collection method, factual verification, privacy duties and redistribution rights are separate questions.

An output’s terms can govern storage, caching, retention, attribution and downstream use. A derived field keeps the applicable restrictions inherited from its inputs. A successful execution does not expand a provider’s redistribution permission or remove a privacy restriction. Keep those terms with the result when passing it to another system.

## Keep public reading and paid execution separate

Anonymous public website readers return bounded published information. The paid Console uses a separate host, credentials and execution contract. Do not attach Console credentials to public website or documentation requests. Conversely, a public profile URL or an anonymous A2A response does not grant access to paid Console research.

## Security and authorization references

- [Canonical authorization guide](https://altss.com/auth.md)
- [Console compatibility authorization guide](https://console.altss.com/auth.md)
- [Console credential management](https://console.altss.com/console/credentials)
- [Altss security](https://altss.com/security)
- [Privacy Policy](https://altss.com/privacy-policy)
- [Console Data License](https://altss.com/legal/console-data-license/2026-10-25.1)

[Read authorization guidance](https://altss.com/auth.md)

[Explore capabilities](https://altss.com/console/capabilities)

## Give your agents a defined job.

Start with the capability, its evidence requirements and the decision your team needs to make. Confirm the available tool and permitted use before execution.

[Read the connection guide](https://console.altss.com/connect)

[Discuss a requirement](https://altss.com/contact)

Canonical URL: https://altss.com/console/security-and-permissions

