Skip to content

SmartSimple Idea Lab

SmartSimple Idea Lab

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

216 results found

  1. Prior to promoting changes in the Target environment, we see a comparison log that is similar to what we see in the desktop T2P tool. However, it was not clear that all the changes were represented in the Export package. The comparison log could also include additional information that could make it more useful like Date Changed, Time Changed, User, etc. Additionally, there is no way to export or save the comparison log, and after promoting changes, it is no longer accessible.

    After promoting changes to the target environment, we can see the Import Log, which in some cases, will…

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. The current functionality within listviews allows the user, if the option is enabled, to request the download of the files in a specific Upload - Multiple file storage field to a ZIP file.

    This functionality is not currently available for the field type Upload - Image. We would like to have this option available, as the current workaround requires the configuration of 2 API services and short script to get the same result.

    10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. It is possible to batch update for status, institutions, associated contacts (etc), but it is not possible to do it on Notes.

    Is there something I am overlooking? :)

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. We currently configure SMTP relays for clients who wish to send email from their own domains.

    However, it is often challenging to work with client IT teams to enable SMTP AUTH on the required mailboxes.

    In these situations, we are frequently asked whether SmartSimple supports — or plans to support — integration with Microsoft 365 (Graph API) or Gmail API for outbound mail delivery.

    We understand that the February upgrade strengthened security by enforcing OAuth 2.0 for SMTP authentication. However, this still relies on SMTP as the transport protocol, which many IT providers increasingly consider legacy compared to modern API-based…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. SmartSimple should allow to enable other user roles to delete from the Message Queue without making them Global Administrators. This way other users will be able to delete emails that they accidentally triggered so that they won't be mistakenly sent out.

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Sys admins can search across workflows and tasks, but we can't search against / see connector IDs.

    Project based T2P lets you see the workflow IDs that have been updated, but there's no traceability to the connector ID when looking at a connector in wf.

    At a minimum, I'd like to see the connector ID on the connector itself. Even better if I can search against a connector list to see what was updated

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. I've recently seen great improvements to the grantee user experience when I've utilized the Linked Record List Custom Field "Simplified Association Interface" toggle for Contact Associations, but this option is not currently available for Organization Associations as well as some other list types.

    Please consider adding the "Simplified Association Interface" option for Organization Association list types, as well as all other list types, if possible.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Please allow Batch Update to handle removal of Assigned Contacts based on role. The way it functions now, a name is required in order for Assigned Contacts to be removed. Doing a bulk removal via batch update based on role alone does not seem to work.

    18 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Enable users to link directly to a report when it has been created. This would be incredibly helpful when working collaboratively. Currently we have to describe which folder the report is in and provide a unique ID so they know which report to access. It would be so much easier to send a direct link to the report.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. https://wiki.smartsimple.com/wiki/HistoryOf_function

    When using this function, I have to configure with status names. Example from WIKI:

    @HistoryOf(Status::[Value]='Approved'::Update to [Value] by [UpdatedBy] at [UpdatedTime]::[UpdateTime]::desc::1)@

    This is a brittle approach (as this is the caption / front end field name). I'd love the ability to pass the statusid as opposed to status. Even backend field (name) would be better than the caption

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. All our emails are sent from "no-reply@smartsimple.eu"
    However, even if this is a "no-reply" email address and we describe in the email body the one to use to reply, users continue to use the "reply" button of their email client. So, we would like to define, at the email template level, the reply email address to use (can't be a global parameter as multiple internal teams are involved).
    For now, we try to use the "(reply-to)" feature in cc (see screenshot - do not remove it!) but this is not very practical

    15 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Communicate known issues and their statuses/schedules so clients can review as opposed to creating help desk tickets that may already exist

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. "Highlights" are exactly what they sound like - background color added to specific selected text.

    1. Permission L1 and L2 form types to accept highlights - application types, report types, etc.

    2. Permission highlighter function for various roles (staff, reviewer, evaluator, etc.) - Permissions should include "Create/view highlight" (user can create and see their own highlights), "View all role highlights" (enable reviewers to see each others' highlights IF this function is invoked on the highlight control menu), "View all highlights" (enable users with this role to see all highlights when invoked on the highlight control menu), and "Highlight PDF" (enable use of…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. When we need to update the custom field permissions, the Permission Quick Edit is often unusable. Once you scroll down a small amount, you lose the header row and can't tell what role or status you're changing. Same for when you scroll to the right, you lose the Custom Field column on the far left and have no idea what field you're editing.

    We also usually don't really know the field's name as well as we know the Caption. It would be so helpful to include both the name and caption for reference so you know you're really updating the…

    14 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Why have "email" as an interaction type if you can't actually create, select, store or reference the email within the user interface?

    Use case: Our Finance staff wants to initiate an email conversation about unspent grant funds with an organization. The easy way would be to create an Interaction, use the "Email" type, and have it open an email template they could add subject line, body, and attachment(s) to, then select the "To" options from the "Contacts" specified in the Interaction. When a contact replied to the email, the email should show up in the owner's regular email client but…

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. In the old version, our grant ID numbers would stay at the top of the screen as we scrolled down activity forms. Now they do not. I'd like this one feature to go back to the way it was. In the new look grant ID numbers should stay at the top of the screen as we scroll down the page.

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. The current permissions tab for creating a new folder within a system folder is limited to View Folder and Modify Folder permissions.

    Add the "Upload and Move Files" and "Create Sub-Folder" sections under the Role Permissions settings as well.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Introduce a visual indicator, similar to a stoplight system, to represent the risk level associated with records such as grants or other engagements. This would allow users to quickly assess the likelihood of success by viewing the associated risk level at a glance:

    • Green – Low Risk
    • Yellow – Medium Risk
    • Red – High Risk
    • Grey – No Value/Not Assessed

    Key Features:

    • Display Locations: The indicator should be visible on the individual record, within list views, and be accessible for reporting purposes.

    • Data Representation: In addition to the color-coded indicator, the corresponding textual value (High, Medium, Low, or None) must…

    18 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Currently to have any sort of verification process on org profiles and contact profiles being up to date one has to use statuses and workflows to push them back and forth and this is the best practice for verifying these are up to date when submitting an application.

    Many clients request the ability to check whether these have been updated recently by the applicant as part of the application submission process. It would be nice if there was a way to enforce that applicants confirm their org/contact profiles are up to date without having to configure statuses. Similarly with the…

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Problem: Logs related to configuration and system behavior are currently fragmented across multiple locations, making troubleshooting slow and inefficient. There is no clear centralized view or consistent process to identify high-impact issues, and important configuration errors are often buried as generic warnings.

    Key Gaps:
    No single, centralized location for all relevant logs
    Configuration-related errors are hard to discover and correlate
    Log severity levels are not granular enough, causing critical issues to appear as low-priority warnings
    Lack of guidance on whether customers should rely on platform logging or develop internal processes

    Requested Improvements
    Centralized Log Access
    Provide a single, unified location…

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?