User Management¶
PRO + ENTERPRISE Feature
Multi-user support requires a PRO or ENTERPRISE tier licence.
Manage multiple users with role-based access control for your CertifyClouds deployment.
Overview¶
PRO tier enables multi-user support with:
- Multiple user accounts
- Role-based access control
- SSO auto-provisioning
- Account security features
User Roles¶
CertifyClouds supports two roles:
| Role | Permissions |
|---|---|
| Admin | Full access to all features and settings |
| User | View access to assets, compliance, alerts; cannot modify settings |
Permission Matrix¶
| Feature | Admin | User |
|---|---|---|
| View dashboard | ||
| View assets | ||
| Run Key Vault scans | ||
| View compliance | ||
| View alerts | ||
| View dependencies / blast radius | ||
| View audit logs | ||
| Configure alert rules | ||
| Map dependencies (PRO + ENTERPRISE) | ||
| Verify dependencies (PRO + ENTERPRISE) | ||
| Run rotation (PRO + ENTERPRISE) | ||
| Run full-stack rotation (PRO + ENTERPRISE) | ||
| Configure sync (PRO + ENTERPRISE) | ||
| Manage subscriptions | ||
| Manage users | ||
| Configure SSO | ||
| System settings |
Credential-modifying actions require Admin
Any action that changes a credential or the data driving a rotation - rotation, full-stack rotation, dependency mapping/verification, and multi-cloud sync - requires the Admin role. Users have full read access (dashboards, assets, compliance, alerts, dependency blast-radius, audit logs) and can run Key Vault scans, but cannot perform write or destructive operations.
Managing Users¶
Create User¶
- Go to Settings → Users
- Click Add User
- Enter:
- Username: Unique identifier
- Email: User's email address
- Password: Initial password (must change on first sign-in)
- Role: Admin or User
- Click Create
Edit User¶
- Go to Settings → Users
- Click the edit icon on a user
- Modify:
- Email address
- Role
- Account status (enabled/disabled)
- Click Save
Delete User¶
- Go to Settings → Users
- Click the delete icon on a user
- Confirm deletion
Warning
Deleting a user cannot be undone. Consider disabling the account instead.
The user's sessions stop working immediately. You cannot delete your own account, the built-in admin account, or the last active admin. An SSO user who is deleted can sign in again as a new user while SSO auto-provisioning is on, so disable the account to block access.
Reset Password¶
- Go to Settings → Users
- Click on a user
- Click Reset Password
- Generate or enter new password
- Share with user securely
SSO User Provisioning¶
When SSO is configured, users can be auto-provisioned on first sign-in.
Configure Auto-Provisioning¶
- Go to Settings → SSO
- Enable Auto-create users
- Set Default role for new SSO users
- Save
How It Works¶
- User clicks "Sign in with SSO"
- Authenticates with identity provider
- If user doesn't exist and auto-create is enabled:
- New account created with SSO identity
- Default role assigned
- User signed in
- If user exists:
- Existing account linked to SSO
- User signed in
SSO-Only Mode¶
Disable local password authentication:
- Go to Settings → SSO
- Enable SSO-only mode
- Save
Warning
Keep at least one admin account with local auth until SSO is fully tested.
Account Security¶
Password Requirements¶
Local accounts must meet a configurable complexity policy. Defaults and tuning options are documented in your customer deployment package; ask your administrator for the active policy.
Account Lockout¶
Accounts are temporarily locked after repeated failed sign-in attempts. Threshold and lockout duration are configurable by your administrator (see your customer deployment package for tuning).
Unlock Account¶
Admins can manually unlock accounts:
- Go to Settings → Users
- Find the locked user
- Click Unlock Account
Session Management¶
Maximum session duration and idle timeout are configurable by your administrator.
Audit Trail¶
All user-related actions are logged:
- User created/modified/deleted
- Sign-in attempts (success/failure)
- Password changes
- Role changes
- Account locks/unlocks
View in the Audit Log section of the left-hand navigation, or filter by user.
Best Practices¶
Initial Setup¶
- Create individual accounts - Don't share admin credentials
- Use SSO - Integrate with corporate identity for better security
- Least privilege - Assign User role unless Admin is needed
Ongoing Management¶
- Regular reviews - Audit user list quarterly
- Disable inactive - Disable accounts for departed team members
- Monitor logins - Review audit logs for unusual activity
Security¶
- Enable MFA - Use SSO with MFA enforcement
- Strong passwords - Enforce complexity requirements
- Session limits - Configure appropriate timeouts
API Reference¶
User-management endpoints are part of the authenticated admin API. The full OpenAPI specification is available at /docs on your CertifyClouds deployment, and request/response schemas + example payloads are documented in your customer deployment package.