Multi-User admin UI: Who can see what.

[ErisDS]

Updated based on comments.

This is good reference material: #2264

Note There are likely to be some subtleties here that won't be clear until we've actually tried logging in as a particular user. This is the best guess we've got in advance of how it should work.

Overall UI:

• author: doesn't see 'settings' in the navbar
• all other roles: can see the 'settings' item

Settings screen

• author: cannot get here **
• editor: only has the 'users' pane available.

Settings/Users screen

• author: cannot get here **
• editor: gets a version restricted to authors, editors can only edit author level users:
  • can invite authors only
  • can see a list of invites to authors
  • can revoke invites to authors
  • can edit authors

Note: because editors can only edit authors, it would be nice if the user list only showed authors. However, that is counter to the API which will return all because editors can browse all users, see: #3097. Therefore it's ok if this list shows all active users, as long as only the authors are clickable.

Content list screen

• author:
  • can browse all their own posts
  • can only edit their own posts: so no post settings or edit icons if they don't own the post
• editor: can browse and edit everything

Editor Screen

• author: can access the editor to create new posts, or edit their own.
• author: cannot access the editor to edit other people's posts
• editor: can edit any post

Note: because authors can only edit their own posts, it would be nice if the content list only showed their stuff. However, that is somewhat counter to the API which will return all because authors can browse all posts. We're going to need to change the Post API to handle this, issue TBD.

** - Because the author cannot see the settings screen, this makes editing their own profile (accessible through the user menu) somewhat weird, esp from a URL perspective. There is probably another issue to be done here.

Dealing with permissions errors:

Anyone trying to do something for which they don't have permission should see an error. Short term this is probably the error template with a 403 and a reasonable error message.
Preferable is to send them back to /ghost/ with an error notification, but this may be too time consuming for now.

[halfdan]

can an author see all the posts on the content screen? or only their own posts?

Only his own (published and drafts) + all published from someone else. Only his own posts should be editable though.

if (post.status === 'published' || (post.status === 'draft' && post.created_by == currentUser)

what does an editor see?

All posts.

[JohnONolan]

an author shouldn't even see the settings option in the menu?

correct

an editor should only be able to get to /settings/users, and then only to invite users who are authors?

correct

Should an editor see the general or apps panes?

no - this leads into more discussion/work around #1895

can an author see all the posts on the content screen? or only their own posts?

own

what does an editor see?

all

[ErisDS]

I have updated this issue with more info based on the comments - this has thrown up a number of API additions / amends that need to be made.