You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/setup.md
+22-5Lines changed: 22 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -123,17 +123,34 @@ Each permission set can have a service. The `service` field can be:
123
123
- `challengehound`
124
124
- `*`, for any service.
125
125
126
+
The `level` determines what permissions a user has access to on the named service(s). They are
127
+
additive, one level grants all previous levels in addition to previous levels.
128
+
126
129
The `level` can be:
127
130
128
131
- `commands`Can run commands within connected rooms, but NOT log in to the bridge.
129
-
- `login`All the above, and can also log in to the bridge.
130
-
- `notifications`All the above, and can also bridge their notifications.
132
+
- `login`All the above, and can also log in to supported networks (such as GitHub, GitLab). This is the minimum level required to invite the bridge to rooms.
133
+
- `notifications`All the above, and can also bridge their own notifications. Only supported on GitHub.
131
134
- `manageConnections`All the above, and can create and delete connections (either via the provisioner, setup commands, or state events).
132
135
- `admin`All permissions. This allows you to perform administrative tasks like deleting connections from all rooms.
133
136
134
-
When permissions are checked, if a user matches any of the permissions set and one
135
-
of those grants the right level for a service, they are allowed access. If none of the
136
-
definitions match, they are denied.
137
+
If any of the permissions matches positively for a user, they are granted access. For example:
138
+
139
+
```yaml
140
+
permissions:
141
+
- actor: example.com
142
+
services:
143
+
- service: GitHub
144
+
level: manageConnections
145
+
- actor: "@badapple:example.com"
146
+
services:
147
+
- service: GitHub
148
+
level: login
149
+
```
150
+
151
+
would grant `@badapple:example.com` the right to `manageConnections` for GitHub, even though they
0 commit comments