Comment on page
App Permission System
Each feature available in the Apps-Engine is mapped to a permission. Adding the permission in the app's manifest (
app.jsonfile) will unlock said feature to be used by the app. For example, if you add the
send messagespermission to your app's manifest, your app can send messages in the Rocket.Chat server. If your app tries to send a message without having the
send messagespermission listed in the manifest, Apps-Engine will block the feature and the app will not be able to perform the desired action.
When installing an app, be it via the Marketplace or installing it manually via zip file, a window asks the user to review the permissions that the app requires to work properly. The user installing the app can either accept and install the app or deny the permissions and not install it.
In your app's manifest file (
app.json), add the field
permissions. It receives a list containing all the permissions that you are asking for. For example:
Currently, the Apps-Engine does not enforce the use of the permissions to make your apps work, meaning your current apps (including those published on the Marketplace) will still work as expected. All the apps that do not have the permissions listed in their manifest will still have access to all the features they need through
default permissions. They are applied to your app automatically when no
permissionsproperty is found in the app's manifest.
Until the sunsetting period for the "permissionless engine" is not defined, setting permissions in your app's manifest will be optional.
Here is a list of the available permissions:
Once an app is on the Rocket.Chat workspace, it goes through several lifecycle phases unique to Rocket.Chat. The phases depend on the capabilities that your app has. To learn about the app lifecycle, head over to the next page.
Last modified 13d ago