1.0
Control the workspace baseline
Settings define the default review posture, notification routing, retention rules, and integration readiness.
- Approval modes
- Notification targets
- Retention
Home
Resource
Workspace settings
Approval defaults, notifications, member roles, retention, usage controls, and billing limits for the whole support workspace.
Defaults
Workspace
Teams set operating posture once.
Access
Roles
Members receive explicit permissions.
Limits
Hard
Usage and billing controls stay enforceable.
2.0
Separate billing from runtime enforcement
Plans and top-ups can live in billing, while the app ledger enforces AI usage and sending caps in real time.
- Usage caps
- Auto top-up limits
- Billing warnings
Operations
What this means in production.
These pages describe the product contract behind the UI, not a decorative brochure. Each surface should connect back to the same governed support loop.
Control boundary
Workspace access is derived from session membership.
Operator workflow
Support moves through secure ingest, AI preparation, human approval, outbound execution, and audit evidence.
Configuration impact
Provider setup, project policies, knowledge trust, retention, and billing limits decide how this behaves for a real workspace.
Proof points
Designed for governed support, not hidden autonomy.
Workspace access is derived from session membership.
Settings changes are auditable.
Secrets are never shown in the browser.
References
Official stack and legal references.
These external links point to provider documentation, privacy notices, data-processing terms, or platform terms that shape production operation.
Next