Factorial Docs

Appearance

Organization Settings ​

  Table of Contents

Organization settings control workspace-wide behavior in Factorial. These settings apply across the organization and should be managed by users responsible for administration, quality, or process governance.

Review and Approval ​

An organization configures the approval requirements used for controlled changes. These requirements allow each organization to match Factorial's review workflow to its own quality system. Read more on reviews and approvals.

The procedure review policy sets how many approvals a procedure revision requires before it can be released. The default is one approval. A value of zero allows release without approvals, although outstanding change requests still block release.

Only administrators can change the review policy. A change takes effect immediately, including for revisions already in review. Factorial keeps every earlier policy along with who changed it and when.

Administrators change the required number of approvals on the Settings page under Organization. Other users can view the current requirement there. The policy can also be changed through the API with PATCH /api/v1/review-policies.

The review policy is the only thing that decides how many approvals a revision needs. Asking specific people to review a revision notifies them and puts it in their review center, but it does not add to the requirement.

Approvals from a revision's owner or submitter never count. An organization in which only one person can approve procedures must either add another user with the Approve procedure permission or set the required number of approvals to zero before it can release procedures.

The redline review policy sets how many approvals a work order redline requires before it can be applied. It works the same way as the procedure policy and is changed in the same place: the default is one approval, zero allows applying without approvals, and approvals from the person who opened or submitted the redline never count. Only reviews from users with the Approve redline permission count.

The disposition review policy sets how many approvals an issue disposition or NCR cancellation requires before it can be applied. It works the same way as the redline policy. Only reviews from users with the permission the disposition's type requires count, and only reviews from users with the Disposition permission count toward a cancellation.

The disposition review policy is planned and not yet available. See issues.

LLM Features ​

Analytics can write SQL from a question in English, asked with an API key from Anthropic, OpenAI, or Gemini. Factorial sends the provider only the analytics views and columns and the question, never rows or results. No Factorial feature sends data to an LLM on its own.

Administrators control LLM features in the LLM features section of organization settings. Other users can view the current settings there.

LLM features decides which keys may ask:

  • On, with personal and organization keys, the default. People may ask with keys of their own or the organization's.
  • On, with the organization's keys only. People's own keys are kept but cannot be used, added, or edited.
  • Off disables Ask everywhere. Saved keys are kept, and SQL still runs.

Nothing is sent to a provider until someone saves a key. Factorial keeps every earlier setting along with who changed it and when.

Analytics is the only feature that uses LLM keys today. A future feature that sends more than the analytics schema and a question, such as rows or execution records, will get its own setting here rather than turning on under LLM features.

Organization Keys ​

Organization keys are API keys the organization pays for, saved by administrators. Anyone with the Analytics permission can ask with them, using any of the provider's models. A provider's balanced model, which each question starts on, is usually enough to write a query.

Each organization key needs its own name. To rename a key or paste a new one, select Edit under it. Leave the key blank to keep the saved one. Factorial does not track usage or set quotas. Use the provider's own usage limits and billing alerts for that.

Plugin Approval Requirements ​

Approval requirements for enabling a plugin can only be configured from Organization Settings. A plugin cannot govern the review of another plugin. Plugins may govern reviews for other supported entities by adding automatic review requirements.

Allow/Disallow Projects in Your Org ​

Projects allow one-off work to proceed without a released procedure. An organization can disable projects when its policies do not permit that type of ad hoc execution.

Barcode Templates ​

Barcode templates define the human-readable information printed beside a QR code. Organization settings manage the templates available for supported entity types, such as inventory, tools, and locations. See Barcode Templates for details.

Part Interchangeability ​

Part interchangeability controls whether Factorial automatically creates global substitute relationships for parts in the same part group. The setting provides three options:

  • Off is the default. Factorial does not automatically create global substitutes. Turning the setting off does not remove global substitutes that Factorial created previously.
  • New parts only creates global substitutes when new parts are added to part groups. It does not modify existing parts.
  • Backfill part groups creates global substitutes for parts already assigned to part groups.

Global substitutes may also be managed directly in the parts library. See Global part substitutes for their behavior.

Issue Disposition Types ​

Administrators manage the disposition types available on issues. Each type has a name, one of the six base behaviors, and the permission required to approve and apply it: Disposition or Design authority. Every organization starts with one type for each base behavior, plus Accept.

A type may be renamed at any time. Its base behavior cannot change once a disposition uses it, so a type always does the same thing to inventory and holds, and plugins and scripts that refer to it keep working. Types are never deleted. An archived type is no longer offered for new dispositions, and dispositions that already use it keep it.

Organizations that need additional rules, such as extra reviewers or required customer approval for particular parts, add them with plugins.

Disposition types are planned and not yet available. See issues.

Enterprise Version Pinning ​

Enterprise organizations can configure whether Factorial follows the latest available release or remains on a selected supported version. See Version Pinning for the available update modes and upgrade behavior.