Skip to content

SmartSimple Idea Lab

SmartSimple Idea Lab

Categories

JUMP TO ANOTHER FORUM

(thinking…)

How can we improve SmartSimple? Search and Submit your ideas below.

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

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

5 results found

  1. Role names in report

    We would like to review on a regular basis (1 or 2 times per year) that all users having a privileged account in the system still need such access. We would like therefore to generate a report listing all users with their current role. Unfortunately, only "Role ID" can be added to report. Not "Role Name" or "Role Caption"

    11 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    Under Consideration  ·  0 comments  ·  Security and Compliance  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  2. User Emulation - Add granular role-based privileges

    At present, the settings for user emulation do not allow for granular role-based permissions. For example, there is no feature to restrict which other roles a user role can emulate. It would be incredibly useful for our staff to be able to emulate grantee user accounts. Unfortunately, we currently cannot enable this feature for them, as it allows them to emulate all other roles which includes higher-level users.

    Something like "Roles this role can EMULATE" (reference attached image) would be incredibly useful.

    3 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    2 comments  ·  Security and Compliance  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  3. Replacement of Google reCAPTCHA with a more privacy-friendly alternative

    At the moment SmartSimple does use Google reCAPTCHA v2 or v3 as a security measure on the system. The use of Google reCAPCTHA however raises privacy issues since Google uses the data (IP adresses, Browser and device, user info, cookies) for own purposes. Google collects more data than is neccessary for the functioning of the reCAPTCHA. The use of Google reCPATCHA v3 raises even more privacy issues since in v3 Google continously analyses online behaviour and users are not aware anymore that their online behaviour is analyzed.

    We would like to have a more privacy friendly reCAPTCHA on the system,…

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    Proposed Idea  ·  0 comments  ·  Security and Compliance  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  4. Default file size size limit

    I suggest that default limit when you add a new upload field should be set to 10mb.
    It can always be increased if necessary.

    3 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    Feedback Needed  ·  0 comments  ·  Security and Compliance  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  5. Support for SCIM 2.0 for user provisioning and de-provisioning

    We would like to propose that SmartSimple develops support for SCIM 2.0 (System for Cross-domain Identity Management).

    We're moving towards automated provisioning and de-provisioning of users directly from Microsoft Entra ID (Azure AD). SCIM 2.0 is the industry standard protocol for this purpose, and is already supported by Entra ID as well as most modern identity and access management systems.

    Efficiency: Automating user lifecycle management reduces manual administrative tasks and minimizes delays in onboarding and offboarding users.

    Security: Automatic de-provisioning ensures timely removal of access when people leave the organisation, reducing the risk of orphaned accounts and potential breaches.

    Compliance:…

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    Monitoring Interest  ·  0 comments  ·  Security and Compliance  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
  • Don't see your idea?