# Project Settings You can find these in **Project Settings > Codecks Scene Notes**. Some settings are shared with the whole team, others are personal.

Setting	Function
Codecks Project
Org Name	The organisation to pull card data from. The org name is the one that makes up your domain URL. For instance, if your org is on example.codecks.org, the org name will be example.
Default Deck ID	The ID of the default deck in which cards will end up when you create a Scene Note from Unity (they can be moved to another deck later).
Specific Project IDs	The IDs of the projects (in Codecks) that notes will be taken from. It's preferable to choose these by running through the configuration Wizard, but you can also edit them by hand here.
Codecks User
Last Used Email	The last email used to login in the Setup Wizard. This is just stored for convenience, so you don’t have to type it in case you need to login again.
Personal Preferences
Display Title In Scene	If enabled, the title of the note will be visualised in the Scene View alongside the note's icon.
Title Colour	The colour of the title's text (if enabled).
Title Background Colour	The colour of the title's background (if enabled).
Maximum Title Length	The maximum title length when visualising note titles in the Scene View. If a title is longer than this, it will be elided with "..."
Lock Notes You Don't Own	When visualising a note, it will lock it from edits if the currently logged user doesn't match the note's Owner. This is useful to prevent editing other people's notes by mistake. Notes with no Owner will not be locked.
Unity Project
Notes Folder	The folder in the project that Notes ScriptableObjects get created in.

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://tools.continis.io/codecks-scene-notes/other/project-settings.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.