If you do not want someone specific to be able to even ask your permission to use your ARES system, the best solution is to create a ban for them. This can be done by pressing F5 BLOCK in response to a consent request or by adding their UUID with access control... > bans... > add new.

Unlike F4 REJECTing a request, bans last until they are rescinded. Removing a ban is done through the access control... > bans menu also, by selecting the individual's name and choosing unban.

Self-denial and consent

As we mentioned in the previous tutorial, it is common for units to be configured to have reduced self-access, either by reducing them to regular Users, or by complete denying the ability to interact with the system beyond the normal functions of chat processing. However, if you ban the unit from interacting with itself, you'll quickly discover the unit is still asked to consent to interactions from strangers, which may not be what you want. To complete the process of denying a unit self-access, see Configuring ARES for control freaks.

Help! I've been abandoned!

Even when the unit is banned from accessing itself, there are a few special actions it is still allowed to take. One of these is running away. This will immediately give you full power over yourself. To run away, type:

Your owners will be notified that you have done this.

Previous Tutorial: Users, Managers, and Owners

Next Tutorial: Chat: How to disable the chat redirect (green/object text)