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
movement The movement permission governs all the Corrade commands that are meant to move Corrade. This includes nudging the bot, teleporting the bot and other commands that would allow Corrade to move around.
economy Granted the economy permission, groups will have the ability to use Corrade's L$ balance which includes, paying other avatars, buying items, etc…
land Most commands that deal with in-world land assets such as changing parcel descriptions, querying data for a region, and so on, need the land permission.
grooming The grooming permission can be granted to groups that are allowed to change the in-world profile of Corrade.
inventory Commands that deal with Corrade's inventory are protected by the inventory permission. Searching Corrade's inventory, handing out objects from Corrade's inventory and so on are all restricted by the inventory permission.
interact interact is a permission that, when granted, gives the right to groups to interact with in-world assets such as primitives.
mute The mute permission restricts commands that are able to modify and query Corrade's mute list.
database The database permission, when granted to a group, allows that group to store key-value pairs in a custom database for each group.
notifications To be able to install notifications groups need the notifications permission.
talk Corrade's talking ability - whether it is in a group, in local chat, or sending private messages to agents is restricted by the talk permission.
directory Any group that is able to search directory services (land sales, scheduled events, people and group search, etc…) needs the directory permission enabled.
system Commands that change Corrade's functionality need the system permission. Note that this permission can be considered very dangerous since it allows a group to reconfigure and poll Corrade's entire configuration file.
friendship All the commands that deal with friendship requests, either received, being sent by the bot or generally polling the friends list require the friendship permission.
execute To be able to execute commands on the machine that Corrade is hosted on, groups need the execute permission. Note that this command is dangerous because it would allow any group to execute any command on the host machine with the same privileges that Corrade runs under.
group 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 group permission to be set.
filter The filter permission protects the commands that are able to modify or query Corrade's input and output filters.
schedule The schedule permission allows groups to schedule a command for later execution. This permission works together with the per-group setting that limits the amount of commands allowed to be scheduled for each group.

secondlife/scripted_agents/corrade/api/progressive/permissions.txt · Last modified: 2019/01/03 01:36 (external edit)

Access website using Tor Access website using i2p

For the copyright, license, warranty and privacy terms for the usage of this website please see the license, privacy and plagiarism pages.