Roles are automatically created when policies are added / removed (e.g. when a listener ID is blocked).
- Currently, the script can only block listeners IF they have an ID attached to it via their options / metadata;
- Furthermore, the full ID must be specified when creating policies;
- None of the script's commands are blocked by default (i.e. anyone can use it, but they can not use it against a power user).
src/rbac.coffee for full documentation.
Installation via NPM
Install the hubot-rbac module as a Hubot dependency by running:
npm install --save hubot-rbac
Enable the module by adding the hubot-rbac entry to your
Run your bot and see below for available config / commands
||N/A||A comma-separated list of user names to be granted complete, and immutable permissions.|
|hubot auth me||
||Returns your current role(s).|
|hubot auth block
|hubot auth unblock
|hubot auth assign
|hubot auth unassign
|hubot auth default
||Changes the default
|hubot auth ids||
||Returns a list of listener IDs that can be blocked.|
|hubot auth roles||
||Returns a list of roles, and their respective subjects.|
user1>> hubot links list hubot>> user1: Nothing has been shared recently. user1>> hubot auth me hubot>> user1: You are not assigned to any roles. user1>> hubot auth block links.list nolinkrecording hubot>> user1: Listener ID "links.list" is blocked for "nolinkrecording" subjects. user1>> hubot auth assign user1 nolinkrecording hubot>> user1: Assigned "user1" to "nolinkrecording". user1>> hubot links list hubot>> user1: Sorry, you are not authorised to execute that command. user1>> hubot auth me hubot>> user1: You have been assigned the following role(s): nolinkrecording