Feature Sets: Control Company Availability

Overview

Feature Sets controls which groups of Spotto capabilities are available to a company. It sits before user permissions: a role cannot grant access to a feature that the company does not receive.

This page appears only when feature-set management is available to the selected company and your role can view or manage it.

Where to find it

In the Spotto Portal, open a company and go to Settings -> Feature Sets.

• View access lets you inspect effective states and sources.
• Manage access lets you change company overrides and save them.

Read the feature-set table

Column	Meaning
Feature Set	The customer-manageable bundle and the features it contains.
Effective State	Whether the bundle is Enabled, Disabled, or Restricted after defaults, local decisions, and parent decisions are evaluated.
Source	Whether the current state comes from the Default, This company, or a Parent company.
Company Override	The decision this company applies instead of inheriting.
Applies To	Which audience receives the local decision.
Presentation	How a denied feature is shown in the Portal.

Every feature set stays in its normal position. A feature set restricted by a parent is muted, marked Restricted by company, and read-only. The tooltip identifies the company where the decision must be changed. Recommendation-category feature sets are grouped under Recommendation categories so they are easier to scan.

Choose an override

The Company Override choices are:

Choice	Result
Default	Remove the local override and use the nearest parent decision or the system default.
Allow	Enable the feature set for the selected audience.
Restrict	Block descendant companies from receiving the feature set.
Deny	Disable the feature set for the selected audience.

An inherited parent restriction is read-only in a child company. Change it at the parent that supplied the restriction instead of trying to override it lower in the hierarchy.

Control a feature-set plan

Use the two existing controls together for centrally managed plans such as Bronze, Silver, or Gold:

1. At the plan company, set feature sets outside the tier to Restrict. Descendant companies cannot override that decision.
2. At each customer company, keep Company-managed Feature Sets disabled. Customer administrators then cannot manage feature sets themselves.

For example, a Bronze plan can restrict the Security and Compliance recommendation categories for company users. Upgrade a customer by moving it under the Silver or Gold plan company rather than adding customer-specific overrides.

Review change history

The Change history tab records feature-set override events. Each entry identifies the feature set, action, administrator, and time, and retains the previous and resulting configuration for operational review. Historical lock and unlock events remain visible for older records, but there is no longer a live lock control. If history cannot be loaded, use Retry rather than treating the table as empty.

Audit entries are append-only. They are not editable from the Portal.

Manage Kanban Board separately

Kanban Board is an independent feature set. Disabling Cost Optimization no longer implicitly controls the tracked-recommendations board, and changing Kanban Board availability does not change recommendation discovery or cost-analysis availability.

Choose who the decision applies to

For a local override, Applies To can be:

• Everyone
• Company users
• Parent administrators

Use the narrowest audience that matches the intended rollout. Feature availability and role permissions are both evaluated, so an allowed feature set does not by itself grant every action to everyone in that audience.

Choose denied-feature presentation

When the override is Deny, the presentation can be:

• Hidden: do not show the feature.
• Teaser: show a non-actionable preview.
• Promo: show non-actionable rollout or availability information.

Teaser and promo states do not grant data or action access. Server-side authorization remains authoritative even when a feature is visible.

Save changes

1. Review the current Effective State and Source.
2. Select a company override.
3. Choose Applies To when the decision is local.
4. For Deny, choose the presentation mode.
5. Select Update to save all pending changes, or Cancel to discard the drafts.

The Portal refreshes evaluated access after the update. Navigation and page access change when the refreshed state loads.

Troubleshooting

A restricted row cannot be edited

What you're seeing: The row is restricted and has no editable override control.

Likely cause: A parent company supplied the restriction.

How to fix:

1. Check the row's Source.
2. Open the parent company that supplied the decision.
3. Change the parent restriction only if descendants should be allowed to receive the feature.

The controls are read-only

What you're seeing: You can open Feature Sets but cannot change a value.

Likely cause: Your role has view access but not manage access.

How to fix: Ask an administrator to review your role and scope in Users.

A user still cannot open an enabled feature

What you're seeing: The feature set is enabled, but a user cannot open the feature.

Likely causes:

• The user's role does not include the required action.
• The role scope does not include the selected company.
• The user is outside the audience selected under Applies To.

How to fix: Review the user's role and scope, then use Portal Access and Permissions to trace the effective result.