Ideas

Allow users to add an additional column (or field) for alternate names (e.g. "Name #2" or "AKA") when defining information requirements. This helps support workflows where the same parameter might have different names across multiple modeling platforms. The system should recognize either name when checking against model elements for compliance.

The date is always written with the US format which is not used elsewhere, e.g. May 13, 2025, even when it is translated to the project language. We would prefer a short or long version of the local date format, as given by the project language. E.g. if the project language is german: short date = 13.05.2025 long date = 13. Mai 2025

We are using ACC Docs as our main CDE and it would be very beneficial if we could export and sync Plannerly's files in File Manager directly to a specific path/folder in ACC docs. This way when you update the document and export a new version ACC will automatically get updated.

Would like issues from ACC to be in Plannerly Track. That way tasks and issues can be tracked together.

A more strategic way to manage people, teams, and permissions across all workspaces and projects from one place. Proposed approach: A new centralized Team Management dashboard to view and control user access across the entire account. Simplify adding, removing, or adjusting roles across multiple workspaces and projects. Add the ability to copy team structures (members and roles) from one project to another for faster setup. Include granular workspace permissions, such as: - Can create and delete only their own projects - Can create and delete any projects in the workspace - Cannot create or delete projects (view/edit only) This would make permission management faster, clearer, and more scalable across large organizations.

Would be great to apply information requirements across all elements in a scope folder or even project wide, thanks.

The ability to see when a user (team members) last logged in to the project. In addition to tracking user activity, it would be beneficial to include user login activity within the project feed. This added visibility into when and how users are accessing the project can provide valuable data for analysis purposes.

Syncing files between Sharepoint and the filtered folders in Plannerly's File Manager

When connecting a model to the tasks you need to have the tree sorted by element types to assign PILES to piles tasks and DOORS to doors task. The direct attribute NAME is actually the human readable unique name of the element (essentially = GLOBALID) and the type should be in the attribute OBJECTTYPE. There could be an option to build the tree by any attribute.

When I’m in a project, it would be easier to have an arrow in the top left corner that I could click on to go from a drop-down list to another project. Now a little bit complicated a project changing.