Everything a service offers, grouped by what you would be trying to achieve. These are the service’s own tools; each module has its own feature set documented separately.
| Feature |
What it does |
| Module list |
Every module available here, grouped by purpose, with a badge for beta and new ones |
| Setup state |
Each module shows either Set up → or a count of what it already holds |
| Module search |
Filters the module list by name |
| Module create actions |
Each module landing page provides the creation flow and options for that type of work |
| Feature |
What it does |
| Service name and description |
What the service is called and what it is for |
| Department |
The part of the organisation it belongs to |
| Owner |
The person accountable for it |
| Tags |
Up to 12 labels, so it is easy to spot in the catalogue |
| Icon |
A single emoji |
| Accent colour |
Tints the service wherever it appears |
| Banner |
An image, chosen or generated in this service’s Image Generation module |
| Feature |
What it does |
| Module toggles |
Turn off the modules this service does not use, to keep its sidebar focused |
| Non-destructive |
Nothing is deleted. Turning a module back on restores it with its content |
| New modules |
Modules added to the platform later are enabled automatically |
| Feature |
What it does |
| Members |
Individuals given direct access to this service |
| Teams |
Link a platform team so all of its members get access |
| Roles |
Owner, admin, editor, and member, which decide what each person may do |
| Audit log |
Every action taken in the service |
| Audit filters |
By action — created, updated, deleted, archived, moved, completed, approved, rejected, exported, imported, assigned, linked, cloned and more |
| Actor type |
Filter by whether a human, a scheduled job, an AI, or the system did it |
| Audit export |
CSV or JSON |
The actor filter is worth knowing about. As more work is done by automations and AI agents, “who changed this?” stops having a human answer, and the log records which kind of actor it was.
| Feature |
What it does |
| Internal Publisher access |
The widest audience any item hosted inside Lunar Paper may use — service members or anyone signed in |
| A maximum, not a default |
Individual items may be stricter. The setting is a ceiling, not a switch that publishes anything |
| Sign-in always required |
The Internal Publisher always requires sign-in, whatever the setting |
| External publishing |
Whether items here may be published anonymously outside Lunar Paper at all |
| Publisher allow-list |
Any registered external publisher, or only selected ones |
| Feature |
What it does |
| Artifact Map |
Draws every connected artifact and the relationships between them |
| Artifact count |
How many artifacts and relationships exist |
| Type filters |
Show or hide flowcharts, dashboards, pages, data sources, data views, projects, task boards, email templates, and campaigns |
| Groups |
Collapse the map into groups |
| Zoom and reset |
Move around a large map |
| Honest exclusions |
The map states what it is not drawing — unreferenced assets, tasks counted on their board, and resources with no allocation |
Nine artifact types are drawn. Artifacts and the Artifact Map covers each one and what it connects to.
Reached from Assets. Covered in full on Asset Library.
| Feature |
What it does |
| Automatic cataloguing |
Everything a module creates appears here without being added |
| Upload |
Adds files from your machine alongside them |
| Folders |
A tree for organising assets |
| Collections |
Group assets from across folders — a campaign set, a pitch deck |
| Lifecycle states |
Draft, In Review, Published, Shared, Deprecated, Archived |
| Rights filters |
Expiring soon and rights expired, for licensed material |
| Starring |
Mark assets you return to |
| Grid and list views |
Two ways to browse the same set |
| Asset analytics |
Views, downloads, uses, and totals over 7, 30, or 90 days |
| Most popular assets |
Ranked usage, plus recent activity and storage by type |
| Duplicate detection |
Scans for duplicate files to save storage |
| System assets |
Shown or hidden with a toggle |
| File filters |
By type, date range, and size |
| Automatic metadata |
File type, size, dimensions, thumbnail, file hash, and perceptual hash |
| Custom metadata fields |
Text, textarea, number, date, select, and boolean |
| Required at upload |
A required field blocks an upload that omits it, enforced on the server |
| Field scoping |
A field can apply to every asset type or only to listed ones |
| Feature |
What it does |
| Friendly URL |
A readable link such as /s/app-user-guides. The numeric link keeps working |
| Catalogue visibility |
Hide the service from lists while keeping it reachable by direct link |
| Duplicate service |
Create a new service with this one’s configuration. Content is not copied |
| Archive service |
Retire a service that is no longer in use |
| Service metadata |
Service ID, who created it, when it was created, and when it was last updated |
| Not available |
Detail |
| Sharing content between services |
A service is a boundary. Content belongs to one |
| Per-module membership |
Membership is service-wide. A member of the service can reach every module in it |
| Publishing on its own |
Content Access sets a ceiling; each item still chooses whether and where to publish |
| Copying content when duplicating |
Duplicate copies the configuration, not the work |
Quickstart sets a service up from scratch. Capabilities maps each feature to the page that covers it.
