Project Settings

Per-project configuration covering the project form, RFI, Change Request, Drawing Number Request, Checklist, Workflow, Download, Transmittal, and Dashboard & Navigation settings.

Overview

The Project Settings section lets administrators standardise how projects are created and managed across the tenant. It requires the Administration Pages access right.

Project defaults can be configured to automatically apply predefined settings such as document types, workflows, access controls, metadata values, folder structures, and naming conventions when a project is created. This ensures consistency, reduces manual configuration effort, and helps enforce governance and compliance requirements from the outset.

Default behaviours also provide a predictable baseline that users can work within, while still allowing controlled exceptions where required. Careful definition of project defaults is particularly important in environments with a high volume of projects, as it improves scalability, reduces configuration errors, and keeps projects aligned with organisational standards from creation through to closure.

These settings apply per project. For settings that apply to every user and every project in the tenant instead, see General Settings.

Project Form

Project Form controls which fields appear on the project create and edit form, whether they are required, and a handful of related project-level feature toggles.

Project Settings page on the Project Form tab, showing the nine-tab strip and the Start Date, Due Date, Document Controller, Project Manager, Project Type, Project Number, Project Status, Project Manager Label, Project Templates, CR Only Member Type, and Project Folder settings

Setting	What it controls
Start Date visible / Start Date required	Show the Start Date field on the project form, and whether users must supply a value when creating a project.
Due Date visible / Due Date required	Show the Due Date field on the project form, and whether users must supply a value when creating a project.
Is Create Project Role visible?	Give users the option of creating a role to associate with the project.
Is Document Controller field visible? / Is Document Controller field required?	Show the Document Controller field on the project form, and whether a value is required.
Is Project Manager field required?	Require a value in the Project Manager field.
Is External Project Manager field visible?	Give users the option of selecting an external project manager when creating a project.
Is Project Type field required?	Require a value in the Project Type field.
Is Project Number unique?	Prevent creation of multiple projects that share the same project number.
Disable project number registration routing?	Turn off routing self-registrations based on the supplied project number.
Enabled Project Status field?	Include the Project Status field on the project create and edit form.
Project Manager Label	Rename the Project Manager field throughout the project UI, so an organisation can call the role whatever it calls it internally.
Enable Project Templates?	Turn on project templates, letting users create and use templates for quick project setup.
Enable CR Only Member Type?	Allow project members to have restricted (CR Only) access instead of full access. When disabled, every member gets full access.
Display Project Folder?	Show project folder locations on the project details page.

Not an access right

Document Controller here is a field on the project form, not an access right. There is no Document Controller access right in Lunr.

RFI

RFI controls whether RFIs are enabled for projects, and how they are labelled and displayed.

Setting	What it controls
Is RFI Enabled?	Allow users to create RFIs in Lunr.
RFI Label	Rename "RFI" throughout the project UI. This is why the user guide says RFIs can appear labelled with an organisation's own wording.
RFI Description Note	Multi-line help text shown alongside the RFI description field.
Show 'Create' Menu in the Repository view?	Allow users to create or upload documents directly into the repository. Despite sitting on the RFI tab, this setting governs document creation rather than RFIs.
Table Columns	JSON configuration of the columns shown in the RFI table.

Change Request

Change Request is the largest tab, so it is split into six pages: Form, Priority & Due Dates, Reviewers & Workflow, Documents, Numbering, and Advanced. Choose a page from the list down the left of the tab, or from the dropdown list above the settings on a narrow screen.

Change Request tab of Project Settings open on the Form page, with the list of six pages down the left and the Full Change Request page, Open by default, Message placeholder, Unique subjects, Project number label, and Default project number settings

Each setting is a row with its name and a short description, and a control on the right. A setting that depends on another is unavailable until that one is enabled, and pointing at it explains which setting to enable first. Changes save as you make them.

Form

Form controls how Change Requests open and what the form asks for.

Setting	What it controls
Full Change Request page	Give users the full Change Request page rather than the standard dialog-based experience. See Change Request Experiences below.
Open by default	Make the full Change Request page the default view when users open Change Requests. Available once Full Change Request page is enabled. Which experience applies is currently decided by Full Change Request page and the repository override alone, so changing this on its own may not alter what users see.
Message placeholder	Guidance text shown in the empty Message box on the full Change Request page. It is never saved as the message. Available once Full Change Request page is enabled.
Unique subjects	Prevent creation of a Change Request whose subject matches another in the same project.
Project number label	Rename the project field on the Change Request form.
Default project number	The project selected by default on new Change Requests and transmittals.

Priority & Due Dates

Priority & Due Dates controls how a priority sets a Change Request's due date.

Setting	What it controls
Priority	Allow users to choose a priority on each Change Request, which sets its due date.
Editable due date	Allow users to change the due date a priority fills in. Without it, the due date follows the priority and cannot be edited.
Priority or due date required	Ask for a priority, a due date, or both, rather than always requiring a priority. The due date can then be set without a priority.

Editable due date and Priority or due date required are available once Priority is enabled.

Under Durations, enter the number of days from today each priority sets the due date to. The priorities themselves come from the ChangeRequestPriority lookup list; select Manage Priorities to edit it on Lookup Lists. Until you enter any durations, Lunr uses its defaults of 1 day for P1, 7 for P2, 30 for P3, 90 for P4, and 180 for P5.

Reviewers & Workflow

Reviewers & Workflow controls who reviews a Change Request and how it moves through its statuses.

Setting	What it controls
Project Manager as reviewer	Add the project's Project Manager as a reviewer on each new Change Request. Enabled by default.
Workflow reviewer selection	Allow users to select reviewers for each workflow status, based on workflow configuration.
Notify reviewers when assigned	Send email notifications to reviewers when they are assigned to review a Change Request.
On hold	Allow reviewers to place Change Requests on hold and resume them later.

Workflow display opens Change Request Workflow Display, for customising the names, ordering, and category of each Change Request status, and the actions that move a request between them.

Documents

Documents controls how documents are added to, organised on, and released from a Change Request.

Setting	What it controls
Folders	Allow users to organise Change Request documents into folders.
Upload v2	Use the newer upload endpoint for Change Request document uploads.
Reference document queue	Show queue status on reference documents attached to Change Requests, and allow managing document processing order. Only users with the View Document Queue or Manage Document Queue access rights see the queue column.
Bulk release	Allow users to release the selected or all valid documents on a Change Request in one step.

PDF export columns opens Change Request Export Columns, for choosing which columns appear in the documents table on the Change Request PDF export, including any document tag.

Numbering

Numbering controls how new Change Requests are numbered.

Setting	What it controls
Sequence numbers	Automatically assign sequence numbers to new Change Requests, based on a number format.

Number formats opens Change Request Number Formats, where you set the pattern new Change Request numbers follow. It is unavailable until Sequence numbers is enabled.

Advanced

Advanced holds settings entered as JSON. Leave a box empty to disable the setting.

Setting	What it controls
Reviewer groups	For each repository, the groups whose members review a Change Request at each workflow status. Statuses not listed use the usual reviewers.
Default project numbers by repository	Repository-specific default projects for new Change Requests and transmittals. Where set, these take precedence over Default project number on the Form page.

Change Request Experiences

Full Change Request page, on the Form page, chooses between the two Change Request experiences Lunr ships. It changes what users see rather than what they are allowed to do, and no data is converted either way, so an existing Change Request opens in whichever experience currently applies.

	Disabled, the standard experience	Enabled, the full page
Raising a request	A dialog asking for a subject and an optional message, plus a project where the user raised it outside one	A full creation page also capturing attachments, tags, priority, due date, and reference documents
Tabs on a request	Documents, Comments, and History, opening on Documents	Adds Overview, which it opens on instead, and Reference Documents
Workflow progress nav	Not shown	Shown across the top of the request
The request's message	In the action pane, with an Edit action	On the Overview tab
Reference documents	Unavailable, including the repository's Add as Reference Documents action	Available, with allocation and bulk allocation

Checklist joins the tabs in both experiences where checklists are enabled.

Change Requests remain fully available with the setting disabled. Users raise them from New Change Request in a project's action pane and work them through the same workflow, reviewers, releasing, and packaging.

A repository can override this

Each document repository carries its own Full Change Request page setting of Use global setting, Enabled for this repository, or Disabled for this repository, described in Repositories. The repository's value wins, so repositories in one organisation can run different experiences, and a Change Request always resolves against the repository it belongs to rather than the one the user is currently in.

Disabling this hides the Create menu entry

With Full Change Request page disabled and no repository overriding it, the Change Request entry is hidden from the Create menu across the application, including in the repository. New Change Request in a project's action pane is unaffected, so users can still raise requests, but only from inside a project.

Change Requests in the user guide covers both experiences from the user's side.

Drawing Number Request

Drawing Number Request controls how drawing number requests are approved and how many sheets a request can cover.

Setting	What it controls
Auto-approve drawing number requests?	Approve drawing number requests automatically, without manual review.
Enabled new sheets option?	Allow users to add new sheets to existing drawing numbers.
Copy content from existing document	Allow users to copy content from an existing document, creating a linked child document.
Asset Id Tag Name	The tag name used to look up an asset ID for facility lookup.
Enable facility lookup?	Turn on facility lookup for drawing number requests.
Max drawing number sheets	The maximum number of sheets a single request can cover, from 1 to 99.

Checklist

Checklist has a single master switch, Are Checklists Enabled?. It allows checklists to be attached to change requests as well as projects, and shows the checklist template library under Administration.

Disabling it hides every checklist surface tenant-wide: the checklist tabs on change requests and projects, the checklist tile on a change request's overview, and the admin Checklist Templates library itself. No existing checklist data is deleted, but the effect reaches beyond the UI: with the switch off, the checklist API refuses every request with "Checklists are not enabled for this tenant", so nothing checklist-related works anywhere in the tenant, not only what disappears from the screen.

No confirmation before disabling

Turning Are Checklists Enabled? off takes effect immediately, with no confirmation prompt, despite disabling checklists across the whole tenant.

Gates another admin area

Are Checklists Enabled? also reveals the Checklist Templates admin page, which additionally requires the Manage Checklist Templates access right. This is the clearest example on this page of one setting opening up another admin area.

Workflow

Workflow has a single setting. Only show Finalise for As Constructed? restricts the Finalise workflow action so it only appears for As Constructed documents.

Download

Download has a single setting. Enable automatic downloads (no prompt)? controls whether a downloaded file saves straight to the downloads folder or the browser asks where to put it, as described in Downloading Documents.

Transmittal

Transmittal controls the transmittal page, its layout, and the labels used on generated transmittals.

Transmittal tab showing the Show Transmittal Page, legend, acknowledgement, compact layout, header field, and label settings

Setting	What it controls
Show Transmittal Page?	Display the transmittal page in projects.
Include legend on transmittals?	Append the document legend to generated transmittals.
Enable transmittal acknowledgement?	Allow recipients to acknowledge received transmittals, the Acknowledge step described in Shares.
Use compact transmittal layout?	Use a simplified layout when generating transmittals.
Include CR ID in header field?	Add the Change Request ID to the transmittal header field.
Transmittal document number label	Rename the document number field shown on transmittals.
Transmittal CR field label	Rename the Change Request field shown on transmittals.
Transmittal tags	Comma-separated list of tags to display on transmittals.
Transmittal group tag	The tag name used to group recipients on a transmittal.

Dashboard & Navigation controls the project dashboard and a handful of navigation defaults.

Setting	What it controls
Show Dashboard?	Show the project dashboard.
Show Change Request Page First?	Make Change Requests the first page users see when they open a project.
Show My Projects Only by Default?	Default the project list to showing only the projects the current user belongs to.
Enable enhanced project documents view?	Uses optimised endpoints for improved performance when browsing and searching project documents.

Saves through General Settings

Enable enhanced project documents view? is the exception on this tab: it actually saves through General Settings rather than Project Settings, and if the save fails, the checkbox silently reverts with no error toast, unlike every other toggle on this page.

On this page