Organize projects with categories

Create consistent categories and use them to improve project discovery. Organize projects with categories keeps the project record connected to its owner, current state, evidence and accepted outcome. Use it inside the authorized project instead of maintaining a separate shadow record. Open the intended workspace and project, then confirm the project name and current status. Check that your project role includes the section and action you need. Prepare only the source records or evidence required for this task. Navigate to Organize projects with categories from the project menu. Shared Sample projects are visible for learning but remain read-only. Check ownership, status, revision and linked evidence before making a change. Resolve any stale-version warning instead of overwriting it. Use the defined fields and approved files. Keep identifiers, dates and technical values aligned with the source evidence. Wait for the confirmed save or upload result, then review history, status and downstream links before leaving the page. AutoNexit records project evidence; it does not replace engineering approval, functional-safety review, manufacturer instructions or site authorization. Never treat a document status as permission to energize or operate equipment. A permission message means the project role or explicit section access does not allow that operation. A shared Sample warning is intentional: Sample records cannot be edited, cloned or converted into a real project. A stale or conflict message means the record changed elsewhere; reload, compare and apply the update again deliberately. An upload or capacity error must be resolved before the record can claim the file was saved.