---
title: "Named Sessions"
slug: "named-session"
description: "This document explains how to create a Named Session in Decisions for purpose of invoking a workflow via REST integration."
tags: ["Session", "integration"]
updated: 2025-07-01T18:31:37Z
published: 2025-07-01T18:31:37Z
canonical: "documentation.decisions.com/named-session"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.decisions.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Named Sessions

## Overview

A **Named Session** allows for a specific user account to pass in when executing a Flow via REST, without exposing the user account information. To relay the data properly, a **Session ID** is automatically applied to the generated URL when the Named Session is selected.

Named Sessions do not expire; if expiration is needed, a [JSON Web Tokens can be configured](/v9/docs/using-jwt) instead.

[Embedded content](https://www.youtube.com/embed/50n5-0anWNc?&wmode=opaque&rel=0)

---

## What changed from V8 to V9?

| Version 8 | Version 9 |
| --- | --- |
| Named Sessions were configured at the System level and were visible across the platform. | Named Sessions are now Project-level and are visible only within the Project. |

---

## Creating a Named Session

This example will demonstrate how to create a Named Session and generate the appropriate REST URL from the Flow.

1. In the desired Designer Folder, navigate to **Settings** > **Security** > **Named Sessions** and select **ADD NAMED SESSION** from the Global Action Bar.
2. When the window appears, enter a name for the session. Use the PICK button under **ForAccountId** to select the user account it applies to.
3. Select **SAVE** once complete and refresh the FOLDER VIEW to confirm the **Named Session** appears.  
![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/Screenshot%202024-03-07%20135620.png)
4. Now that the **Named Session** is configured, it can be selected on the [INTEGRATION DETAILS](/v9/docs/view-integration-details) page for a Designer Element, such as a Flow or Form.
5. Right-click the Element's name and in the Action Menu, navigate to **More** > **View Integration Details**.  
![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/Screenshot%202024-03-07%20140255.png)
6. In the **View Integration Details** window, use the drop-down list for **Authentication Type** and choose the name of the **Named Session**.
7. Upon the selection, all service API URLs will appear for the corresponding integration type (typically GET or POST by default).Clear Session URL ExtensionAdd **&clearsession=true** to the end of the URL to ensure that each time the user exits the browser after completing the **Named Session** Flow/Form, the session is cleared. This will allow another user to run the same Flow/Form on the same machine with a different Named Session.

---

## Testing the Named Session

Once a named session has been configured, the named session can be tested using the Test section from the [Integrations Details](/v9/docs/view-integration-details) page of a Designer Element. To access the page, the Designer Element, such as a Flow, will need to be configured as an [API Service](/v9/docs/rest-handling-services). Once this has been configured:

1. From the **Setup** drop down menu, select the named session
2. Select the **TEST** page, a URL will be selectable as a Get or Post call. Select either option then select the **Run** button.
3. The Flow will be executed using the named session for authentication.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/Screenshot%202024-03-07%20140953.png)

In addition, the generated URL can be used in other applications such as Postman to validate the results. The URL can be copied and used as a Get/Post request, depending on the requirements.

For **Postman**, a collection can be generated and imported for testing using the **DOWNLOAD POSTMAN COLLECTION** button. The request generated from this method will be a POST call.

![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/Screenshot%202024-03-07%20140834.png)

---

For further information on Integrations, visit the [Decisions Forum](https://community.decisions.com/categories/Integrations).