Skip to content
English - United States
  • There are no suggestions because the search field is empty.

What are the General features of Lumion Cloud?

LCloud-Placeholder-mktg1.jpg

 

TO DO:

Revamp and extract from the tables 

add a few more screencaps

maybe add some extra explanations

can fill out more over time

 

[PURPOSE]: To cover the other features in basic terms and to cover all features given we are supposed to be doing the documentation [public] [Requirement from ...]

 

Structure:

each of the other features basically form the Lumion_Cloud_BETA_PRD

 

  1. General platform features

  1. Feature: Profile & Auth Settings

see also My Profile article: My Lumion Cloud Profile

Field
Description
Description
Lets users edit personal information, change password, link Google account, and enable 2FA.
Purpose

Provides account management and enhanced security options.

User Problem

Users need to update their info and secure their account.

Assumptions
User is logged in and has access to security settings.
Not Doing

Social login beyond Google, advanced security analytics.

Dependencies

Auth API, Google OAuth, 2FA provider.

Acceptance Criteria
Editable fields for name/email, profile picture upload, password change, Google link, 2FA setup.
  1. Feature: In-app & Email Preferences

Field
Description
Description
The Profile Settings screen allows users to view and edit their personal information, manage authentication (password, Google account), and set up two-factor authentication (2FA). The interface is organized with tabs for profile and notification preferences.
Purpose
To provide users with a secure and convenient way to manage their account details and enhance account security.
User Problem
Users need to update their personal info, change their password, link external accounts, and enable 2FA to protect their account.
Assumptions
User is authenticated and has access to account settings; integration with authentication and 2FA services is available.
Not Doing
Advanced security analytics, social logins beyond Google, or account deletion from this screen.
Dependencies
User profile API, authentication service, Google OAuth integration, 2FA provider.
Acceptance Criteria

Profile tab is visible and accessible

Personal info fields (first name, last name, email) are editable

Profile picture can be changed

Password can be updated via masked input and edit button

Option to link Google account is present

2FA setup section is available with setup button

Save button is present for changes

 

  1. Feature: Searching

>>should be linked from other articles to here: as Searching is a common core feature of usage

Field
Description
Description
The dashboard features a prominent, centered search bar that allows users to search for projects, renders, and (out of scope) pages, with a dropdown displaying categorized search results for quick access.
Purpose
To enable users to quickly locate projects and renders from anywhere , improving efficiency and navigation.
User Problem
Users need a fast, centralized way to find specific projects or renders without manually browsing through lists or folders.
Assumptions
User has multiple projects/renders and expects instant, relevant search results; search is accessible from the main dashboard.
Not Doing
Searching for “pages” or static content within the platform; advanced filtering or search within file contents.
Dependencies
Search API/service, project and render metadata indexing, UI for dropdown results.
Acceptance Criteria

Search bar is visible and accessible from dashboard

Dropdown shows categorized results for projects and renders

Results are relevant and clickable

 

  1. Feature: Notifications

>> link to here from mentions in other articles

Field
Description
Description
The dashboard displays a notification icon with a badge in the header; clicking it opens a pop-up panel showing recent notifications with thumbnails, titles, timestamps, and options to mark all as read or access settings.
Purpose
To keep users informed of important updates (e.g., comments, project changes) and provide quick, centralized access to recent activity directly from the dashboard.
User Problem
Users need to stay updated on project activity and feedback without navigating away from their main workspace or missing critical updates.
Assumptions
User is logged in, has active projects or collaborations, and receives notifications relevant to their activity or role.
Not Doing
In-depth notification filtering, advanced notification customization, or direct action (e.g., reply) from the notification panel.
Dependencies
Notification service/API, user profile and project activity tracking.
Acceptance Criteria

Notification icon with badge in header

Pop-up panel with recent notifications

Thumbnails, titles, timestamps for each notification

Options to mark all as read and access notification settings

Seamless access from dashboard

 

  1. Feature: Sharing folders and renders

>> this has more detailed covering in How do you share Lumion Cloud content?

Field
Description
Description
A modal popup for sharing renders or folders, allowing users to invite others by email, assign roles, manage access levels (private/public), copy a shareable link, generate a QR code, and view/manage the list of people with access.
Purpose
To provide a secure, flexible, and user-friendly way to share renders or folders with collaborators or external stakeholders, while controlling access and permissions.
User Problem
Users need to easily share content with specific people or publicly, manage who can view or edit, and quickly distribute access via link or QR code.
Assumptions
The user has permission to share the render/folder; email invitations and access management are supported; roles and public/private access are configurable.
Not Doing
Advanced sharing analytics, time-limited links, or custom access expiration settings.
Dependencies

User management and role APIs, email invitation service, link generation, QR code generator, access control logic.

Acceptance Criteria

Modal window opens with “Share render” title

Email input field and role dropdown for inviting users

Send invitation button is present

Access level dropdown allows switching between private (invited only) and public (anyone with link)

List of users with avatars, names, and roles (Owner, Admin, Editor, Viewer)

Expandable user list with “see more” arrow

Copy link button is present

QR code button is present

 

  1. Feature: Moving folders and renders

>> this is file management, point to here from Projects Screen and Render Screen

Field
Description
Description
A modal dialog for moving one or more renders or folders to a new location, featuring a searchable folder tree, current location display, and options to create new folders or confirm the move.
Purpose
To enable users to efficiently reorganize their files and folders by moving them to the desired destination within the workspace.
User Problem
Users need a simple, intuitive way to move files/folders, especially when managing large or complex folder structures, while respecting permissions.
Assumptions
User has permission to move the selected items; folder structure is accessible; context menu triggers the dialog; multiple selection is supported.
Not Doing
Bulk permission editing, moving across different workspaces/organizations, or advanced conflict resolution.
Dependencies
File/folder management APIs, permission and rights logic, UI for folder navigation and search, context menu integration.
Acceptance Criteria

Modal dialog opens with “Move to” title

Current location and destination path are displayed

Search bar allows filtering folders

Folder tree is navigable and supports expanding/collapsing

Selected destination is highlighted

“New folder” button is present for creating subfolders

“Save” button confirms the move

Checkmarks indicate selected items

Permissions are checked before move; errors shown if move is not allowed

  1. Feature: Permissions and user roles (TBD)

>> might require separate article with more indepths and FAQ

(Example Concept/reference)

Field
Description
Description
Permissions Management provides a clear, role-based access control system for projects and assets. It uses a permissions matrix to define what actions each user role (e.g., Project Owner, Admin, Editor, Viewer) can perform, such as user management, project/asset management, and commenting.
Purpose
To ensure secure, granular control over who can view, edit, manage, or comment on projects and assets, supporting collaboration while protecting sensitive data and workflows.
User Problem
Users and admins need to easily understand and manage who can do what within a project, reducing the risk of unauthorized changes or confusion about access rights.
Assumptions
All user roles are clearly defined; permissions can be updated as needed; external users (e.g., via email invite) have limited, controlled access.
Not Doing
Custom, per-user permissions outside of predefined roles; advanced audit logging or permission history tracking in MVP.
Dependencies
User and role management APIs, UI for permissions matrix, project and asset access control logic.
Acceptance Criteria
Permissions matrix is accessible from the settings