Jump to content

RefractTrack Groups

From Pixel Refraction Studio
Revision as of 23:20, 27 August 2026 by Nerdofepic (talk | contribs) (Created page with "== Groups == Groups are a many-to-many tag on tasks, scoped to a single project — a task can belong to multiple groups at once (e.g. both "Pause UI" and "Localization"). Managed from the Groups page (<code><nowiki>groups.php</nowiki></code> / <code><nowiki>group_form.php</nowiki></code>), gated by <code><nowiki>groups:view</nowiki></code> / <code><nowiki>groups:create</nowiki></code> / <code><nowiki>groups:edit</nowiki></code> / <code><nowiki>groups:delete</nowiki></c...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Groups

Groups are a many-to-many tag on tasks, scoped to a single project — a task can belong to multiple groups at once (e.g. both "Pause UI" and "Localization"). Managed from the Groups page (groups.php / group_form.php), gated by groups:view / groups:create / groups:edit / groups:delete.

Per-project, with a seeded starter set

Groups are per-project, like Stages and Saved Lists: every new project automatically gets a standard starter set — Art, UI, BGM, Gen, SFX, Player, Mob, Boss, Map — each with a distinct color, which can be freely renamed, recolored, deleted, or added to afterward. Nothing about one project's groups affects another project's.

Editing scope

When editing an existing group, the project it belongs to is derived from the group's own project_id, not from the URL or whichever project happens to be "current" in the session — so editing a group while a different project is active in the nav doesn't silently mis-scope the save. (Creating a new group still uses the normally-current project.)

Permissions

Like stages, group management permissions (groups:*) are deliberately not project-scoped — the ability to manage groups at all is a global grant; only which project's groups are being viewed changes per page. See "Project-scoped permissions" in Permissions and Roles.