Administrator Guide
Complete guide for Argy administrators: user management, SSO, quotas, audit, and security.
This guide walks you through the day-to-day administration of your Argy tenant.
Accessing the Admin Console
- Log in to portal.argy.cloud
- Click on your avatar in the top right corner
- Select Administration
Note: Only users with the
AdminorPlatform Engineerrole have access to the admin console.
User Management
Inviting a User
- Go to Administration → Users
- Click Invite a user
- Fill in the form:
- Email: user's email address
- Role: select the appropriate role
- Teams: assign to one or more teams (optional)
- Click Send invitation
The user will receive an email with a link to activate their account.
Available Roles
| Role | Description | Permissions |
|---|---|---|
| Admin | Tenant administrator | Full access, user and settings management |
| Platform Engineer | Platform engineer | Module management, Golden Paths, agents |
| Product Manager | Product manager | Product management, roadmaps, approvals |
| User | Standard user | Module usage, Argy Code |
| Approver | Approver | Approval workflow validation |
| Viewer | Read-only | View only, no modifications |
Modifying a User
- Go to Administration → Users
- Click on the user to modify
- Edit the information:
- Role
- Teams
- Status (active/disabled)
- Click Save
Disabling a User
- Go to Administration → Users
- Click on the user
- Click Disable user
- Confirm the action
Important: Disabling immediately revokes all access. Active tokens are invalidated.
SSO Configuration
Argy supports SSO authentication via SAML 2.0 and OpenID Connect (OIDC).
Azure AD Configuration (OIDC)
Step 1: Create an application in Azure AD
- Log in to the Azure portal
- Go to Azure Active Directory → App registrations
- Click New registration
- Configure:
- Name:
Argy - Redirect URI:
https://api.argy.cloud/auth/callback/azure
- Name:
- Note the Application (client) ID and Directory (tenant) ID
Step 2: Create a client secret
- In the application, go to Certificates & secrets
- Click New client secret
- Note the secret value (it won't be visible again)
Step 3: Configure in Argy
- Go to Administration → Authentication → SSO
- Click Configure Azure AD
- Fill in:
- Client ID: the Application ID noted earlier
- Client Secret: the created secret
- Tenant ID: the Directory ID
- Click Test connection
- If the test succeeds, click Enable
Okta Configuration (OIDC)
Step 1: Create an application in Okta
- Log in to your Okta console
- Go to Applications → Create App Integration
- Select OIDC - OpenID Connect and Web Application
- Configure:
- App integration name:
Argy - Sign-in redirect URIs:
https://api.argy.cloud/auth/callback/okta - Sign-out redirect URIs:
https://portal.argy.cloud
- App integration name:
- Note the Client ID and Client Secret
Step 2: Configure in Argy
- Go to Administration → Authentication → SSO
- Click Configure Okta
- Fill in:
- Okta Domain:
your-domain.okta.com - Client ID: the noted Client ID
- Client Secret: the secret
- Okta Domain:
- Click Test connection
- If the test succeeds, click Enable
SAML 2.0 Configuration (Generic)
- Go to Administration → Authentication → SSO
- Click Configure SAML
- Download the Argy metadata (SP Metadata)
- Import them into your IdP
- Retrieve your IdP metadata
- Upload them to Argy
- Configure attribute mapping:
email→ your IdP's email attributefirstName→ first name attributelastName→ last name attributegroups→ groups attribute (optional)
- Click Enable
Enforcing SSO Authentication
Once SSO is configured, you can force all users to use it:
- Go to Administration → Authentication
- Enable Enforce SSO authentication
- Users will no longer be able to log in with email/password
Warning: Keep at least one admin account with email/password access in case of SSO issues.
Branding & Custom Domain (Growth+)
Give your tenant a dedicated brand and portal URL.
Configure a custom portal domain
- Create a DNS CNAME record for your portal subdomain (example:
portal.your-company.com). - Point the CNAME target to
portal.argy.cloud. - In Administration → Settings → Branding, enter your custom domain.
- Save and wait for DNS propagation (up to 24h).
Set your brand name and logo
- In Administration → Settings → Branding, set:
- Brand name
- Logo URL (HTTPS, square PNG or SVG recommended)
- Save to apply across the portal and outbound communications.
LLM Gateway Filters (RGPD)
Admins can tune data filters directly in the portal:
- Go to Administration → Settings → LLM Gateway.
- Choose PII filtering mode: Mask, Block, or Off.
- Choose secret filtering mode: Mask, Block, or Off.
- Select the output policy: Mask output or Block output.
- Save to apply the policy across LLM Gateway requests.
Quota Management
LLM Quotas (Credits)
Credits control LLM Gateway usage. 1 credit = 1 million tokens.
Configure default quotas:
- Go to Administration → Quotas → LLM
- Set quotas by role:
- Admin: unlimited or specific value
- Platform Engineer: e.g., 500 credits/month
- User: e.g., 100 credits/month
- Click Save
Configure individual quota:
- Go to Administration → Users
- Click on the user
- In the Quotas section, modify the value
- Click Save
Configure alerts:
- Go to Administration → Quotas → Alerts
- Configure alert thresholds:
- Warning: e.g., 80% of quota
- Critical: e.g., 95% of quota
- Configure alert recipients
- Click Save
Deployment Quotas
Limit the number of deployments per period:
- Go to Administration → Quotas → Deployments
- Configure:
- Deployments per day: e.g., 50
- Deployments per hour: e.g., 10
- Click Save
Viewing Usage
- Go to Administration → Usage
- View the charts:
- LLM usage by user
- LLM usage by model
- Deployments by product
- 30-day trends
Audit and Logs
Viewing Audit Logs
- Go to Administration → Audit
- Use the filters:
- Period: last 24h, 7 days, 30 days, custom
- User: filter by user
- Action: login, logout, deploy, approve, etc.
- Resource: product, module, user, etc.
Audited Event Types
| Category | Events |
|---|---|
| Authentication | Login, Logout, Failed login, MFA enabled |
| Users | Creation, Modification, Deactivation, Invitation |
| Products | Creation, Modification, Deletion |
| Deployments | Start, Success, Failure, Cancellation |
| Approvals | Request, Approval, Rejection |
| LLM | Request, Quota exceeded, Filter triggered |
| Configuration | SSO modified, Quotas modified, Agent added |
Exporting Logs
- Go to Administration → Audit
- Apply your filters
- Click Export
- Choose the format:
- CSV: for Excel/Google Sheets
- JSON: for SIEM integration
- Download the file
SIEM Integration
To send logs in real-time to your SIEM:
- Go to Administration → Integrations → SIEM
- Configure the webhook:
- URL: your SIEM endpoint
- Format: JSON or CEF
- Events: select the types to send
- Click Test
- If the test succeeds, click Enable
Team Management
Creating a Team
- Go to Administration → Teams
- Click Create a team
- Fill in:
- Name: e.g., "Backend Team"
- Description: team description
- Lead: responsible user
- Click Create
Assigning Members
- Go to Administration → Teams
- Click on the team
- In the Members tab, click Add
- Select the users
- Click Add to team
Assigning Products
- Go to Administration → Teams
- Click on the team
- In the Products tab, click Assign
- Select the products
- Set permissions:
- Read: view only
- Write: modification allowed
- Admin: full management
- Click Assign
Agent Management
Viewing Connected Agents
- Go to Administration → Agents
- View the agent list:
- Name: agent identifier
- Status: Connected, Disconnected, Error
- Last activity: timestamp
- Version: agent version
Creating a New Agent
- Go to Administration → Agents
- Click Create an agent
- Fill in:
- Name: e.g.,
agent-prod-paris - Description: location, usage
- Tags: for routing (e.g., "production", "europe")
- Name: e.g.,
- Click Create
- Copy the token (it won't be displayed again)
Revoking an Agent
- Go to Administration → Agents
- Click on the agent
- Click Revoke
- Confirm the action
Important: Revocation is immediate. The agent will be disconnected and won't be able to reconnect.
Security Settings
Password Policy
- Go to Administration → Security → Passwords
- Configure:
- Minimum length: e.g., 12 characters
- Complexity: uppercase, lowercase, numbers, symbols
- Expiration: e.g., 90 days
- History: e.g., last 5 passwords forbidden
- Click Save
Sessions
- Go to Administration → Security → Sessions
- Configure:
- Session duration: e.g., 8 hours
- Maximum inactivity: e.g., 30 minutes
- Simultaneous sessions: e.g., 3 maximum
- Click Save
IP Restrictions
- Go to Administration → Security → IP Restrictions
- Add authorized IP ranges:
- CIDR: e.g.,
192.168.1.0/24 - Description: e.g., "Paris Office"
- CIDR: e.g.,
- Enable Block unauthorized IPs
- Click Save
Warning: Make sure to include your current IP before enabling restrictions.
Notifications
Configuring Email Notifications
- Go to Administration → Notifications → Email
- Configure events:
- Deployment failed: ✅
- Quota reached: ✅
- New user: ✅
- Pending approval: ✅
- Configure default recipients
- Click Save
Configuring Webhooks
- Go to Administration → Notifications → Webhooks
- Click Add a webhook
- Configure:
- URL: destination endpoint
- Events: select the types
- Secret: for HMAC signature (optional)
- Click Test
- If the test succeeds, click Enable
Backup and Restore
Exporting Configuration
- Go to Administration → Settings → Export
- Select items to export:
- SSO configuration
- Quotas
- Teams
- Policies
- Click Export
- Download the JSON file
Importing Configuration
- Go to Administration → Settings → Import
- Upload the JSON file
- Preview the changes
- Click Apply
Troubleshooting
A user cannot log in
- Verify the user is active in Administration → Users
- Check IP restrictions if enabled
- Review audit logs for login errors
- If SSO, verify the configuration on the IdP side
Quotas are not updating
- Check the billing period in Administration → Quotas
- Quotas reset at the beginning of each month
- Contact support if the issue persists
An agent is not connecting
- Verify the token has not been revoked
- Check network connectivity to
api.argy.cloud:443 - Review the agent logs
- Regenerate a new token if necessary