Agent-native Dilnaka Cloud
Service accounts
Non-human identities are first-class, revocable, scoped, and attributable.
Credential lifecycle
Create a service account in Settings → Agents, choose scopes and an optional project boundary, then copy the credential once. Only its SHA-256 digest is stored.
- Credentials are shown once.
- Revocation takes effect on the next request.
- Last-use and expiry metadata are visible.
- Create a replacement before rotating a live integration.
Least-privilege scopes
Read and write scopes are separate. Authentication alone never grants administrator access.
apps:read
deployments:create
deployments:read
logs:read
tasks:readTenant isolation
Every request is bound to the service account's organization and optional project. Resource identifiers are re-resolved inside that boundary; cross-tenant identifiers return RESOURCE_NOT_FOUND.