> For the complete documentation index, see [llms.txt](https://developer.collibra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.collibra.com/workflows/designing-workflows/forms/form-scopes.md). # Form scopes The scope of a form input component refers to how its value is bound to a variable in the workflow payload. This binding uses expressions enclosed in double curly braces, such as `{{variableName}}`. The scope of a component determines where the value is saved and where it can be accessed. You can use the following predefined scopes for input components: self Refers to data stored at the current process level. This is the default behavior of input form fields. parent Refers to the parent item relative to the current scope, for example the process that initiated the current process. root Refers to the top-level instance and works regardless of where the expression is being used in the execution tree. ## Containers and scopes Container components, such as subforms and panels that store data in a single variable, have their own scopes. To read data from these scoped containers, you must indicate the scope, for example `mySubform.variableName`. Because container components have their own scope, they are limited to it and cannot access data outside of it using the predefined scopes available to input components. To access data from outside the scoped container, use keywords that specify the outer scope: $itemParent Provides read-only access to the parent scope data, for example `{{$itemParent.variableName}}`. $payload Provides read and write access to the full workflow payload, for example `{{$payload.variableName}}`. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://developer.collibra.com/workflows/designing-workflows/forms/form-scopes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.