Reference
Arcane.users
Arcane user administration and shell configuration.
This focused page is derived from the mechanically checked full member inventory.
Syntax
Arcane.users
Member kind
Namespace
Description
Arcane user administration and shell configuration.
Overview
Arcane.users owns the Provisioner's bounded account inventory, validation,
creation, activation, temporary-password flow, and shell verification or
restoration. Usernames are explicit inputs; password application is separate
from password reset so the application can control disclosure and confirmation.
Availability and security
Every method requires users.manage and the provisioner app type. Account and
shell mutations add privilege or exclusive-mutation controls as declared by
policy. Temporary passwords are sensitive: never log, persist, or place them in
diagnostic examples.
Example
const access = await globalThis.Arcane.capabilities.list();
const canValidateUsers = access.methods.includes('users.validate');
console.log('User validation admitted:', canValidateUsers);
Members
Arcane.users.list()— Lists supported local users plus the platform username policy and accounts the Provisioner must not convert.Arcane.users.validate()— Validates candidate usernames without changing an account.Arcane.users.add()— Creates/configures local Arcane users and returns sensitive temporary credentials for protected presentation.Arcane.users.activate()— Activates a staged configured user.Arcane.users.resetPassword()— Prepares a temporary credential but does not change the operating-system password; apply it with users.applyPassword().Arcane.users.applyPassword()— Performs the privileged native password mutation and forces change at next sign-in.Arcane.users.verifyShell()— Verifies the user's Arcane shell configuration.Arcane.users.restoreShell()— Restores the recorded supported shell configuration.