app/templates/views/manage-users/permissions.html

{% from "components/checkbox.html" import checkbox %}

<fieldset class="form-group">
  <legend class="form-label">
    Permissions
  </legend>
  {{ checkbox(form.send_messages, block=True) }}
  {{ checkbox(form.manage_service, block=True) }}
  {{ checkbox(form.manage_api_keys, block=True) }}
</fieldset>

<div class="form-group">
  <p class="form-label">
    All team members can see
  </p>
  <ul class="list list-bullet">
    <li>templates</li>
    <li>history of sent messages</li>
    <li>who the other team members are</li>
  </ul>
</div>
Set permissions with checkboxes, not yes/no inputs The yes/no pattern didn’t work too well, because: - it didn’t read naturally as a question and answer - often users left them completely unclicked if they didn’t want to set the permission (rather than clicking no) This commit changes both the invite and edit user pages to use checkboxes to set permissions. If also rewords these pages to read more naturally, and explain what the permissions mean. This meant changing some of the view logic around invites and persmissions, and I ended up refactoring a bunch of it because I found it hard to understand what was going on. 2016-03-22 13:18:06 +00:00			`{% from "components/checkbox.html" import checkbox %}`

			`<fieldset class="form-group">`
			`<legend class="form-label">`
			`Permissions`
			`</legend>`
			`{{ checkbox(form.send_messages, block=True) }}`
			`{{ checkbox(form.manage_service, block=True) }}`
			`{{ checkbox(form.manage_api_keys, block=True) }}`
			`</fieldset>`

			`<div class="form-group">`
			`<p class="form-label">`
			`All team members can see`
			`</p>`
			`<ul class="list list-bullet">`
			`<li>templates</li>`
			`<li>history of sent messages</li>`
			`<li>who the other team members are</li>`
			`</ul>`
			`</div>`