Corrade permissions are an ACL system to limit groups to a subset of Corrade's functionality. In other words, they are meant to protect Corrade from its configured groups. For example, you may not want that a group be able to change the bot's profile description or modify its picks and in that case, you would not give the grooming
permission to a configured group. Most Corrade commands are sorted to require certain permissions and by looking-up the command on the API page, you can determine what permissions are required for a set of commands. In the table below we explain in general terms what a permission is meant for.
permission | description |
---|---|
|
The |
|
The |
|
Any group that is able to search directory services (land sales, scheduled events, people and group search, etc…) needs the |
|
Granted the |
|
In order to be able to execute commands on the machine that Corrade is hosted on, groups need the |
|
All the commands that deal with friendship requests, either received, being sent by the bot or generally querying the friends list require the |
|
The |
|
All the commands that deal with group operations, such as inviting people to groups, creating group roles, ejecting group members, banning group members from a group, and so on require the |
|
|
|
Commands that deal with Corrade's inventory are protected by the |
|
Most commands that deal with in-world land assets such as changing parcel descriptions, querying data for a region, and so on, need the |
|
The |
|
The |
|
In order to be able to install notifications via the notify command groups need the |
|
Commands that change Corrade's functionality need the |
|
Corrade's talking ability - whether it is in a group, in local chat, or sending private messages to agents is restricted by the |
For the contact, copyright, license, warranty and privacy terms for the usage of this website please see the contact, license, privacy, copyright.