Organisation Settings

Organisation Settings is where platform-wide configuration is managed. These settings apply to your entire SenseOn tenant and affect every user, device, and integration.

Scope: Most operational behaviour is controlled at the Device Segment level rather than at the organisation level. Use organisation settings for platform-wide policies such as MFA enforcement, notification defaults, and feature toggles.

Accessing Organisation Settings

Navigate to Settings > Organisation. This view requires the Admin role.

Settings Categories

Authentication

Settings that affect how users log in to the platform.

Setting	Description
Require MFA for all users	When enabled, every user must enrol a TOTP device before they can access the platform. Active Response users have MFA enforced regardless of this setting.
Session timeout	How long an idle session remains valid before requiring re-authentication.
Step-up authentication window	How long a step-up authentication remains valid before another challenge is required for sensitive actions.

Notifications

Default behaviour for end-user and operator notifications.

Setting	Description
Default end-user notifications	Sets the default for whether endpoints display toast notifications to users. Can be overridden per segment.
Slack workspace URL	The Slack workspace to send case notifications to. See Slack Integration.
Operator email address	Default address for operational notifications (system health, credit alerts, etc.).

Case Defaults

Setting	Description
Default case assignee	The user new cases are assigned to by default. Leave empty to leave cases unassigned.
Auto-close trusted false positives	When enabled, observations classified as Benign True Positive by Reflex automation are auto-closed without analyst intervention.
Reflex enabled	Master toggle for automated case-response actions. See Reflex.

UI Visibility

Controls which modules and features are visible in the navigation for users in your organisation. Disabling a module here hides it from all users, useful when a feature has been purchased as an add-on for only part of an organisation.

Setting	Effect when disabled
Hide Reveal	Reveal module is removed from the main navigation
Hide Reporting	Reporting section is removed from Settings
Hide Knowledge Graph	The Knowledge Graph tab is not visible in case detail panels

Feature Flags

A list of platform feature flags that can be toggled per organisation. Feature flags are typically used to enable new capabilities ahead of general release. Your customer success representative will let you know when a flag is available for your tenant.

Editing a Setting

Go to Settings > Organisation.
Navigate to the relevant category tab.
Change the setting value.

Each field saves itself. There is no page-level Save button and no confirmation step. Toggles and dropdowns save as soon as you change them, and free-text and numeric fields save shortly after you stop typing. While a save is in progress the field header shows Saving, followed by Saved once it completes. The Saved indicator clears after a few seconds.

When a field holds a value that has not reached the server, its header shows an amber Not saved status instead. This appears in three cases: the value you have entered is invalid and cannot be saved, a collection field has a staged edit still waiting for its Save button (see below), or a save has failed. The status clears once the value is valid and saved.

If a save fails, the field header shows Not saved and an error message appears above the field value with a Click to try again. button that sends your change again. Your value stays in the field so you do not lose it.

Note: Collection fields, such as a list of values, stage your edits locally and provide their own Save and Revert buttons in the field footer. Save stays disabled until you change the value and while any entry is invalid, and Revert discards your unsaved edit. While an edit is staged, the field header shows Not saved.

Unsaved changes: If you navigate away from the settings page while any field still shows Not saved, your browser warns you before leaving so you can go back and resolve the change. Leaving anyway discards the unsaved edit.

Most settings take effect immediately. Some endpoint-side settings (for example, notification defaults) propagate to devices on their next check-in.

Defaults and resetting

When a setting's value differs from its default, a Modified badge appears next to its title. Hover over the badge to see the default value. To return a setting to its default, use the field's reset action. This reads Reset setting when the default has a value, or Clear setting when the default is empty.

Note: The Modified badge and the amber Not saved status are separate indicators. Modified means the saved value differs from its default. Not saved means an edit has not yet reached the server. A field can show either, both, or neither.

Audit Trail

All changes to organisation settings are recorded in the Audit Log with the action category settings, including the user who made the change, the setting key, and the previous and new values.

API Access

Organisation settings can also be read and updated through the API. Authentication may require an API key or an endpoint key in addition to a standard user session, depending on the setting being modified. See the API Reference for details.