# Session timeout

**URL:** <https://community.sendbird.com/t/session-timeout/269>\
**Category:** Miscellaneous\
**Tags:** peak-connection\
**Created:** [May 15, 2020, 9:21am UTC](https://community.sendbird.com/t/session-timeout/269 "2020-05-15T09:21:42Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![StephenCP](https://sea2.discourse-cdn.com/flex020/user_avatar/community.sendbird.com/stephencp/32/83_2.png) [@StephenCP](https://community.sendbird.com/u/StephenCP)\
**Post date:** [May 15, 2020, 9:21am UTC](https://community.sendbird.com/t/session-timeout/269/1 "2020-05-15T09:21:42Z")

</div>

Is there session timeout in SendBird Chat?

---

<div class="post-metadata">

**Author:** ![eric.kim](https://sea2.discourse-cdn.com/flex020/user_avatar/community.sendbird.com/eric.kim/32/8_2.png) [@eric.kim](https://community.sendbird.com/u/eric.kim)\
**Post date:** [May 15, 2020, 9:33am UTC](https://community.sendbird.com/t/session-timeout/269/2 "2020-05-15T09:33:10Z")

</div>

@StephenCP Are you referring to session token timeout?

> **[User | Platform API Chat SDK Documentation | Sendbird](https://docs.sendbird.com/platform/user#3_create_a_user_4_access_token_vs_session_token)**
>
> Users can chat with each other by participating open channels and joining group channels. They are identified by their own unique ID, and may have a customized nickname and profile image. Using the API, you can manage the various attributes of each...

---

<div class="post-metadata">

**Author:** ![StephenCP](https://sea2.discourse-cdn.com/flex020/user_avatar/community.sendbird.com/stephencp/32/83_2.png) [@StephenCP](https://community.sendbird.com/u/StephenCP)\
**Post date:** [May 18, 2020, 2:23am UTC](https://community.sendbird.com/t/session-timeout/269/3 "2020-05-18T02:23:05Z")

</div>

Hi Eric,

Yes, I see, I believe it is. Is it possible to have some users with access token, and others with session token?

Best regards,  
Stephen

---

<div class="post-metadata">

**Author:** ![janna-sendbird](https://sea2.discourse-cdn.com/flex020/user_avatar/community.sendbird.com/janna-sendbird/32/963_2.png) [@janna-sendbird](https://community.sendbird.com/u/janna-sendbird)\
**Post date:** [May 18, 2020, 8:43pm UTC](https://community.sendbird.com/t/session-timeout/269/4 "2020-05-18T20:43:50Z")

</div>

Hi @StephenCP yes, it’s technically possible to have both users with access tokens and session tokens in the application, but we recommend selecting one approach for simplicity.

Advantages of access tokens are that you do not need to re-issue access tokens since they do not expire. But, the downside is, in the event the access token is ever compromised, you would need to manually handle revoking a compromised access token and calling update on the user to re-issue the access token. [https://docs.sendbird.com/platform/user#3\_update\_a\_user](https://docs.sendbird.com/platform/user#3_update_a_user)

Advantages of session tokens are that they are more secure due to the expiration date. But, the downside is they should be cached locally or at least on your server-side and handled upon expiration.