Missing product access

Overview

In Ottili ONE, roles, permissions and entitlements* together decide which product or module you can see and use. Access is always explicit and company-scoped (company_id): there is no global, cross-company access and no implicit inference of a company context. When a product is missing, it is almost always one of three layers — role, entitlement (plan/add-on) or product status — or the wrong company context.

This article lists the most common causes and walks you through checking access step by step. It applies to every Ottili ONE surface: Ottili Console, Workspace, Ottili HQ, Ottili AI, Ottili Files, Ottili Flows, LD3, Ottili Coder, Ottili Cloud and the Module Store.

Possible causes at a glance

1. The module is not activated for your company

Most products in Ottili ONE are modules* that are activated per company. If a module is not active, you will not see it in navigation or in module areas.

• Open the Module Store* (module management) in the Ottili Console.
• Check whether the module you are looking for has the status Active* for your current company.
• Activating modules is a role-gated action — you typically need the Owner* or Admin* role.
• On activation, the platform automatically grants the module's default permissions* to the Owner*, Admin* and Manager* roles, so the module is usable immediately.

Which module can be activated in which workspace is covered in [Workspace and modules](/docs/workspace-and-modules). The roles themselves are described in [Roles and permissions](/docs/roles-and-permissions).

2. Your role lacks access

Even when a module is active, your role* decides what you can see and do in it. Ottili ONE uses five roles: Owner*, Admin*, Manager*, Employee* and Viewer*.

• Viewer* and Employee* can use modules but cannot change company-wide settings or activate modules.
• If you lack a permission, the action ends clearly with an error — nothing happens in the background.
• Ask an Owner* or Admin* to review and, if needed, adjust your role in the Team* area.

The exact permission split per role is in [Roles and permissions](/docs/roles-and-permissions).

3. The entitlement engine is missing the grant (plan or add-on)

On top of roles, the entitlement engine* decides deny-by-default which features are available to a company at all. For exactly one explicit company context it combines:

• the company's plan*,
• purchased add-ons*,
• approved trials*,
• the Free-Forever* inclusion,
• administrative grants*,
• region,
• product status*, and
• company suspension*.

If your plan does not include a module or feature, it is not available to the company — even if the module is activated. Which modules your plan can activate and how many credits are included is explained in [Understand plans and credits](/docs/understand-plans-and-credits). When a company is suspended, or a region/product is blocked, the capability is denied by default. The combined effect of roles and entitlements is described in [Shared permissions and entitlements](/docs/shared-permissions-and-entitlements).

4. Wrong company context

Ottili ONE is strictly company-scoped. If you belong to multiple companies, you only see the products and modules of the currently selected company*.

• Switch your active company from the company switcher* in the top bar (the building icon). Choose the company you want to work in.
• Make sure you are an active* member of the target company.
• Check whether the module is activated in the correct company — modules and permissions are company-specific.

Background: [Company and team](/docs/company-and-team) and [Tenant isolation](/docs/tenant-isolation).

5. Private Beta or Early Access (invite only)

Some features or products are in a Private Beta* (feature level) or an Early Access* (product level) and are available only to invited groups. This is intentional, deliberately narrow availability — not a bug.

• One example is Ottili Cloud*: Compute is reachable through an Early Access program while further categories such as Storage and Networking are still *Planned*.
• If you are not invited, the product will not appear in your account.
• Express interest in an Early Access program through the relevant product page or support; invitations are sent by the Ottili ONE team.

The difference between open beta, Private Beta and Early Access is explained in [Product lifecycle and feature status](/docs/product-lifecycle-and-feature-status) and [Understand feature-status labels](/docs/understand-feature-status-labels).

6. The product is not available yet (In Development, Planned, Concept)

Not every product mentioned in the docs or on the website is usable yet. The maturity labels are consistent everywhere:

• Live / Available* – generally available and fully supported.
• Beta* – publicly usable in a pre-release state.
• Private Beta / Early Access* – only for an invited group.
• In Development* – actively being built, not yet available.
• Planned* – scheduled but not yet started.
• Concept* – early idea, no delivery promise.

If a product or feature is *In Development*, *Planned* or *Concept*, it cannot be activated yet — that is expected. Current status is shown on the public status page and in the Console. The meaning of each label is in [Understand feature-status labels](/docs/understand-feature-status-labels) and [Product lifecycle and feature status](/docs/product-lifecycle-and-feature-status).

Step by step: check access

1. Check company context* – switch to the right company using the company switcher in the top bar.

2. Check module status* – is the module Active* in the Module Store for this company?

3. Check your role* – does your role allow the action you want? Ask an Owner/Admin to adjust it in the Team* area if needed.

4. Check plan/entitlement* – is the feature included in the plan or bought as an add-on? See Settings → Billing*.

5. Check status* – is it a Private Beta / Early Access (invite required) or *In Development*/*Planned*/*Concept* (not available yet)?

6. Contact support* – if everything checks out and access is still missing, contact your Company Admin or Ottili ONE Support and provide the product name, your company and your role.

Common error messages

• "No permission" / 403* – your role or entitlement does not allow the action. Review role or plan.
• Module not visible* – either not activated, wrong company context, or not included in the plan.
• Feature greyed out* – entitlement missing (plan/add-on) or product status restricts usage.
• "Not available in your region"* – the entitlement engine denies by default for blocked regions/products.

Related articles

• [Roles and permissions](/docs/roles-and-permissions)
• [Shared permissions and entitlements](/docs/shared-permissions-and-entitlements)
• [Understand plans and credits](/docs/understand-plans-and-credits)
• [Company and team](/docs/company-and-team)
• [Understand feature-status labels](/docs/understand-feature-status-labels)
• [Product lifecycle and feature status](/docs/product-lifecycle-and-feature-status)
• [Workspace and modules](/docs/workspace-and-modules)