2.2. Users ¶

Contents

Users
- Information stored
- Managing users and permissions
  - Manage users
    - Bulk import
    - Deleting and undeleting users
  - Permissions

Users of Coil are stored in the Redis database.

2.2.1. Information stored ¶

The following data about users is stored:

2.2.1.1. Profile ¶

Name	In Account	Notes
`username`	Username	Used to log in
`realname`	Real name	Prominently displayed on posts
`email`	E-mail address	Used by administrators to contact users
`password`	Password	Hashed and salted using bcrypt

2.2.1.2. Preferences ¶

Name	In Account	In Permissions
`want_all_posts`	Show me posts of other users by default	Want all posts

2.2.1.3. Permissions ¶

Coil uses a very granular permission system. Each user can have a different set of permissions, depending on the needs of the organization.

Name	In Account	In Permissions
`active`	n/a	Active
`must_change_password`	Must change password on next login	Must change password
`is_admin`	User is an administrator	Admin
`can_edit_all_posts`	Can edit posts of other users	Can all posts
`can_upload_attachments`	Can upload attachments	Attachments
`can_rebuild_site`	Can rebuild the site	Rebuild
`can_transfer_post_authorship`	Can transfer post authorship	Transfer authorship

2.2.2. Managing users and permissions ¶

All administrators (people with the is_admin permission) get access to user management views, accessible from the user menu. They are:

2.2.2.1. Manage users ¶

This is a table of all users. You can add new users at the bottom by typing in a name and clicking Create. You can also Edit, Delete or Undelete.

2.2.2.1.1. Bulk import ¶

The last row lets you import a file with user data. TSV (Tab-Separated Values) files are accepted.

The first row MUST contain all the column names. They are:

username
realname
email
password
active
is_admin
must_change_password
can_edit_all_posts

9. want_all_posts 10 can_upload_attachments 11. can_rebuild_site 12. can_transfer_post_authorship

The following rows should contain data for the users. Passwords should be in plain-text. All the boolean fields (active and everything after it) accept 0 or 1 as their value.

2.2.2.1.2. Deleting and undeleting users ¶

Even when you press the Delete button, the user stays in the database. You can then Undelete them if you change your mind.

You could delete the user straight from Redis, but this is not recommended and can have unexpected side effects.

2.2.2.2. Permissions ¶

This is a table of all permissions in the system. It can be used to quickly modify the permission list for groups of users. The teal buttons can be used to select the permission for all users.