Organization Profile
Last updated
Last updated
The organization profile contains key information about the system settings, gateway sessions, limits and other system behaviors.
Also referred to as the Workspace Name, this is the label that will be displayed in navbar on hover.
Global controls can be found here, including connection controls for systems, gateway controls, and quota enforcement.
This section is only available on the Enterprise license tier.
This settings determines how many concurrent sessions any one given gateway will handle:
A gateway is any individual named instance in the organization/workspace (there may be none, one, or many)
A session is an individual query request (thus sessions do not persist while a user is in chat, freeing allocation for another user)
Any queries/sessions in excess of this limit will be queued until other requests/sessions complete.
If set to zero there will be no limit on queues.
A limit on "query costs" can be imposed by system (if it is supported, see Source System Integrations for more details).
The query cost is calculated on the target query inclusive of any unaliasing (i.e., abstraction reversal) CTE's that must be applied. The exact calculation and magnitude/scale depends on the system specifically.
Query Cost Limits apply across all underlying Knowledge Bases.
Any query that exceeds the Query Cost Limit for the organization/workspace will not be executed (and if in the Chat or other user-oriented interface, will be mentioned to the user).
A non-existent or 0 cost implies no limit. This is the default and is suitable if:
There is no concern over query cost (e.g., source system is small, data warehouse can comfortably accommodate large queries)
Other controls at the system exist (e.g., throttling controls)
The Query Duration Limit is relied upon instead
Outside of these cases, it is recommended that controls be applied, even if the threshold is very high.
An alternative to "query costs", this limits the duration of the query/session instead.
This is an effective alternative/complement to the previous control if:
An additional safeguard is warranted
Query Cost Limit is not available for the target system
Distinct from Query Cost Limits, Query Duration Limit will allow the execution of the query until the metric is exceeded.
This determines the maximum number of records returned for each Lumi query by default. This setting ensures that query results are manageable and tailored to user needs.
Default Limit: The system is preset to return a maximum of 25 records per query.
Customizable Options: Depending on preferences or use cases, this limit can be adjusted to 50 or 100 records.
This toggle governs whether the license/plan limit for requests is to be strictly enforced or allowed to be exceeded.
Behaviour of the toggle:
Off: (Default) Once the limit is reached, users will be warned and administrators must upgrade to another plan
On: Once the limit is reached, a charge will be applied at the next billing cycle for the next bundle of allotment for requests
