SHOPAR FOR AGENTS · PUBLIC DOCSIdentity, Permissions, and Safety
Understand which identity a tool uses, how role permissions apply, and why consequential actions need human approval.
Last updated: 2026-10-08Available
The operator's identity
Each operator signs in with their own account. Shared administrator accounts and embedded service credentials are not used. Session credentials stay in the operator's environment and must never be pasted into agent conversations.
Backend permissions
Current back-office roles include admin, moderator, and accountant. Each role may access different areas; a method appearing in client help does not mean that role is allowed to call it.
The backend checks the current role and action permissions for every request. A denial must not be bypassed by switching identities or trying another method.
Consequential actions
Actions that change product, campaign, user, support, finance, or security data must first explain the target and expected result. Tools preserve confirmation steps; an agent prompt alone is not user approval.
Sensitive data
- Do not request, display, or include PWT or refresh tokens in responses.
- Do not place production identifiers, personal data, or signed download URLs in public agent docs.
- Stop on authorization denial or an ambiguous result and report it to the operator.
Agent-readable Markdown
---
title: "Identity, Permissions, and Safety"
summary: "Understand which identity a tool uses, how role permissions apply, and why consequential actions need human approval."
canonical_url: https://shopar.app/agents/docs/en/identity-permissions/
status: available
audience: people,agents
language: English
last_updated: 2026-10-08
---
# Identity, Permissions, and Safety
Understand which identity a tool uses, how role permissions apply, and why consequential actions need human approval.
## The operator's identity
Each operator signs in with their own account. Shared administrator accounts and embedded service credentials are not used. Session credentials stay in the operator's environment and must never be pasted into agent conversations.
## Backend permissions
Current back-office roles include admin, moderator, and accountant. Each role may access different areas; a method appearing in client help does not mean that role is allowed to call it.
The backend checks the current role and action permissions for every request. A denial must not be bypassed by switching identities or trying another method.
## Consequential actions
Actions that change product, campaign, user, support, finance, or security data must first explain the target and expected result. Tools preserve confirmation steps; an agent prompt alone is not user approval.
## Sensitive data
- Do not request, display, or include PWT or refresh tokens in responses.
- Do not place production identifiers, personal data, or signed download URLs in public agent docs.
- Stop on authorization denial or an ambiguous result and report it to the operator.
