CommunityHire an ExpertSign Up
User Groups and PermissionsPage Rules
User Groups and Permissions

Page Rules

Redirect user groups to specific pages after signin, signup, signout, and unauthorized attempts.

Benefits of using Page Rules

With Page Rules, you can use your defined User Groups to route users to different pages based on which user group(s) they are a part of. This is helpful when you need to control the flow of users through your app. When combined with block level visibility, Page Rules allow for complex user onboarding flows, user approval processes, and even subscriber page routing.

How do I use Page Rules?

To access Page Rules, click on the Page Tab, then click on the Pages Rules button.

Click on page tab, then the Page Rules link

Click on page tab, then the Page Rules link

On the Page Rules screen, you have several options to configure, depending on your number of users groups.

Notion image

  1. You’ll see all of your User Groups listed. You can think of Logged-in User as a fallback rule for any user that does not fit into a user group. If a user falls into multiple user groups, the groups at the top of the list take precedence. You can think of the list of group as a hierarchy and adjust them in the stack by dragging and dropping the handle to the left of the user group’s name.

  2. Depending on what the user is doing, you can define the page they are taken to based on these columns - After sign-in, sign-up, and sign-out. For pages users are not allowed to see, they will always be taken to the Permission Denied Utility page.

  3. In each dropdown, you can choose which page the user should be taken to after the action in the column. By default, all user actions take them to the Home Page.

Which signin/signup options are supported?

As of now, the user group redirects are applied to all the signin/signup options apart from the following ones:

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.