> This page is for Glide Classic.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://www.glideapps.com/docs/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://www.glideapps.com/docs/_mcp/server.

# Show Sign In

> Show the sign in screen on your app.

The **Sign In** action will pull up the sign in screen for the user.

For the Sign in action to work, your [app's privacy settings](/docs/getting-started/app-settings#access) must be set to Public, with either optional or required sign-in, where Anyone can create a profile. The sign-in action will only appear if the user is not signed in yet.

The **Sign In** action can be used as an action in the components of your app (like [Buttons](/docs/essentials/components/button), [Collections](/docs/essentials/components/collections), and much more), or it can be triggered along with other actions as part of a [Workflow](/docs/getting-started/introduction-to-workflows).

## **Setting up the Sign In Action**

#### Layout Editor

#### Sign In Layout Arcade

Click on the plus (+) sign in the **Components** panel and select the **Component** you want to trigger the action.

In the **General** tab on the right side of the Layout Editor, navigate to the **Actions** section and select **Sign in**.

Select the icon and descriptive text to use in your app. **Success** shares the descriptive text on a green background, and **Failure** shares the descriptive text on a red background.

You can optionally add **Conditions** for certain criteria to be met before a user can trigger this action.

#### Workflow Editor

#### Sign in Action Editor Arcade

Select the **+ New Workflow** button. If you have existing actions, click on the plus (+) sign in the left panel.

Select the **data source** for your action.

Configure your first action by clicking the first step in the workflow. You can also add conditions to your actions, if needed.

To add new actions to the flow, hover just underneath a step and click the plus button. In this way you can add the Sign In action as just one step in a larger workflow.

Check the [Introduction to Actions](/docs/automation/actions) page for a full list of components that can be used to trigger actions.