The full name of the one job or folder the permission window is for, for example team/batch/nightly-report or team/batch. A job or folder of any kind can be named (a Pipeline, a Freestyle project, a folder, a Multibranch Pipeline, ...), but not a part of a job such as a configuration of a multi-configuration project; once the name is recognised, its kind is shown below the field.

The window grants permissions on that item only, and on no other item: to change a job in a folder, request a window for that job. A folder's own settings still affect the items inside it, though (for example implicitly loaded Pipeline libraries), and reconfiguring a Multibranch Pipeline or organization folder can create or delete the items it generates.

• Configure: the item's own configuration. For a job, the job; for a folder, the folder's settings, which the items inside it may use.
• Create: only for a regular folder (not a job, a Multibranch Pipeline or an organization folder). It lets you create new items directly inside that folder, not inside a folder nested in it.
• Delete: only for a job. A folder, Multibranch Pipeline or organization folder cannot be deleted (or moved) through a permission window, because deleting it would also delete everything inside it; ask an administrator.

A window applies only to the item it was approved for. It follows that item when an administrator (or a user with their own permissions) renames or moves it, and ends when the item is deleted. No window allows renaming a job or folder of any kind: neither a Configure window nor Delete and Create windows together. A rename needs an administrator, or your own standing permissions: Configure on the item, or Delete on it plus Create in its parent (the folder that contains it, or Jenkins itself for a top-level item).