CommunityHire an ExpertSign Up
User Groups and PermissionsOptions Filters
User Groups and Permissions

Options Filters

Filter options in form dropdowns, inputs, and inline filters.

Overview

Options filters are a specialized use of conditional filters to restrict the choices available in dropdown inputs, conditional forms, or similar selection fields, ensuring users only see relevant options based on conditions.

Where Can Options Filters Be Used?

  • Dropdown Inputs: In forms for creating or updating records, to filter options in linked record or value-based dropdowns.

  • Quick Select Inputs: You can filter a quick select field in conditional forms to only show options that meet certain criteria.

  • Inline Filters: On dynamic blocks, where user-facing filter dropdowns can have their options restricted (e.g., only show filterable statuses that the user has access to).

  • Other Contexts: Any selection field mapped to a data source, such as in conditional forms for step or section logic.

Why Use Options Filters?

Options filters improve user experience by preventing irrelevant or unauthorized selections. For example, clients can only see and select projects relevant to them in a dropdown (for example, filter by client email matching the Logged-in user’s Email). This can help dramatically in reducing errors and keep people from seeing options they shouldn’t see.

How Options Filters Work with Global Data Restrictions

Global data restrictions apply first to limit the overall data (e.g., hiding restricted records from the data source table), and options filters then refine the visible choices within that selection. For instance, if global data restriction rules restrict a projects table to user-owned records, options filters can further limit dropdown options to active projects only. This layered approach ensures security at the app level while allowing precise control in inputs.

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search Softr Documentation documentation and read it in full, instead of answering from memory.

https://docs.softr.io/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://docs.softr.io/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.