Jump to content

RefractSurvey Projects

From Pixel Refraction Studio
Revision as of 13:50, 13 September 2026 by Nerdofepic (talk | contribs) (Created page with "A '''project''' is the top-level container in RefractSurvey. Every survey, every access code, and every uploaded image belongs to exactly one project. thumb|center|600px|The Projects list, under Manage. == Why projects exist == If you're working on more than one game, or you want to keep an internal team survey cleanly separate from a public playtest, projects are how you do that. There's no limit on how many you can create, and no...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

A project is the top-level container in RefractSurvey. Every survey, every access code, and every uploaded image belongs to exactly one project.

The Projects list, under Manage.

Why projects exist

If you're working on more than one game, or you want to keep an internal team survey cleanly separate from a public playtest, projects are how you do that. There's no limit on how many you can create, and no per-project fee — see Cost Breakdown.

A brand new install starts with none; you create your first one as the last step of the install wizard (see Getting Started).

Creating a project

From Manage > Projects, click New project and give it a name and (optionally) a short description. Right after creating it, you'll be shown a checklist of every other active user on your install so you can immediately decide who else should be able to access it — this is purely additive, so it's a fast way to grant a whole team access at once without visiting each person's account individually.

Switching between projects

If you have access to more than one project, a dropdown in the top navigation bar lets you switch which one is "current." Most of the app (Surveys, Media Library, Import) works within whichever project is currently selected.

Deactivating a project

Projects can be deactivated rather than deleted — useful once a game has shipped and you don't need to keep collecting feedback for it, but still want to keep the historical responses around.

Who can see this

Whether someone can see or manage a project at all depends on both their permissions and whether they've specifically been granted access to that project — see Permissions and Roles for the full picture. Templates are the one exception: they're shared across every project on the install rather than belonging to just one.

See also