Feature Requests

It is vital that there is a much clearer connection with an opportunity and the project associated with it. During an opportunity there is a lot of discovery. Notes from sales reps, notes from admins and even documents or pictures captures that fall into the NOTES of the opportunity. When the opportunity is WON and CLOSED none of those notes, pics etc come over INTO the project that was created from that opp. It is nice to be able to make properties "shared" and in the same way we need to be able to share the notes, communication etc. It is all part of the project, not seperate. Being told to have the notes at the account level will not work as many of our customers have multiple sites, multiple projects and multiple service work orders etc. There is NO WAY to tell which opportunity is connected to which projects unless you go into the notes and click around to see what is connected.

Right now if you have to create an invoice for anything outside of the contract, you have to go to financials + Invoice. It would be nice to have it added to the workflow for visibility in the field and office by +WORK and +Invoice. If you don't know an invoice exists, you're not going to go looking for it in financials.

In Company Settings>Portal>Work Orders, we need the ability to make the customer notifications only occur for certain Work Orders, instead of all Work Orders. We want to leverage the calendar feature so field personnel can see things like permit pick ups and material deliveries on their calendar, without bombarding the client with out-of-context notifications. We ONLY want to notify the client of their actual Solar Installation work order(s).

We receive one payment for 6-10 invoices at a time. I spend a lot of time copying a pasting the reference number and the description of customers included in the invoice.

we need the ability to include job titles alongside usernames, so titles are visible wherever users are displayed across Coperniq. We want to leverage this to help our team quickly identify the right person to assign, tag, or follow up with based on their role — especially in a growing organization where multiple users share similar names or work across departments. Today, seeing only the name forces us to look up each person's role separately, which slows down assignments and increases the chance of routing work to the wrong person. We would like the title to display alongside the name (for example, "Jane Doe — Project Manager") in every place a user appears in the platform. Ideally, this would pull from an existing "Title" field on the user profile, so it stays in sync automatically as roles change.

I would like to be able to leave comments and tag users on documents/files via API call similar to commenting on a project or work order.

So we can track week over week, and month over month sales. Would also like to be able show by rep or segment (commercial vs residential vs special projects etc)

Please add a paginated endpoint for retrieving Forms across all Projects, with support for filtering by the Form’s last update time. An ideal endpoint would look similar to: GET /v1/forms?page=1&page_size=100&updated_after=2026-08-01T00:00:00Z Useful response fields and filters would include: Form ID Project ID Work Order ID, when applicable Template ID Status Archived state Created timestamp Reliable updated timestamp Pagination updated_after and updated_before Optional Project, Work Order, template, and status filters If a global Forms endpoint is not feasible, an include_form_updates=true option on the Projects endpoint would provide a useful alternative. It should cause a Project to be returned when any attached Form is created, updated, completed, or archived, including changes to Form field values.

In the filter we are missing a custom date range. Between customer dates filtering. I want to be able to view several weeks ahead but isolate in chunk of 7 days. For example I would like to see the installs scheduled on the week of 9/7 through 9/11

When a file is uploaded to a Project Property field, and is removed from the field, it completely deletes that file. This is a problem because if we have a Contract field and we want to upload a new one, we need to remove the old one so its clear what the current active contract is. Ideally, when creating a File Upload field, we would have an option to choose how to handle files removed from that field. Just remove the tag but keep the file uploaded like any other file, archive the file, or delete the file. However, even just Archiving the file by default instead of deleting it, would be in-line with Coperniq's current methodology for deleting things, and would be an improvement for our use case. Nowhere else in the system can you skip right to Deleting something without Archiving it first.