Skip to content

Settings and activity

4 results found

  1. 28 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)
    Planned  ·  Danielle Robadey responded

    Thank you for your feedback. We are in the planning phase of a feature or update related to this item.

    Joshua Kramer-Jensen supported this idea  · 
  2. 9 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)
    Joshua Kramer-Jensen supported this idea  · 
  3. 53 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)
    An error occurred while saving the comment
    Joshua Kramer-Jensen commented  · 

    To expand on this, currently, client privacy is tied to the Agency which created the client. Private clients can only be associated with one agency, and clients with data from multiple agencies cannot be changed to private. Clients with data in multiple agencies must be duplicated, which breaks cross-agency reports, as the duplicated client will show up as multiple individuals.

    These issues could be resolved by a Client Privacy Setting that restricts access to a client record based on the agencies it is currently associated with.

    For example, a client is enrolled with AgencyA and AgencyB, then revokes sharing permission. Enabling the proposed privacy setting for the client would cause them to be visible only to these agencies. If the client were then enrolled with AgencyC, a new client record would need to be created, as the original is not visible to AgencyC. This record could then be merged with the original, private client by an Admin, and would then only be visible to AgencyA/AgencyB/AgencyC.

    Joshua Kramer-Jensen supported this idea  · 
  4. 25 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)
    Joshua Kramer-Jensen supported this idea  ·