Settings
Configure security, access, and integration settings for your Zijus agent.
Secrets Management
Overview
Securely store sensitive credentials (API keys, tokens, etc.) for workflow use. Secrets are:
- Encrypted at rest with AES-256
- Never exposed in logs or LLM interactions
- Accessible only via the GetSecret tool
Creating a Secret
- Navigate to Settings > Secrets
- Click + Add Secret
- Provide:
- Name: Reference for workflows (e.g.,
stripe_api_key) - Value: The sensitive data
- Description (Optional): Usage context
Usage in Workflows
# Correct usage
api_key = await CallTool('GetSecret', SECRET="stripe_api_key")
# Avoid (logs values):
print(api_key)
Management
- Deletion:
- Blocked if referenced in active workflows
- Requires workflow modification first
- Audit: All accesses are logged
Token Management
Token Types
| Type | Use Case | Max Validity |
|---|---|---|
| API | Third-party integrations | 1 year |
| Agent email communication | 2 years | |
| Widget | Embedded chat sessions | Unlimited |
Creating Tokens
- Go to Settings > Tokens
- Click Generate New Token
- Specify:
- Name (e.g., "CRM Integration Token")
- Expiry date
- Description (optional)
Security Practices
- đ Tokens are displayed once upon creation
- âŗ 7-day expiry notifications
- đī¸ Immediate revocation available
Access Control (RBAC)
Current Roles
| Role | Capabilities |
|---|---|
| Admin | Full system control |
| Developer | Create/edit workflows |
| Analyst | View analytics only |
Granting Access
- Admin navigates to Settings > Users
- Enters target user's work email
- Selects role from dropdown
- Clicks Grant Access
âšī¸ Users must re-login to apply new permissions
Upcoming Features
- Custom role creation
- Permission granularity controls
Widget Configuration
Embedding Steps
- Navigate to Settings > Widget
- Customize:
- Colors: Match your brand
- Icons: Upload custom logo
- Features: Toggle file upload/voice input
- Click Get Code
- Paste generated script in website
<body>
Example Output:
<script>
window.zijusWidget = {
agentId: "AGN-12345",
theme: {
primaryColor: "#3a86ff",
headerText: "Support Assistant"
}
};
</script>
<script src="https://cdn.zijus.com/widget/v2.js" async></script>
Email Settings
Setup Process
- Create a long-lived token (Settings > Tokens)
- Navigate to Settings > Email
- Configure:
- Display Name: "Acme Support Bot"
- Footer Text: "This is an automated message"
- Access Control:
- Public (all senders)
- Domain-restricted (e.g., "@company.com")
- Allowlist (specific emails)
Security Notes
- đ Token must be active
- âī¸ Email-bound tokens can't be deleted
- đ Inbound emails are scanned for spam
Sample Email Flow
sequenceDiagram
User->>Agent: Email to agent@zijus.com
Agent->>Workflow: Triggers email_handler
Workflow->>User: Sends response
Best Practices
- Secrets
- Rotate quarterly
- Use descriptive names
-
Never hardcode in workflows
-
Tokens
- Set minimum viable validity
- Revoke unused tokens
-
Store securely (e.g., password manager)
-
Access Control
- Follow principle of least privilege
- Audit quarterly
- Use SSO where possible
Troubleshooting
| Issue | Solution |
|---|---|
| Can't delete secret | Check workflow dependencies |
| Token not working | Verify expiry date |
| Widget not loading | Check browser console for errors |
| Email delays | Review agent's workflow latency |