---
title: Adjust Salesforce Session Timeout
slug: reports/adjust-salesforce-session-timeout
docTags: 
createdAt: 2026-06-17T20:53:49.469Z
---

The connection between Unaric Reports and Salesforce uses Salesforce's standard OAuth and session security. After a set period, Salesforce expires your session (and its access token), requiring you to sign in again. This is expected behaviour, and it is controlled entirely by the session and OAuth settings in your own Salesforce org, not by Unaric Reports.

This page explains how to set up the session timeout between Unaric Reports and
Salesforce. This is helpful in case you're being prompted to sign in more often than you would like or, in turn, you would prefer to tighten security and have your users re-authenticate sooner.

## Requirements

- You need **administrator access** to your Salesforce org.
- Decide on the duration you want. Longer sessions mean fewer login prompts but lower
  security; shorter sessions are more secure but ask users to sign in more often.

## Option 1 : Set the timeout on the app

:::hint{type="success"}
Use this when you want to control the timeout for this specific integration.
:::

1. In Salesforce, open **Setup**.
2. Navigate to **Apps >** **Connected Apps >** **Manage Connected Apps**.
3. Find **Cloud4J - Report Builder** and click **Edit**.

::Image[]{src="https://api.archbee.com/api/optimize/10Nod6Ww95R3dPr0k0TCJ/4XvTRvZSe7KblhVNy9J_x_image.png" size="70" isUploading="false" width="1914" height="935" showCaption="false"}

4. Click **Edit Policies**.
5. Under **Session Policies**,use the **Timeout Value **dropdown to choose a convenient duration (for example *15 minutes*, *2 hours*, or *24 hours*). If the dropdown is not visible, click **Set app-specific token timeout **to activate it.
6. Click **Save **to finish.

:::hint{type="info"}
If **Timeout Value** is left as *None*, the app falls back to your org-wide **Session**
**Settings **instead. See Option 2.
:::

## Option 2 : Set the org-wide Session Settings

:::hint{type="success"}
Use this when the app relies on your org's default, or when you want to change the timeout for the whole org. This value applies across your org wherever a more specific setting is not in place.
:::

1. In Salesforce, go to **Setup**.
2. Navigate to **Security > Session Settings**.
3. In the **Session Timeout **section, use the **Timeout value** dropdown and choose a convenient duration.
4. Click **Save**.

:::hint{type="info"}
You can see which sessions are currently active and remove them at **Setup >** **Session Management.**
:::

## Troubleshooting

### Users are still logged out sooner than the value I set

A profile-level setting may be overriding the org default. In **Setup**, go to
**Profiles**, open the relevant profile, and check **Session Settings > Session Times Out**
**After**. A value set here overrides your org-wide Session Settings for users with that
profile.

### Where does the timeout come from if the app's value is ***None***?

Salesforce falls back to your org-wide Session Settings (Option 2), unless a profile-level
override applies.

### Users have to fully sign in again instead of the connection refreshing quietly

Alongside the timeout, Salesforce uses a *refresh token policy* to decide whether the
connection can renew automatically when a session ends. If that policy is set to expire
quickly, users are asked to sign in more often. You can review it under the app's **OAuth**
**policies** (the same place as Option 1); the default of *Refresh token is valid until*
*revoked* keeps users signed in until access is explicitly removed.