Enterprise Settings¶
Enterprise Settings is where you configure your organisation's profile, branding, and operational preferences in DIBOP.
Accessing Enterprise Settings¶
Navigate to SETTINGS > Enterprise Settings in the sidebar. You must have the Enterprise Admin role or higher to access this page.
Organisation Profile¶
Basic Information¶
| Setting | Description |
|---|---|
| Enterprise Name | Your organisation's display name, shown in the sidebar and reports |
| Enterprise ID | A read-only unique identifier assigned when your enterprise was provisioned |
| Primary Contact Email | The email address used for system notifications and alert escalations |
| Support URL | A link to your internal support portal (shown in help menus) |
Logo¶
Upload your organisation's logo to replace the default DIBOP logo in the sidebar and on reports. Supported formats: PNG, SVG, JPEG. Recommended size: 200x50 pixels.
Timezone¶
Set the timezone used for all timestamp displays throughout the platform:
- Execution timestamps
- API call timestamps
- Alert firing times
- Report date ranges
User-Level Override
Currently, timezone is set at the enterprise level. All users in your enterprise see the same timezone. User-level timezone overrides are planned for a future release.
Branding¶
Customise the look and feel of your DIBOP instance:
| Setting | Description |
|---|---|
| Primary Colour | The main accent colour used in the sidebar and buttons |
| Secondary Colour | Used for highlights and secondary actions |
| Default Theme | Set whether new users start with Light or Dark mode (users can override) |
| Sidebar Title | Custom text displayed at the top of the sidebar (defaults to "DIBOP") |
Brand Consistency
Setting your primary colour to match your corporate brand makes DIBOP feel like an integrated part of your technology stack rather than a third-party tool.
Data Retention¶
Configure how long DIBOP retains different types of operational data:
| Data Type | Default Retention | Configurable Range |
|---|---|---|
| Execution logs (metadata) | 90 days | 30 - 365 days |
| Execution payloads (input/output data) | 30 days | 7 - 90 days |
| API call logs (metadata) | 90 days | 30 - 365 days |
| API call payloads (request/response bodies) | 30 days | 7 - 90 days |
| Dead letter queue | 30 days | 7 - 90 days |
| Alert history | 180 days | 30 - 365 days |
| Audit logs | 365 days | 90 - 730 days |
Changes to retention settings take effect immediately. Data older than the new retention period is purged in the next cleanup cycle (runs daily).
Reducing Retention
If you reduce a retention period, data older than the new limit will be permanently deleted within 24 hours. This cannot be undone.
See Retention Policies for more detail.
Notification Preferences¶
Configure default notification settings for your enterprise:
Alert Notification Defaults¶
| Setting | Description |
|---|---|
| Default Email Recipients | Email addresses that receive all alerts by default |
| Default Webhook URL | A webhook URL that receives all alerts by default |
| Digest Frequency | How often to send a consolidated alert digest (never, daily, weekly) |
Individual alert rules can override these defaults with their own notification settings.
System Notifications¶
| Setting | Description |
|---|---|
| Maintenance Notifications | Receive alerts about scheduled DIBOP platform maintenance |
| Security Notifications | Receive alerts about security-relevant events (failed logins, role changes) |
| Usage Notifications | Receive warnings when approaching quotas or limits |
Security Settings¶
Session Configuration¶
| Setting | Description | Default |
|---|---|---|
| Session Timeout | Inactivity period before auto-logout | 4 hours |
| Max Sessions per User | Maximum concurrent sessions per user account | 5 |
| Remember Me Duration | How long "remember me" sessions persist | 30 days |
Authentication Requirements¶
| Setting | Description | Default |
|---|---|---|
| Require 2FA | Whether two-factor authentication is mandatory for all users | Recommended but optional |
| Password Policy | Minimum length, complexity requirements, rotation period | 12 chars, 1 upper, 1 number |
| SSO Only | When enabled, password-based login is disabled entirely | Disabled |
See SSO / Identity for SSO configuration.
API Access¶
API Keys¶
Enterprise administrators can generate API keys for programmatic access to the DIBOP API. API keys are scoped to your enterprise and inherit the permissions of the user who created them.
To generate an API key:
- Click Generate API Key
- Give it a descriptive name (e.g., "CI/CD Pipeline", "Monitoring Integration")
- Set an expiration date (optional but recommended)
- Copy the key immediately -- it will not be shown again
To revoke a key, find it in the list and click Revoke.
Webhooks¶
Configure incoming webhook endpoints that can trigger orchestrations from external systems:
- Click Add Webhook Endpoint
- Configure the endpoint URL path and authentication
- Map the webhook to a specific orchestration
- Save and activate
Audit Log¶
View a log of all administrative actions taken in your enterprise:
| Action | Details Recorded |
|---|---|
| User created/deleted | Who, when, by whom |
| Role changed | Which user, old role, new role, changed by |
| Credential updated | Which connection, when, by whom (value not logged) |
| Alert rule changed | Rule name, what changed, by whom |
| Settings changed | Which setting, old value, new value, by whom |
The audit log is read-only and cannot be modified or deleted. Retention is governed by the audit log retention setting.
Next Steps¶
- User Management -- add and manage users
- Roles & Permissions -- understand what each role can do
- Retention Policies -- detailed retention configuration
- SSO / Identity -- configure single sign-on