The Rocket.Chat User Status setting lets you manage custom users' presence and status in your workspace.
A presence is used to determine the Status of a user in the workspace.
By default, Rocket.Chat has the following presence options:
Online: Used to indicate a user is online and available.
Away: Indicates a user is idle and away from the workspace. See how to configure the idle time limit here Default User Preferences or as a user in User Presence.
Busy: This shows a user is busy and unavailable on the workspace.
Offline: Used to indicate a user is offline and not connected.
To access the User Status setting, go to Administration > Workspace > User Status.
Add custom status
To create a custom status,
On the User Status page, click New custom status.
Enter a name for your custom status.
Select a presence to tie with your custom status.
Click Save.
Use custom status
The custom and default status options will be visible to all users in your workspace.
To set a custom status,
Click on your avatar by the top left of your workspace.
From the drop-down menu, select the custom status from the list of statuses.
Edit and delete custom status
To delete or edit a custom status,
Go to Administration > Workspace > User Status.
Search and click the custom status you want to edit or delete.
Update the details and click Save to edit the status. Click Delete to delete the status.
Presence service cap
Premium plans do not have a presence service limit. Workspaces on the community plan have a maximum limit of 200 concurrent connections. While you can have more connections active, users' statuses will no longer be visible, and the presence service gets disabled once you reach this cap. However, this limitation does not impact their capacity to send and receive messages.
With the presence service enabled, users can see the status of other users in the workspace.
To enable the presence service,
Go to Administration > Workspace > User Status > Presence service.
Click the Presence service button.
Enable the Service status option.
When the presence service gets disabled automatically due to the cap on concurrent connections,
Users see the status indicator for all users, including themselves as
disabled.The workspace administrator has to manually reactivate the presence service when the number of connections drops below the connection limit of 200.
Workspace users and administrator(s) are notified that presence is inactive because the workspace has exceeded the connection limit.