3 results found

1. Clearer Separation Between Users and Contacts in CRM

   To simplify and future-proof our CRM, we propose a clearer distinction between users and contacts:

   Distinct Types

   Users: Authenticated accounts with login privileges.

   Contacts: Business records tracked in the CRM system, without login privileges.

   This separation ensures that external contacts are never mistaken for system users.

   Permissions

   Only admins can create or manage users.

   Regular staff can add and edit external contacts, but not users.

   This approach safeguards system integrity while allowing staff to work freely with contact data.

   Notifications

   By default, contacts do not receive system notifications, unless explicitly set up for GDPR purposes.

   Context for Our Use

   We use the CRM differently from many other organizations:

   Our team does not administer grants; we apply for funding.

   The system is used to manage our portfolio of projects and coordinate our fundraising efforts.

   Without this separation, the CRM functionality would become unusable for organizations like ours.

   Outcome

   This upgrade reduces complexity by firewalling users from contacts.

   Staff can interact with contacts efficiently, while sensitive user management remains restricted to admins.

   Overall, this ensures both security and operational flexibility in our CRM workflows.

   To simplify and future-proof our CRM, we propose a clearer distinction between users and contacts:

   Distinct Types

   Users: Authenticated accounts with login privileges.

   Contacts: Business records tracked in the CRM system, without login privileges.

   This separation ensures that external contacts are never mistaken for system users.

   Permissions

   Only admins can create or manage users.

   Regular staff can add and edit external contacts, but not users.

   This approach safeguards system integrity while allowing staff to work freely with contact data.

   Notifications

   By default, contacts do not receive system notifications, unless explicitly set up for GDPR purposes.

   Context for Our Use

   We… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Other  ·  Delete…  ·  Admin →
   Product Education  ·  AdminJohn Fulton (Director of Product Management, SmartSimple, Foundant Technologies) responded

   Thanks for the suggestion, most likely, this is something that can be done via configuration, we will be reaching out to you to discuss.

2. email alerts for admins when autoloader fails

   We'd like to be able to receive an alert when an autoloader fails. Currently, system admins cannot receive these, yet SmartSimple does. We have many autoloaders that run hourly and when they hang, it creates a big problem to clean up so if we could be alerted soonest, that would help greatly. We've asked if this is possible and currently it is not. We'd like to see this added to an upcoming release.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Other  ·  Delete…  ·  Admin →
   Product Education  ·  AdminJohn Fulton (Director of Product Management, SmartSimple, Foundant Technologies) responded

   There are notification settings on the process tab in the autoloader to specify the recipient(s) of failures, see screenshot.

3. Group-Based Permissions for Custom Fields

   Description:
   Introduce the ability to assign custom field permissions based on predefined groups, rather than manually configuring permissions for each individual role or status. This would streamline permission management and reduce redundancy in configuration.

   Example:
   Instead of selecting 10 statuses in "Allow View Field" for each custom field, create a predefined group called "Youth Program EOI" to include these 10 statuses, and this group could be used to apply permissions for all statuses related to "Youth Program EOI" in one step.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Product Education  ·  0 comments  ·  Other  ·  Delete…  ·  Admin →