> ## Documentation Index
> Fetch the complete documentation index at: https://docs.insight.nobly.dk/llms.txt
> Use this file to discover all available pages before exploring further.
# Administration
> Permissions for form configuration, the rights users need, what makes a document a form document, and how form documents behave across Nobly Insight.
## Permissions
Designing form templates is governed by the **Form configuration** area of the [application permissions](/permissions/application-permissions#form-configuration). It follows the usual tiers:
| Permission | Grants |
| ------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| **View form configuration** | Open **Settings → Documents → Form templates**, see every document type's templates and their version history. |
| **Manage form configuration** | Create, edit and delete templates, set or unset the default, restore versions, and use the AI assistant. Includes **View**. |
| **Form configuration administration** | Full control of the area, including any permission added to it later. Includes **Manage** and **View**. |
Grant them on the [Permissions screen](/permissions/managing-permissions) to the user groups that design forms. When form documents become available in your environment, the three permissions are granted automatically to the **MANAGER** and **NOBLY-MANAGERS** user groups where those groups exist, so an established administration group can start without a separate grant. The automatic grant is recorded in the permission audit log like any other, and can be revoked there.
Form configuration permissions cover *designing* templates only. They grant no access to any document: opening, creating and editing a form document is governed by the document type's [access rights](/configuration/document-access-rights), exactly as for a file document.
## What users need
| To | The user needs |
| -------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| See **New form** and create a form document in a document type | A **create** template selectable for the user on that type, and the type's **document creation**, **document viewing** and **view keywords** rights. **New form** appears only when at least one document type qualifies. |
| Open a form document | The type's **document viewing** and **view keywords** rights, as for any document. The preview template — or the generic layout — shows what the keyword panel would show. |
| Use **Edit form** | The **modify keywords** right on the type, and an **update** template selectable for the user. |
| See restricted keywords on the form | The right to access restricted keywords. Without it, keywords hidden by configuration stay hidden on the form as they do in the keyword panel. A keyword hidden by a conditional rule is hidden for everyone. |
Template selection is per user group, so two people with the same document rights can see different forms — see [template selection](/forms/templates#template-selection).
## Which documents are form documents
Nobly Insight treats a document as a form document when it has no file content: it was created through **New form**, or it is a legacy electronic form whose only content is its keywords. The distinction is made per document, not per document type. A document type can hold both files and form documents, which is what happens when an archive of electronic forms also receives scanned or uploaded files.
Nothing has to be configured for an existing archive. Its documents show through the generic layout until you give the document type a preview template, and their keywords remain editable through the keyword panel until you add an update template. The old form layouts of legacy electronic forms are not used; design the templates you want in the [designer](/forms/templates#the-designer).
Any document type can hold form templates. A type without a create template never appears on **New form**, and its existing documents are unaffected.
## How form documents behave across the product
| Area | Behaviour |
| --------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Search** | Form documents are found by keyword search like any other document. Result rows show a form icon in place of the file-type icon, and the preview pane renders the type's preview template. AI search finds documents by their file content; a form document has none, so search for it by keywords. |
| **Viewer** | The preview template replaces the file viewer. Keyword panel, document information, history, notes, follow and links work as usual. **Edit form** shows the update template; while it is open the keyword panel is read-only so the two never compete for the same values, and **Stop editing** returns to the preview. |
| **File actions** | Download, revisions, upload new revision, Office editing, redaction and annotation do not apply and are unavailable. The document's history is its keyword history. |
| **Keyword rules** | Saving from a form goes through the same validation as the keyword panel: required keywords, masks and lengths, datasets, cascading values, autofill sets, conditional rules, revision comments and duplicate detection. |
| **Re-indexing** | A form document re-indexed into another document type stays a form document and is shown through the target type's templates. |
| **Retention, workflows, events, notes** | Apply unchanged. A form document is a document of its type. |
| **API and integrations** | Form documents are created through the API with keywords only, and document metadata and search results carry a content kind of *Form* so integrations can tell them from files. |
## Troubleshooting
The entry appears only when the user can create a form document in at least one document type. Check, for the intended type:
* A **create** template exists and is selectable for the user — assigned to one of their user groups, or marked default.
* The user's groups hold **document creation**, **document viewing** and **view keywords** on the type.
The generic layout is used when no preview template is selectable for the user. Check that the document type has a preview template that is either the default or assigned to one of the user's groups. Group templates need a precedence to be saved, so the designed template may never have been stored.
**Edit form** needs both the **modify keywords** right on the document type and a selectable **update** template. Without an update template, keywords are still editable through the keyword panel.
In order of likelihood:
* The keyword is not assigned to the document type — a `KeywordField` for an unassigned keyword is reported by the lint and rendered as unknown.
* The keyword is hidden by the [keyword configuration](/configuration/keyword-behaviour) or by a conditional rule for the current values.
* It is a restricted keyword and the user lacks the right to see it.
* The template binds it by a name that differs from the configured keyword name; bind by `keywordTypeId` instead.
Check:
* The template has no name or no content.
* User groups are assigned without a precedence, or the precedence collides with another group template of the same type on the document type.
* The template was changed by someone else since it was opened; reload the version history and apply the change again.
Lint findings never refuse a save. A template that saves but renders wrongly usually has errors in the **Problems** panel.
A create is refused when the document type no longer has a create template selectable for the user, when a required keyword is empty — including required keywords the template does not show — or when a value fails its keyword type's mask or length. The form reports the reason next to the create button.
## Rollout checklist
1. Give every document type that will hold form documents a **preview** template, and a **create** template where users are to create documents in it.
2. Add an **update** template where users are to edit through the form rather than the keyword panel.
3. Preview each template against a **real document** of the type before making it the default.
4. Assign group templates deliberately: a precedence per group template, and a default as the fallback.
5. Test with a user who holds only the intended document rights, not with a member of a bootstrap group.
6. Check the keyword configuration of the type — required, hidden and conditional keywords apply to the form whether or not the template shows them.
## Where to read next
What users see once the templates and rights are in place: New form, the create form, and the stored document.
The full permission catalogue, including the form configuration tiers.
The per-document-type rights that decide who can open, create and edit form documents.