Every project uses one Observation Profile, which decides the classes and fields available when recording findings.
The profile is set in the upload wizard, on the Setup step, alongside the project's title and asset type. See Setting up your upload.
Pick the profile matching the kind of inspection. A bridge profile on a building project gives your inspectors the wrong classes.
Those defined in the workspace the project belongs to. A profile in another workspace is not offered. If the one you want is elsewhere, either create the project in that workspace or recreate the profile where you need it.
Changing a project's profile needs Admin access to that project. Editors can record findings but not change which profile the project uses.
Changing it after observations exist is not something to do casually: those observations carry classes and field values from the old profile, and the new one may not have matching ones.
If you have recorded nothing yet, changing is harmless.
Profiles are made to be shared. A workspace inspecting twenty bridges should have one bridge profile used by all twenty, so findings are comparable and reports read consistently.
A profile can also be copied into other workspaces, which is how one agreed standard reaches several of them. Each copy is then independent. See Setting up Observation Profiles.
The trade-off is that a shared profile locks quickly, so get the classes and fields right before the first project goes live. See Understanding locked Observation Profile edits.
| What you see | What it means |
| The profile is not in the list | It belongs to a different workspace. |
| No profiles at all | The workspace has none yet. A workspace administrator creates them. |
| The field is greyed in the wizard | You lack permission to create projects here. |
| The profile cannot be changed on an existing project | You need Admin access to the project. |