Allow invalid and self-signed SSL certificates for link validation and previews.
If you are integrating Bugsnag with Rocket.Chat, you should put your Bugsnag API Key here.
Insert here the prefix for the CDN that should load the JS/CSS assets
If you want to use a CDN to load the assets of your server, insert here your CDN Prefix.
This will define if all assets from the server will come from a CDN.
- Yes: Users will be able to favorite public, private and direct channels.
- No: Users won't be able to favorite channels.
Insert here the name of the channel that the user will enter after logging in. Setting this field to empty or setting a invalid name will result in the user being directed to the server's home page.
Will not use OpLog to sync cache even when it's available
You can use this setting to force SSL on your server. We Strongly Discourage the usage of this setting, this should be done at the reverse proxy level by redirecting to https.
Caution! Force SSL should never be used with reverse proxy. If you have a reverse proxy, you should do the redirect THERE. This option exists for deployments like Heroku, that does not allow the redirect configuration at the reverse proxy.
You can use Google Tag Manager on Rocket.Chat by setting your Id on this setting.
This sets the default language for the server. This setting will be overridden if the user has changed his language preference.
This button restarts the server.
This sets the content of the Robots.txt file, used to help indexing your server on different search engines and crawlers.
For now this setting SHOULD NOT be changed. Setting this to pending and logging out can basically lock down your server. Please refer to this issue.
This sets the name of the server.
This sets the URL of the server.
Example:
https://chat.domain.com/
Store last message sent on each room. This will enable the viewing of the last message on the left sidebar (should be on by default)
This setting changes the behavior of the unread counter
- All messages: All messages will be counted on the counter, regardless if they are a mention or not.
- User mentions only: Only mentions using
@yourUsernamewill be counted on the counter. - Group mentions only: Only group mentions using
@allor@herewill be counted on the counter. - User and group mentions only: All mentions will be counted, this includes
@all,@hereand@yourUsername
This setting changes the behavior of the unread counter on Direct Messages
- All messages: All messages sent by another user will be counted on the counter.
- Mentions only: Only mentions using
@yourUsernamewill be counted on the counter.
Use this setting to enable the Rocket.Chat Apps Framework. This allows you to add Rocket.Chat Apps from our Marketplace to your server.
This setting defines if a parent window can send commands to Rocket.Chat.
Origins with protocol prefix, separated by commas, which are allowed to receive commands e.g. https://localhost, http://localhost, or * to allow receiving from anywhere.
This setting defines if Rocket.Chat can send events to the parent window.
Origin with protocol prefix, which commands are sent to e.g. https://localhost, or * to allow sending to anywhere.
Choose to always notify mobile device regardless of presence status.
Max number of members in room when notifications for all messages gets disabled. Users can still change per room setting to receive all notifications on an individual basis. (0 to disable)
This setting affects the count query parameter. See more at Offset and Count Information
- Yes: Allows the usage of the number
0ascountparameter. Settingcountto0will return ALL the data from that endpoint - No: Setting the number
0oncount, will return0results.
Should calls to the REST API be allowed to return everything in one call?
Here you can set what origins are allowed to make requests to your server.
You can use
*to accept from all origins. For multiple Origins use a comma separated list. E.ghttps://domain1.com, https://domain2.com, https://domain3.com
The default count for REST API results if the consumer did not provided any.
Use this setting to enable CORS for the REST API. Enabling CORS will make the server only accept API Calls from specific origins.
Note: Setting this to
false, will make your server only accept requests from the same domain of said server. E.g.rocket.chatserver will only accept requests from therocket.chatdomain.
This enables the /api/v1/im.history.others which allows the viewing of direct messages sent by other users that the caller is not part of.
Enables the usage of Shields via API
Enabled shields are available at
/api/v1/shield.svg
Types of shields to enable as a comma separated list, choose from online, channel or * for all
This sets the maximum number of records the REST API should return when not set to unlimited
This limits the amount of users that can be added to a Channel at the same time.
By sending your statistics, you'll help us identify how many instances of Rocket.Chat are deployed, as well as how good the system is behaving, so we can further improve it. Don't worry, as no user information is sent and all the information we receive is kept confidential.
IP or Host of your Rocket.Chat central Stream Cast. E.g. 192.168.1.1:3000 or localhost:4000
With this setting you can configure custom translations for your server.
Should be a valid JSON where keys are languages containing a dictionary of key and translations. Example:
{
"en": {
"Channels": "Rooms"
},
"pt": {
"Channels": "Salas"
}
}RegExp that will be used to validate usernames and channel names
Note: If you are having problems with names when creating channels (when using non-english characters for example) changing these values will probably fix it. For example using
[\w_-]+should allow any non-space character to be part of a name.
Whenever we have a new version available, it will show up on this field.