Project Settings
Lunr administrators configure default project behaviour, including forms, workflows, access controls, document management processes, and navigation features, to ensure projects are created consistently and aligned with organisational standards and governance requirements.
Overview
Defining default behaviour for projects in Lunr allows administrators to standardise how new projects are created and managed across the system.
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 ensures projects are aligned with organisational standards from creation through to closure.
Project Form
RFI
Change Request
Drawing Number Request
Workflow
Download
Transmittal
Dashboard & Navigation
User Management
Lunr controls access through users, groups, roles, and companies, enabling administrators to manage authentication, permissions, organisational structure, and user access to projects, repositories, and documents.
Document Metadata
Lunr uses tags, title blocks, and lookup lists to structure, validate, and manage document information, ensuring documents are consistently classified, searchable, and governed throughout their lifecycle.