|
a/index.html |
|
b/index.html |
|
... |
|
... |
| 137 |
<p>After the pop-up window is dismissed, the new Subproject tool will
|
137 |
<p>After the pop-up window is dismissed, the new Subproject tool will
|
| 138 |
be listed along with the other installed tools.</p>
|
138 |
be listed along with the other installed tools.</p>
|
| 139 |
|
139 |
|
| 140 |
|
140 |
|
| 141 |
<h3>Permissions and access control</h3>
|
141 |
<h3>Permissions and access control</h3>
|
|
|
142 |
|
|
|
143 |
<p>The key part of enforcing access control for a project takes place in the User Permissions page, at</p>
|
|
|
144 |
|
|
|
145 |
<p class="hint">Admin > User Permissions</p>
|
|
|
146 |
|
|
|
147 |
<p>
|
|
|
148 |
This page allows the project manager to define which users can read,
|
|
|
149 |
write or update the project's contents. Permissions are assigned by user groups.
|
|
|
150 |
Each project is created with an Admin, Developers, and Member.
|
|
|
151 |
But new user groups can be defined to further extend the control.
|
|
|
152 |
</p>
|
|
|
153 |
|
|
|
154 |
<img src="img/perm.png"/>
|
|
|
155 |
|
|
|
156 |
|
|
|
157 |
<p>The various tools in the platform inherit the general project
|
|
|
158 |
permissions, however some tools provide even more detailed access
|
|
|
159 |
control settings, enforcing per tool or per content access control.</p>
|
| 142 |
|
160 |
|
| 143 |
|
161 |
|
| 144 |
<h2><a name="git">Git</a></h2>
|
162 |
<h2><a name="git">Git</a></h2>
|
| 145 |
|
163 |
|
| 146 |
<p>
|
164 |
<p>
|