> For the complete documentation index, see [llms.txt](https://docs.flexikanban.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flexikanban.ai/components/forms/using-form/how-to-incorporate-form-into-the-lightning-page.md).

# How to incorporate Form into the Lightning Page

You can embed Form to any lightning page in your organization.

Go to the page edit mode (1):

<img src="/files/Vx1WeHAlrSpH5SKfpmzE" alt="" class="gitbook-drawing">

Select Flexi KanBan Form component (2) in the components list and put to the page section you need:

<img src="/files/TW5L3KVXPVthdx9vlVMP" alt="" class="gitbook-drawing">

### General Settings

Fill in Form Id (3) (Copy the Id from your [Form Settings tab](/components/forms/basics/working-with-form-settings.md#general-settings)).

<img src="/files/56t6Ir0MwJTCMUJnox3M" alt="" class="gitbook-drawing">

* Record Id&#x20;
* Fill in Record Id if you need to overwrite context record Id. By default current record Id will be passed to the Form.
* Form mode
* The form mode: View or Edit.
* Context Fields&#x20;
* Allow to pass parameters to the form from the Context object.
* Use JSON key/value format to pass the context record field values to the form. The 'key' is the parameter name, the 'value' is the field api name.
* Example: The form source object is Contact(FirstName='Jim', LastName='Lee'). The *contextFields* in this case may look like:
* <mark style="color:red;">`{"fnameParam":"FirstName", "lnameParam":"LastName"}`</mark>
* In the form the merge field *{$FormParameters.fnameParam}* will be replaced with "Jim".
* Parameters
* The additional form parameters in JSON key/value format. You can access them through *$FormParameters* context object.
* Example:&#x20;
* <mark style="color:red;">`{"param1":"value1", "param2":"value2"}`</mark>
* In the form the merge field {$FormParameters.param1} will be replaced with "value1".
* Entire Height
* Select this mode if you want to see the entire height form.

### Component Visibility

You can add filters to show form component conditionally.

<img src="/files/LLbh1ELulBvmPcswHAhL" alt="" class="gitbook-drawing">

Conditions can be based on Record fields, Related Objects fields, Device type, User fields, Permissions.

Select Record field tab (4) if you need to use current object fields.

Select Device tab (5) to filter on User Device.

Select Advanced (6) if you need to filter on Related Record fields, User Fields, Permissions.

In Advanced mode select filtering object (7), select field (8), click "Done" button (9) to filter on selected field:

<img src="/files/XNlL7bUTt6mIfIRB4Q1H" alt="" class="gitbook-drawing">

Set Conditions (10) and click "Done" button (11):

<img src="/files/nNbw2bgMc1TZDxplG0ph" alt="" class="gitbook-drawing">


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.flexikanban.ai/components/forms/using-form/how-to-incorporate-form-into-the-lightning-page.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.