Session Identifier

By default, every workflow session in Streamline is identified by a system-generated ID, which makes it hard to tell at a glance which end user a session belongs to. Session Identifier lets you tag one or more fields from your workflow, such as an email address or a name, as a recognizable label that appears next to each session. When a session needs support, debugging, or follow-up, you can find the right person without cross-referencing records elsewhere.

How to Configure a Session Identifier

Who can do this: Admins and Managers.

Configuring a session identifier is optional. Workflows without one continue to use the system-generated session ID. You configure the identifier on a draft version of a workflow; published versions cannot be edited.

1. Open the canvas builder.
2. Click Publish, then select Session Name to open the Build your session name dialog.
   In the dialog, build the identifier from merge fields and your own text. Add a merge field from one of the suggested cards, such as Employee Name, Department, or Reviewer Name, by clicking its +, or use search to find a specific field. You can also type spaces, punctuation, and labels between fields to create a name such as First Name Last Name - (Department).

3. Merge fields appear as chips and your typed text appears inline, under Session name in the order they will display. Remove a chip with its x.
4. Add up to 10 fields, along with any text you need. The fields' values and your text are combined in order to form the session name.
5. Click Save.
6. To make the identifier active, publish the workflow version. Open the Publish menu; Session name shows a green check once it is configured. Click Publish workflow.

Tip: Combine more than one field (for example a name plus an email) when a single field would not uniquely identify a session.

How to Grant Access to Session Data

Who can do this: Admins and Managers.

Session data is the unredacted workflow data that resolves the identifier. Grant view access per project so the right users can see identifier values in the session table.

7. On the project page, click Access to open Edit project access.
8. Select the Session data tab.
9. Check View data for each user or group that should see session data.
10. Click Save changes.

How to View and Reveal a Session Identifier

Who can do this: Admins, and any Builder, Manager, or Operator who has been granted view access on the project. Without view access, sessions show the system identifier only. Admins and Managers can grant view access to other users on a project.

11. Go to the Projects page and click the project to open its session list.
12. The identifier appears in the Session name column. When the session name setting is on and an identifier is configured, that column shows your configured name. When the setting is off, the same column shows the system Session ID instead.

13. Turn on the Show data toggle in the column header to reveal the identifier values.

Tip: To see both the configured name and the system ID, add Session ID as a column. After you set the session name, Session ID is available as a column you can add to the session list.

Important: Revealing a masked identifier value is recorded in the audit log, including who revealed it and when. The value itself is not stored in the audit record.

Note: The session identifier shows on the project page today. Support for showing it in the Workspace is coming and is not available right away.

How to Disable Session Identifiers for an Account

Who can do this: Account admins only.

Turn the feature off so sessions across the account are identified by system ID only.

14. Go to Account > Security and find the Data retention section.
15. Turn off Generate session names using workflow field data.

Feature Considerations

• Identifiers are not unique. Multiple sessions can resolve to the same identifier value. The identifier is a recognizable label, not a unique key.
• Display only. Streamline does not group, deduplicate, or merge sessions by identifier.
• Project-scoped search. Searching by identifier works within a single project. There is no cross-project or cross-workflow identifier search.
• Published versions are locked. You cannot edit or remove the identifier configuration on a published version. Make changes on a draft and republish.
• Removed fields drop out. If a mapped field no longer exists when you publish, that part is removed from the identifier automatically.
• No export. Resolved identifiers are not included in CSV or PDF exports.

Compliance

Identifier values that may contain sensitive information are masked by default and are sent to the session list and detail views only when a permitted user deliberately reveals them. Each reveal is logged with the actor, the timestamp, and the affected session; the revealed value is never stored in the audit log. Resolved values are shown only to users with view access, and account admins can disable the feature entirely.