Jan 20 2021
Nov 25 2019
In D20927, I implemented a policy rule like this:
Nov 6 2019
Sep 26 2019
Sep 24 2019
Sep 19 2019
Aug 22 2019
Aug 21 2019
Aug 20 2019
You can automate at least some administrative actions...
(You can automate at least some administrative actions at an "omnipotent" power level with bin/conduit call --method user.edit nowadays, too, although accountadmin operated with interactive prompts so it's unlikely anyone automated on top of it.)
Mar 29 2019
Feb 7 2019
Feb 6 2019
Jan 25 2019
From T13222, MFA on related flows should generally be updated.
Jan 3 2019
I'm going to merge this into T12738. Although that task primarily discusses Nuance as a Phacility support tool and we ended up building a standalone Support tool instead, I generally believe Nuance is the most likely pathway for interactions falling under the general "helpdesk" umbrella.
Dec 22 2018
$table = new PhabricatorUser();
$cache_path = 'progress.json';
I just deleted the users above and am backing away from D19933, at least for now, since it doesn't feel like an especially great fit for either secure or admin.
On admin, basically every user with a blurb is abusive. I've just disabled the field as a coarse reaction.
I'm planning to banish these users from secure. This is mostly: polish (?) SEO bots; printer fax spam; and "security researchers":
Dec 12 2018
Nov 15 2018
A couple of narrow ideas here:
Nov 6 2018
Sep 13 2018
I don't currently plan to make "Disable User" any more granular than it is. If you have a use case where you want multiple administrator levels and to allow administrators at a certain level to act downward but not upward, you might be able to do something like have an enforcer-bot account which users can instruct to disable one another. The enforcer-bot itself could act via the API.
Aug 27 2018
"Disable User", specifically, is now granular.
I made this public since I've disclosed/discussed this elsewhere, including an indirect reference in the Spaces documentation, and I'm going to schedule it alongside some other stuff.
May 14 2018
Dec 13 2017
As @avivey suggests, the remaining cache can be cleared with:
Dec 9 2017
You need to clear some caches too - ./bin/cache purge - but I'm not sure which; And then hard-refresh the in the browser.