Jump to content

RefractTrack Users

From Pixel Refraction Studio
Revision as of 23:27, 27 August 2026 by Nerdofepic (talk | contribs) (Created page with "== Users == === No public signup === RefractTrack has no self-service registration. Accounts are added by an existing teammate with <code><nowiki>users:create</nowiki></code> (from Users → Add user), or bootstrapped from the command line for the very first account: <pre> php scripts/create_user.php jdoe "Jane Doe" </pre> This prompts for a password interactively. === Adding users === The Add User form (<code><nowiki>user_form.php</nowiki></code>) can generate a r...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Users

No public signup

RefractTrack has no self-service registration. Accounts are added by an existing teammate with users:create (from Users → Add user), or bootstrapped from the command line for the very first account:

php scripts/create_user.php jdoe "Jane Doe"

This prompts for a password interactively.

Adding users

The Add User form (user_form.php) can generate a random password automatically rather than requiring the admin to invent one. When creating a user, an admin sets:

  • Username and display name
  • Password (or generated)
  • Permissions — either applied from a role preset or set individually (see Permissions and Roles)
  • Project access — which projects the user can work in

Editing users

Editing is split across distinct permissions so these can be granted independently:

  • users:edit:contents — display name and password (usernames can't be changed after creation)
  • users:edit:permissions — the permissions granted to the user
  • users:edit:projects — which projects the user has access to
  • users:activate — activating/deactivating the account

Activation and live permission checks

Deactivating a user takes effect immediately: current_user() re-checks the database on every request, so a deactivation (or a permission change) applies right away rather than waiting for the user's next login.