RefractTrack Users - Revision history

Nerdofepic at 22:59, 11 September 2026

2026-09-11T22:59:50Z

← Older revision		Revision as of 22:59, 11 September 2026
Line 15:		Line 15:

	Display name, password, permissions, and project access can each be updated independently — so, for example, someone can be trusted to update a teammate's password without also being able to change what that teammate is allowed to do. Usernames can't be changed once an account is created.		Display name, password, permissions, and project access can each be updated independently — so, for example, someone can be trusted to update a teammate's password without also being able to change what that teammate is allowed to do. Usernames can't be changed once an account is created.

			Changing someone's password also immediately signs them out of anywhere else they were already logged in — handy peace of mind if a password is being changed because it might have been compromised, rather than just as routine upkeep. Whoever makes the change stays logged into their own session as normal.

	=== Deactivating an account ===		=== Deactivating an account ===

Nerdofepic at 03:35, 3 September 2026

2026-09-03T03:35:43Z

← Older revision		Revision as of 03:35, 3 September 2026
Line 24:		Line 24:
	* [[RefractTrack_Permissions_and_Roles\|Permissions and Roles]]		* [[RefractTrack_Permissions_and_Roles\|Permissions and Roles]]
	* [[RefractTrack_Projects\|Projects]]		* [[RefractTrack_Projects\|Projects]]

			[[Category:RefractTrack]]

Nerdofepic at 00:15, 29 August 2026

2026-08-29T00:15:22Z

← Older revision		Revision as of 00:15, 29 August 2026
Line 1:		Line 1:
	== Users ==		== Users ==

	~~=== No~~ public ~~signup ===~~		RefractTrack doesn't have public sign-up — accounts are added one at a time by an admin, which keeps a self-hosted board like this one closed to anyone you haven't personally invited.

	~~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:~~		=== Adding a teammate ===

	~~<pre>~~		From Users → Add User, an admin fills in:
	~~php scripts/create_user.php jdoe "Jane Doe"~~
	~~</pre>~~

	~~This prompts for~~ a ~~password interactively~~.		* A username and display name
			* A password (RefractTrack can generate a strong one automatically, so nobody has to invent one on the spot)
			* Permissions — either applied from a ready-made role, or set individually. See [[RefractTrack_Permissions_and_Roles\|Permissions and Roles]].
			* Which projects they should have access to

	=== ~~Adding users~~ ===		=== Editing a teammate's account ===

	~~The Add User form (<code><nowiki>user_form.php</nowiki></code>)~~ can ~~generate~~ a ~~random~~ password ~~automatically rather than requiring the admin~~ to ~~invent one~~. ~~When creating a user,~~ an ~~admin sets:~~		Display name, password, permissions, and project access can each be updated independently — so, for example, someone can be trusted to update a teammate's password without also being able to change what that teammate is allowed to do. Usernames can't be changed once an account is created.

	* Username and display name		=== Deactivating an account ===
	* Password (or generated)
	* Permissions — either applied from a role preset or set individually (see [[RefractTrack_Permissions_and_Roles\|Permissions and Roles]])
	* Project access — which projects the user can work in

	~~=== Editing users ===~~		Deactivating someone's account takes effect immediately — as soon as it happens, they're logged out of anything they try to do next, rather than staying active until they happen to log in again.

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

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

	~~=== Activation and live permission checks ===~~

	~~Deactivating a user~~ takes effect immediately~~: <code><nowiki>current_user()</nowiki></code>~~ 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~~.

	=== Related pages ===		=== Related pages ===
Line 37:		Line 24:
	* [[RefractTrack_Permissions_and_Roles\|Permissions and Roles]]		* [[RefractTrack_Permissions_and_Roles\|Permissions and Roles]]
	* [[RefractTrack_Projects\|Projects]]		* [[RefractTrack_Projects\|Projects]]
	* [[RefractTrack_Security\|Security]]

Nerdofepic: Created page with "== 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 r..."

2026-08-27T23:27:21Z

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..."

New page

== 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 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 [[RefractTrack_Permissions_and_Roles|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:

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

=== Activation and live permission checks ===

Deactivating a user takes effect immediately: <code><nowiki>current_user()</nowiki></code> 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.

=== Related pages ===

* [[RefractTrack_Permissions_and_Roles|Permissions and Roles]]
* [[RefractTrack_Projects|Projects]]
* [[RefractTrack_Security|Security]]