blob: b3650b0b3fd9b8ace33ad2b4894c16c5e160d601 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
|
<div id="userModal" class="modal fade" tabindex="-1" role="dialog">
<div class="modal-dialog" role="document">
<div class="modal-content">
<div class="modal-header">
<button type="button" class="close" data-dismiss="modal">
<span aria-hidden="true">×</span>
</button>
<h4 class="modal-title">User Accounts</h4>
</div>
<div class="modal-body">
<p>Scrott implements a very flexible permissions and access-control system. It all
starts with users' accounts. Users can create and maintain objects and share them
with other users if they choose. This is done with a mechanism similar to unix
file permission modes. Scrott objects form a hierarchy, so permissions from 'higher'
objects will cascade down. This means that a non-trusted user may control an issue
in your pad, but have no access to the pad itself.</p>
</div>
<div class="modal-footer">
<button type="button" class="btn btn-primary" data-dismiss="modal">
Close
</button>
</div>
</div>
</div>
</div>
|