Skip to content

Settings

Settings

The Settings page lets administrators configure system-wide behavior: login and session settings, workstation defaults, system log retention, default and environment-specific permissions, and (on cloud deployments) autoscaling. You can manage settings through both the GUI and the CLI.

GUI

Open Settings from the left sidebar by clicking the Settings icon.

The page is organized into five top-level tabs: General, Default ACLs, Environment ACLs, Page ACLs, and Autoscaler.

Some tabs have sub-tabs for more specific configuration.


General

The General tab has the sub-tabs Login, Workstations, System, Help Desk, and NFS Mounts (visible to administrators only).

Login settings

The Login sub-tab controls how users authenticate and how long sessions last.

  1. JWT expiration time Set how long a signed-in session stays valid. Use a duration string, for example:
  2. 10s — 10 seconds
  3. 5m — 5 minutes
  4. 2h — 2 hours
  5. 3d — 3 days

Enter the value in the JWT expiration time field. Shorter values improve security but require more frequent logins.

  1. Enable MFA Turn Enable MFA on to require multi-factor authentication for user logins. When enabled, users must complete a second factor (e.g. TOTP) in addition to their password.

  2. SSO setup details For provider support, required fields, and step-by-step setup instructions, see SSO settings below.

  3. SCIM provisioning See SCIM provisioning below. When SCIM is on, SSO no longer creates users on first login.

  4. Save or discard Click Save to apply changes. If you edited fields but don't want to keep them, click Discard to reset the form to the last saved state.

Changes take effect for new logins and token refreshes; existing sessions may continue until their tokens expire.

SSO settings

Use this checklist to configure and validate SSO end to end.

Current provider support

Datatailr supports Microsoft Entra ID, Auth0, Okta, Duo, and Generic OIDC in the GUI and CLI. Only one SSO provider can be active at a time.

  1. Prepare the identity provider Create the application in your identity provider and collect the values shown in the GUI for that provider. Provider-specific setup is listed under Enable SSO using CLI (optional) below.

  2. Configure SSO in Datatailr GUI

  3. Open Settings -> General -> Login.
  4. Turn on Enable SSO.
  5. Choose SSO provider: Microsoft Entra ID, Auth0, Okta, Duo, or Generic OIDC.
  6. Fill in only the fields shown for that provider:

    Field Microsoft Entra ID Auth0 Okta Duo
    Client identifier Application (client) ID Client ID Client ID Client ID
    Secret Client secret Client Secret Client secret Client Secret
    Tenant / host Directory (tenant) ID Domain Okta domain Issuer host
    Authorization server — — Authorization server ID (optional) —
    Callback Redirect URI Allowed Callback URL Sign-in redirect URI Sign-In Redirect URL
  7. For Generic OIDC, fill in Display name, Issuer URL, Client ID, Client secret, and Redirect URI. Advanced holds the email claim and optional authorize, token, and userinfo URLs, which override discovery. Leave the email claim empty to use email, then preferred_username, then upn.

  8. Redirect URI is filled from the address you opened this page at, plus /sso/callback, when the stored value is empty. Register that exact URI on the identity provider. This applies to every provider.
  9. For Okta, leave Authorization server ID empty to use the Org Authorization Server, or set it (often default) for a Custom Authorization Server.
  10. Click Save.

Datatailr sends a state parameter on the authorize request and checks it on callback.

  1. Verify login flow
  2. Open the login page in a new/private browser session.
  3. Confirm the SSO button is visible.
  4. Click SSO and complete sign-in with the configured provider.
  5. Confirm you are redirected back to Datatailr and land on the application home page.

  6. User provisioning behavior

  7. Datatailr maps SSO users by email address.
  8. If the identity provider includes email_verified and it is false, login is rejected. The browser returns to the login page, which says the email address is not verified. Other SSO refusals, such as a missing email or an account that has not been provisioned, return to the login page with their own message.
  9. If SCIM is off and no Datatailr user exists for the email, Datatailr creates a new user automatically during first successful SSO login.
  10. If SCIM is on, SSO does not create users. The identity provider must provision the account first (see SCIM provisioning below). Disabled or unknown users are rejected.

SSO-only login refuses password sign-in for every account, including root. root cannot use the password form even when SSO-only is off; on the host, dt cli is how that account is used. The settings page offers the switch only after an admin has signed in with SSO. Any admin can turn it off, and dt settings put can change the flag directly.

Enable SSO using CLI (optional)

You can configure login settings via dt settings put. Put replaces the whole login object, so include JWT and MFA values you want to keep.

Microsoft Entra ID:

  1. Create (or reuse) an app registration in your Microsoft Entra ID tenant.
  2. Collect Application (client) ID, Directory (tenant) ID, and Client secret value.
  3. Add a redirect URI of https://your-domain.com/sso/callback.
  4. Apply the settings:
dt settings put login '{"jwt_expiration_time":"12h","mfa":"false","sso_enabled":"true","sso_provider":"microsoft","sso_client_id":"<client-id>","sso_client_secret":"<client-secret>","sso_tenant_id":"<tenant-id>","sso_redirect_uri":"https://your-domain.com/sso/callback"}'

Auth0:

  1. In Auth0, create a Regular Web Application.
  2. Enable the Authorization Code grant type.
  3. Add an Allowed Callback URL of https://your-domain.com/sso/callback.
  4. Collect Domain, Client ID, and Client Secret.
  5. Apply the settings:
dt settings put login '{"jwt_expiration_time":"12h","mfa":"false","sso_enabled":"true","sso_provider":"auth0","sso_client_id":"<client-id>","sso_client_secret":"<client-secret>","sso_domain":"<tenant>.auth0.com","sso_redirect_uri":"https://your-domain.com/sso/callback"}'

sso_domain can be the Auth0 Domain field (tenant.auth0.com or tenant.us.auth0.com) or a custom domain. A leading https:// and trailing / are stripped if present.

Okta:

  1. In Okta, create a Web application.
  2. Enable the Authorization Code grant type.
  3. Add a Sign-in redirect URI of https://your-domain.com/sso/callback.
  4. Collect Okta domain, Client ID, and Client Secret.
  5. Choose an authorization server:
  6. Org Authorization Server: omit sso_authorization_server_id (or leave it empty). Datatailr calls /oauth2/v1/authorize, /oauth2/v1/token, and /oauth2/v1/userinfo.
  7. Custom Authorization Server: set sso_authorization_server_id to the server id (often default, or an aus... id). Assign the application to that server and include the openid, profile, and email scopes. Datatailr calls /oauth2/{id}/v1/authorize, /oauth2/{id}/v1/token, and /oauth2/{id}/v1/userinfo.
  8. Apply the settings.

Org Authorization Server:

dt settings put login '{"jwt_expiration_time":"12h","mfa":"false","sso_enabled":"true","sso_provider":"okta","sso_client_id":"<client-id>","sso_client_secret":"<client-secret>","sso_domain":"<org>.okta.com","sso_redirect_uri":"https://your-domain.com/sso/callback"}'

Custom Authorization Server:

dt settings put login '{"jwt_expiration_time":"12h","mfa":"false","sso_enabled":"true","sso_provider":"okta","sso_client_id":"<client-id>","sso_client_secret":"<client-secret>","sso_domain":"<org>.okta.com","sso_authorization_server_id":"default","sso_redirect_uri":"https://your-domain.com/sso/callback"}'

sso_domain can be the Okta org domain (org.okta.com, org.oktapreview.com, or an Okta custom domain). A leading https:// and trailing / are stripped if present.

Duo:

  1. In the Duo Admin Panel, open Applications → Application Catalog and add Generic OIDC Relying Party (SSO label). Do not use the OAuth 2.1 / OIDC catalog app; that product requires PKCE, which Datatailr does not send.
  2. Enable the Authorization Code grant type.
  3. Add a Sign-In Redirect URL of https://your-domain.com/sso/callback.
  4. Enable the openid, profile, and email scopes.
  5. Collect Client ID, Client Secret, and the Issuer host from Metadata (sso-<tenant>.sso.duosecurity.com).
  6. Apply the settings:
dt settings put login '{"jwt_expiration_time":"12h","mfa":"false","sso_enabled":"true","sso_provider":"duo","sso_client_id":"<client-id>","sso_client_secret":"<client-secret>","sso_domain":"sso-<tenant>.sso.duosecurity.com","sso_redirect_uri":"https://your-domain.com/sso/callback"}'

sso_domain is the Duo SSO host from the Issuer URL (https://sso-<tenant>.sso.duosecurity.com/oidc/<client-id>). A leading https:// and trailing / are stripped if present. Datatailr calls /oidc/{client-id}/authorize, /oidc/{client-id}/token, and /oidc/{client-id}/userinfo.

Use dt settings get login to confirm the stored values. The login page button label follows sso_provider (for example Sign in with Auth0, Sign in with Okta, or Sign in with Duo).

Enable a custom OIDC provider (CLI)
  1. At the identity provider, register Datatailr as a confidential web application with a client secret. Leave "require PKCE" off. Datatailr does not send PKCE.
  2. Add a redirect URI of https://your-domain.com/sso/callback.
  3. Allow the scopes openid, profile, and email. Datatailr always requests those three. The scope list is not configurable.
  4. Copy the issuer URL. It is the issuer whose /.well-known/openid-configuration document describes the provider, for example https://idp.example.com/realms/acme.
  5. Apply the settings:
dt settings put login '{"jwt_expiration_time":"12h","mfa":"false","sso_enabled":"true","sso_provider":"oidc","sso_display_name":"Acme","sso_issuer":"https://idp.example.com/realms/acme","sso_client_id":"<client-id>","sso_client_secret":"<client-secret>","sso_redirect_uri":"https://your-domain.com/sso/callback"}'

sso_display_name is the name on the login button (Sign in with Acme). Leave it empty for Sign in with SSO. The same fields can be set on Settings -> General -> Login by choosing Generic OIDC.

Datatailr fetches {issuer}/.well-known/openid-configuration and uses authorization_endpoint, token_endpoint, and userinfo_endpoint. The issuer value in that document must match sso_issuer. A trailing / is ignored. The issuer and every endpoint must be https.

The email address is read from the ID token. If the token has none, Datatailr calls the userinfo endpoint. A token whose issuer, audience, or expiry does not match is rejected and does not fall through to userinfo. email_verified: false on the token stays false when the email itself comes from userinfo. The claim is the first of email, preferred_username, and upn whose value contains @.

Optional fields:

Field Purpose
sso_email_claim Read the email from this claim instead of the default chain.
sso_authorize_url Use this authorize URL instead of the one from discovery.
sso_token_url Use this token URL instead of the one from discovery.
sso_userinfo_url Use this userinfo URL instead of the one from discovery.

When sso_authorize_url, sso_token_url, and sso_userinfo_url are all set, Datatailr does not fetch the discovery document. When sso_issuer is empty, sso_authorize_url and sso_token_url are required.

A custom OIDC provider uses Sign in with plus sso_display_name, or Sign in with SSO when that field is empty.

SCIM provisioning

SCIM (System for Cross-domain Identity Management) lets an identity provider push user and group lifecycle into Datatailr. There is a single API at https://your-domain.com/scim/v2. It is independent of sso_provider: Microsoft Entra ID and Okta all call the same URLs.

SCIM requires the SSO feature to be included in the license. Turn on Enable SCIM on Settings -> General -> Login, generate a bearer token, and copy the tenant URL.

When SCIM is enabled, SSO login is match-only: users that were not provisioned (or that were disabled) cannot sign in. A SCIM DELETE removes the Datatailr user, including the home directory. Builtin user root and group admin cannot be deleted. Removing the group from provisioning clears its SCIM link and leaves the group in place. dtusers is omitted from SCIM, so an identity provider cannot manage it.

While SCIM is on, users and groups, including membership, can be changed only by the identity provider. Local password, MFA, and API token changes still work. A local change that SCIM refuses is recorded in the audit trail as denied.

Every change the identity provider pushes is in the audit trail too, with the actor scim, the provider's address and the same action a change from the CLI or the GUI gets (user.add, group.add_users, ...). A request with a wrong or missing bearer token is recorded as auth.scim denied.

A SCIM displayName change renames the Datatailr group to the slug of the new name (Engineering Team becomes engineering_team). The SCIM response still returns the identity provider's display name. The admin group cannot be renamed: the request fails and the Datatailr name is left unchanged.

Admin group on Settings -> General -> Login names the identity provider group that drives Datatailr's admin group. The name must match exactly, including capitals. While the setting is set, a provider group named admin is refused. Leave it empty to use a provider group named admin. Set it before that group is provisioned the first time. Before changing it, remove the previously linked group from provisioning so Datatailr unlinks it from admin, then provision the new group.

Microsoft Entra ID

Create the enterprise application in Entra, then point provisioning at Datatailr. Do not edit the attribute list or the provisioning schema. The steps below are the mapping changes that are required; everything else stays at the default.

Creating an application requires Cloud Application Administrator, Application Administrator, or Global Administrator. Application Developer is not enough while user app registration is turned off.

  1. In Datatailr, turn on Enable SCIM, generate a bearer token, and copy the tenant URL (https://your-domain.com/scim/v2).
  2. In Entra, open Enterprise applications → New application → Create your own application. Choose Integrate any other application you don't find in the gallery.
  3. Open Provisioning → New configuration. Set Tenant URL to the Datatailr tenant URL and Secret token to the bearer token. Test the connection, then create the configuration.
  4. Set Settings → Scope to Sync only assigned users and groups.
  5. Open Attribute Mapping → Users. Delete every row except the six below.
Entra attribute Datatailr attribute Matching
mail userName 1
mail emails[type eq "work"].value no
givenName name.givenName no
surname name.familyName no
objectId externalId no
Switch([IsSoftDeleted], , "False", "True", "True", "False") active no

Each assigned user needs an email address. Datatailr stores objectId as the user's external id and uses the mail address as the userName. Leave the active expression as it is: a user who is unassigned from the app is disabled in Datatailr.

Leave the matching attribute to be userName at precedence 1.

  1. Under Users and groups, assign the users and groups to provision.
  2. Use Provision on demand to test. For a group, select the members to add in the dropdown below.
  3. Turn provisioning On. A cycle runs about every 40 minutes.

Removing a group from the application deletes that Datatailr group on a later cycle. Provision the unassigned group on demand to delete it immediately. A user who is no longer assigned to the app is disabled, not deleted.

Okta

In the Okta application, enable provisioning:

  • Tenant URL: https://your-domain.com/scim/v2
  • Secret token: the Datatailr bearer token (paste the secret as-is; Okta does not add a Bearer prefix)
  • Provision users and (optionally) groups
  • Under Provisioning → Integration, leave Import Groups unchecked. Groups are pushed from Okta.

CLI (include existing login fields; put replaces the whole object). Hash the token with SHA-256 hex before storing scim_token_hash:

TOKEN="$(openssl rand -hex 32)"
HASH="$(printf '%s' "$TOKEN" | sha256sum | awk '{print $1}')"
dt settings put login '{"jwt_expiration_time":"12h","mfa":"false","sso_enabled":"true","sso_provider":"microsoft","sso_client_id":"<client-id>","sso_client_secret":"<client-secret>","sso_tenant_id":"<tenant-id>","sso_redirect_uri":"https://your-domain.com/sso/callback","scim_enabled":"true","scim_token_hash":"'"$HASH"'","scim_admin_group":"<group name>"}'
echo "Give this token to the identity provider once: $TOKEN"
Workstation settings

The Workstations sub-tab configures default workstation behavior for all users.

  1. Default Workstation Choose which workstation is shown by default on the Workstations page. Select None (use first available) to let the system pick, or choose a specific workstation from the list.

  2. Idle timeout Set how long a workstation IDE can be idle before it is considered inactive. Use a duration string (e.g. 10s, 5m, 2h, 3d). Enter the value in the Idle timeout field.

  3. Save or discard Click Save to apply; click Discard to revert to the last saved state.

System settings

The System sub-tab controls system log retention and lets you download system logs.

  1. System logs retention period Set how long system logs are retained in blob storage before they are purged. Use a duration string (e.g. 10s, 5m, 2h, 3d). Enter the value in the System logs retention period field.

  2. Download system logs In the Download system logs card, set Time range to download to a duration (e.g. 15m for the last 15 minutes). Click Download to download the logs for that range.

  3. Audit log retention Set how many days audit events are kept, which is how far back the Observability page can look: 365 by default, at most 3650. The card has its own Save. Shortening the window permanently deletes older audit events within a minute. From the CLI: dt settings put audit '{"retention_days": 730}'.

  4. Onboarding tour Turn the guided tour for new users on or off. It is on by default. When it is off, the tour does not open at a user's first login and Take the tour is hidden from the help menu. The card has its own Save. From the CLI: dt settings put onboarding '{"enabled": false}'. See First login.

  5. Save or discard Changes to the retention period are applied when you click Save; use Discard to revert.


Image Retention

The Image retention policy card controls how long Docker images of older compute process versions are kept in the registry, per environment. Retention is disabled in every environment by default, so all images are kept.

Promoting a version copies its image into the next environment. Retention then applies to each environment separately: deleting that version's image in Development leaves the Pre Production and Production copies in place, and jobs there can still pull the image.

  1. Enabled Turn retention on or off for the environment.

  2. Retention type

  3. By Count: keep the newest Max images images of each compute process.
  4. By Time: delete images older than Max age (a duration such as 7d). The newest image is always kept.

  5. Save or discard Click Save to apply; click Discard to revert.

Users roll back a compute process by removing its current version, which needs the previous version's image. With By Count set to 1, older images are deleted, so rolling back is not possible in that environment. Keep at least 2 images where users need to roll back. See Rolling back to a previous version.

Only administrators can view or change these settings.

NFS Mounts

The NFS Mounts sub-tab lets administrators mount their own NFS shares into every job container. Only administrators can see the sub-tab and change the list. The list is global: the same mounts apply to jobs in every environment.

Datatailr does not mount anything on the compute nodes itself. Docker on each node mounts the share through a volume of the local driver with type=nfs, so you only give the server address and the export.

The list shows every mount with its share, its target and whether it is read-only. Click Add New to add a mount, or open a row's menu to Edit or Delete it. The form checks every field while you type and shows what each one accepts. Each mount has:

  • ID — Lowercase letters, digits, - and _, at most 32 characters, unique. It names the Docker volume.
  • NFS server — Hostname or IPv4 address of the NFS server.
  • Export path — Absolute path of the export on the server, e.g. /export/data.
  • Target — Absolute path inside the job container. It must be unique and must not contain or sit under another mount's target.
  • Read-only — Mount the share read-only inside the container. Off by default.

Under Additional settings:

  • NFS version — Auto (default, lets the client and server agree), 3, 4, 4.1 or 4.2.
  • Port — NFS server port, 1–65535. Leave empty for the default.
  • Extra options — Comma-separated NFS mount options. Only nconnect, rsize, wsize, timeo, retrans (with an integer value, e.g. nconnect=4) and soft, hard, nolock, noatime are accepted.

Behavior

  • The share must be reachable from the compute nodes (e.g. over VPN/VPC). Access control on the share (exports, Linux file permissions) is your responsibility.
  • Mounts are applied when a job's container is created, so changes only affect jobs started after saving. Running jobs keep their existing mounts.
  • If the server is unreachable or the export does not exist, the job fails to start with the error reported by Docker.

The same setting is available from the CLI under the key client_nfs. The CLI does not check the values, so prefer the NFS Mounts sub-tab: an invalid mount makes every job fail to start.

dt settings get client_nfs
dt settings put client_nfs '{"mounts":[{"id":"customer-data","nfs":{"server":"10.0.0.5","exportPath":"/export/data"},"mount":{"target":"/data","readOnly":true},"additional":{"version":"4.1","port":2049,"extraOptions":["nconnect=4"]}}]}'

dt settings put replaces the whole list, so include the mounts you want to keep.

Default ACLs

The Default ACLs tab defines the default permissions applied when new KV (key-value) or Blob resources are created. Use the KV and Blob sub-tabs to configure each resource type. For an introduction to permissions, see Permissions.

  • Groups — Add or remove groups and assign Read and Write permissions. Use the Preset dropdown (e.g. Viewer, Full access) to apply a predefined set.
  • Users — Add or remove users and assign Read and Write permissions with the same Preset options.

Changes apply to resources created after you save. Click Save to apply; Discard to revert.


Environment ACLs

The Environment ACLs tab configures who can access compute environments (Dev, Pre, Prod). Use the Dev, Pre, and Prod sub-tabs to set permissions per environment.

  • Groups — Assign groups Read, Write, Operate, Access, and Promote permissions. Use the Preset dropdown (Viewer, Editor, Full access, or Custom) to apply a set.
  • Users — Assign the same five permissions to individual users with the same Preset options.
  • Final Permissions For — Use the dropdown to select a user and see the effective permissions they have for that environment (including group membership). The badges show which permissions apply and how (e.g. from group or direct grant).

Click Save to apply; Discard to revert.


Page ACLs

Autoscaler

The Autoscaler tab configures per-environment autoscaling for cloud deployments (e.g. max CPUs, minimum idle time, preferable VM families). It has sub-tabs for Dev, Pre, and Prod.

Local deployments

The Autoscaler tab is not available on local deployments. The tab is disabled and shows "Not available on local version." Use it when running on a cloud provider (e.g. AWS, Azure, GCP).

When available, you can set:

  • Enabled — Turn autoscaling on or off for that environment.
  • Fallback to other families — Allow scaling to VM families other than the preferable ones when needed.
  • Max CPUs — Maximum number of CPUs for the environment (integer ≥ 0).
  • Minimum idle time — How long a node must be idle before it can be scaled down (duration string).
  • Minimum uptime — Minimum time a node must run before it can be scaled down (duration string).
  • Scale-up cooldown — Minimum time between scale-up attempts for that environment (at least 1m). Provisioning a VM usually takes 2–3 minutes, so setting this too low can overprovision nodes.
  • Preferable families — Search and select VM family names to prefer when provisioning (shown as removable chips).

CLI

Settings can also be managed with the dt settings commands. This is useful for scripting and automation.

Action Command
List all settings dt settings ls
List settings by prefix dt settings ls <prefix>
Get a setting dt settings get <key>
Set a setting dt settings put <key> <value>
Remove a setting dt settings rm <key>
List schemas dt settings ls-schemas
List schemas by prefix dt settings ls-schemas <prefix>
Get a schema dt settings get-schema <key>
Set a schema dt settings put-schema <key> <value>
Remove a schema dt settings rm-schema <key>

Common flags:

  • -p / --pretty — Pretty-print output (e.g. indented JSON).
  • -j / --json — Output as JSON.
  • -v / --include-values — For ls, include values in the listing.
  • -J / --json-enrichened — For put and put-schema, return the created or updated entity as JSON.
  • -o / --offset — For ls and ls-schemas, start at the given offset (default 0).
  • -b / --batch-size — For ls and ls-schemas, maximum results per batch (default 100).

Examples:

# List all settings
dt settings ls

# List settings with values
dt settings ls -v

# Get a specific setting
dt settings get <key>

# Set a value
dt settings put <key> <value>

# Set a value from a file
dt settings put <key> file:///path/to/file.json

# Default ACLs (e.g. for KV) — key under default_acls/ prefix
dt settings get default_acls/kv
dt settings put default_acls/kv file:///path/to/acl.json

# List and get schemas
dt settings ls-schemas
dt settings get-schema <key>
dt settings put-schema <key> <value>