Users API: deleting users

[ErisDS]

JSON API	Admin	Editor	Author	NoAuth
users.browse	y	y	y
users.read	y	y	y	y
users.edit	y	y (user == self or user == author)	y (user == self)
users.add	y	y (user == author)
users.delete	y (user != owner)	y (user == author)

Note, authors cannot delete even their own account.

The flow of deleting a user will include a way to transfer ownership of stuff.

[sebgie]

I think user.edit and user.delete are not correct yet? Proposal:

JSON API	Admin	Editor	Author	NoAuth
users.edit	y	y (user == self or user == author)	y (user == self)
users.delete	y (user != owner)	y (user == self or user == author)

[ErisDS]

Note, authors cannot delete even their own account.

The lack of ability to delete yourself is deliberate. From the perspective of a publishing house, you don't want your authors to throw a wobbly and delete themselves taking a tonne of your content with them.

[sebgie]

@ErisDS I read that part and didn't propose to change it. The changes are:

• allow an edtor to edit himself
• allow an editor to delete himself or an author, the rule in the issue suggests that an editor is allowed to delete admins.

[ErisDS]

Sorry I looked too quickly - read change delete and saw user == self against author and thought it was in that row.

I think you are correct about editor editing himself, and that an editor cannot delete admins. Not sure about having editors delete themselves?

[JohnONolan]

I think the only people who should delete themselves are admins

[sebgie]

updated table LGTM 👍

[javorszky]

Couple of questoins:

• What happens to content when an admin deletes itself? Could this potentially lock in parts of Ghost?
• When transferring ownership, will there be an option to delete all content? (suggestion: no)
• Who should be able to mass delete content? (owner only or admins? Any admins? Disgruntled employee, or is that none of our business?)

[halfdan]

IMHO user deletion should perform soft-deletes.
On 2 Jul 2014 10:35, "Gabor Javorszky" notifications@github.com wrote:

Couple of questoins:

• What happens to content when an admin deletes itself? Could this
  potentially lock in parts of Ghost?
• When transferring ownership, will there be an option to delete all
  content? (suggestion: no)
• Who should be able to mass delete content? (owner only or admins?
  Any admins? Disgruntled employee, or is that none of our business?)

—
Reply to this email directly or view it on GitHub
#3100 (comment).

[ErisDS]

This conversation has already been had on #3083 we are not soft deleting, we will transfer content.

[ErisDS]

Coming soon: #3182

[ErisDS]

@javorszky This is just an API call, it should perform a hard deletion of a user and all related content. Assume that if the content wasn't supposed to be deleted it would already have been moved away by logic / flow in the User interface.

The rules of who can delete what are laid out in the table above, if the user can be deleted, all the content can be deleted too.