Organization Settings

Feature flags

Some Kenseme features are optional. They sit behind feature flags so an organization can turn them on when it’s ready. Organization admins manage them on the Features tab. Changes take effect immediately; there’s nothing to publish or restart.

In the app: Settings › Organization Settings › Features tab

[screenshot]
The Features tab listing each optional feature with its description and Enabled switch, one of them locked on as included in the plan.

Before you start

You need the Admin role.

The optional features

Feature What it turns on Needs
Bind to Database Binding ontology entities to tables and columns in external relational databases (SQL Server, PostgreSQL, MySQL, Databricks, Fabric Warehouse, Fabric Lakehouse) through saved connections. See Bind an ontology to a database. —
Data Agent Asking for data in plain English against database-bound ontologies. The agent writes and runs read-only queries. See Data Agent. Bind to Database
Ontology Data MCP Exposing an ontology as an MCP endpoint so an MCP client can ask business questions answered from the ontology’s database bindings. See Expose an ontology over MCP. Data Agent
Industry Standards Browsing industry standards such as GS1, UNSPSC, and ADRM, and using them as grounding and sources for ontology generation. See Industry standards. —
Star Schema The Star Schema tab on a schema, for planning dimensions and facts and generating their tables, views, and load procedures. See Star schema overview. —
Fabric Sync Synchronizing ontologies and bindings with Microsoft Fabric ontology items: pull, push, and round-trip sync. See Sync an ontology with Fabric. —

Note: Saved database connections, importing a schema from a connection, and generating an ontology from a database work whether or not Bind to Database is on. The flag controls ontology binding only.

Turn a feature on or off

  1. Find the feature’s row.
  2. Flip its Enabled switch.

Kenseme confirms with a message such as “Star Schema enabled for this organization.”

Features your plan includes

Some plans include certain features. An included feature shows its switch locked on with a caption such as “Included in Business”. You can’t turn it off while you’re on that plan.

Plan Includes
Trial Bind to Database, Data Agent, Star Schema
Team None; turn features on yourself
Business Bind to Database, Data Agent, Star Schema
Enterprise Bind to Database, Data Agent, Star Schema, Industry Standards, Fabric Sync

Features your plan doesn’t include can still be switched on here, and they stay on when you change plans.

If the subscription lapses (the trial ends, it’s canceled, or a payment stays overdue), the plan’s included features stop applying and only the features switched on here remain. Organizations created before plans existed aren’t affected. See Plans and pricing and Account states and read-only mode.

How dependencies work

Three of the features build on each other: Ontology Data MCP needs the Data Agent, and the Data Agent needs Bind to Database. Kenseme keeps them consistent for you:

  • Turning a feature on also turns on everything it needs. Enabling Ontology Data MCP enables the Data Agent and Bind to Database too.
  • Turning a feature off also turns off everything that needs it. Disabling Bind to Database disables the Data Agent and Ontology Data MCP.

The confirmation message names every feature that changed, for example: “Data Agent enabled. Bind to Database was also enabled because Data Agent requires it.”

Site administrators

Macula staff can set the same flags for any organization from System Administration › Feature Flags. See System administration.