Implementing Apricot in a way that reflects your service delivery model will allow Apricot to grow and change alongside your organization as you continue to scale. Apricot is a data collection tool that should be used to collect data about your participants within a program structure. Therefore, your Program structure in Apricot should reflect the data you need to collect about your Programs in practice. Structuring your Apricot programs in this manner will make it easier for you to adopt new functionality, ensuring you are always getting the most out of Apricot.
In this webinar, our Product and Customer Success teams review some of the benefits of program best practices and how to make them a reality for your organization. We invite you to watch the recording below and review some common FAQs further down the page. We’ve also shared some additional resources you can check out for more information.
Apricot is a very flexible data collection tool. However, there are some common setups that limit its flexibility and add complexity to Apricot when changes need to be made. For example, having too few Programs can limit your ability to control and secure data. While having too many Programs or Programs that are mapped to your staff roles instead of your service delivery model can be unwieldy to manage. Our recommendation is to match your Programs in Apricot to your Programs in practice.
Follow these steps to reorganize your Programs in Apricot according to best practices. While this is not a time-intensive process, we do recommend being thoughtful with your changes and making them during a time of less activity in your system, particularly step 3.
STEP 1: Determine Ideal Program Setup—This is the planning stage before you make any changes in Apricot. Review your current settings, roles and/or permission sets. Does your staff currently have access to everything they need in Apricot? Consider the data that is required to tell a story about the programs you offer. Funder and reporting needs should also be considered.
STEP 2: Create New or Rename Current Programs—Depending on how closely your current Programs in practice match your Programs in Apricot, you may need to rename some and add others. If you prefer to start fresh, you can create new Programs and move your data.
STEP 3: Reassign Records to New Programs—Once your new setup is aligned, you will need to update where your records live. This can be done manually or in bulk. This step is ideally accomplished in one sitting, so you know everything has been addressed.
STEP 4: Streamline New Roles—This is the last step in controlling access. If you haven’t migrated to Role Based Permissions, now is the time. Then you can make any adjustments to your user access based on the Programs and services they support.
How will making changes to my Programs impact my existing data?
You will need to check and possibly change the Program assignment for existing data. This can be done in bulk or one at a time. Every record must be assigned one program but can exist in several if applicable.
Do I need to change any settings to control how my future data is assigned to Programs?
Possibly. If you are using the manual Program assignment option for your forms, you can leave as is because this allows you to choose with each new record created. However, if you have chosen either of the automatic assignment options, you may want to review to ensure these still match your needs. Adjust Program Assignment Settings at the form level.
All my staff needs to see all my data. So why should I divide according to Programs?
It is okay to give your staff access to multiple Programs. You can also put data in multiple Programs if that makes sense for your service delivery model. For example, one participant may be enrolled in more than one Program, so their data will be accessible in more than one. The benefits of adding more structure with Programs in Apricot that match your Programs in practice are clarity, control and efficiency in managing and reporting on data.
Can I deactivate Programs I am no longer using?
Yes, but we recommend waiting until after step 3 above to ensure your data is in the new Programs first. You cannot remove a deactivated Program from a record without reactivating it first.
What happens if I deactivate a Program with data still in it?
You will need to reactivate any Program you want to remove before you deactivate again.
How can I use reports to help with this process?
We recommend building a report with Record ID and Assigned Programs from the Systems fields of any given form to see current assignments. Then, you can click into any record that needs to be revised if you want to handle it manually. Use filters to limit your view to just the records with Programs you are updating.
I am not ready to move to Role Based Permissions. Should I still change my Programs?
You will still benefit from the efficiency and control of our best practices. Many of the new features mentioned will require Role Based Permissions. If you have questions or concerns about the migration, please consult your Client Success Manager for direction.
Is Role Based Permissions required for the new functionality?
Yes, you will need to migrate to Role Based Permissions to use Caseloads, Field Level Access and the Referral Network. More information to come on Program Enrollments as we roll out this new feature.
What are my options if I need help making these changes?
If you have an Advanced Support Consultant, we recommend starting there. If not, contact your Account Manager (firstname.lastname@example.org), and they can help you decide if a Professional Services engagement or an upgraded Support package would suit your needs. You can also reach out via Chat or Email (Customer.Care@socialsolutions.com) to our Support team if you have technical questions.
|_biz_flagsA||1 year||A Cloudflare cookie set to record users’ settings as well as for authentication and analytics.|
|_biz_pendingA||1 year||A Cloudflare cookie set to record users’ settings as well as for authentication and analytics.|
|_biz_sid||30 minutes||This cookie is set by Bizible, to store the user's session id.|
|ARRAffinity||session||ARRAffinity cookie is set by Azure app service, and allows the service to choose the right instance established by a user to deliver subsequent requests made by that user.|
|ARRAffinitySameSite||session||This cookie is set by Windows Azure cloud, and is used for load balancing to make sure the visitor page requests are routed to the same server in any browsing session.|
|BIGipServerab09web-nginx-app_https||session||This cookie is associated with a computer network load balancer by the website host to ensure requests are routed to the correct endpoint and required sessions are managed.|
|cookielawinfo-checbox-analytics||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".|
|cookielawinfo-checbox-functional||11 months||The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".|
|cookielawinfo-checbox-others||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.|
|cookielawinfo-checkbox-advertisement||1 year||Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category .|
|cookielawinfo-checkbox-necessary||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".|
|cookielawinfo-checkbox-performance||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".|
|CookieLawInfoConsent||1 year||Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie.|
|__atuvc||1 year 1 month||AddThis sets this cookie to ensure that the updated count is seen when one shares a page and returns to it, before the share count cache is updated.|
|__atuvs||30 minutes||AddThis sets this cookie to ensure that the updated count is seen when one shares a page and returns to it, before the share count cache is updated.|
|__cf_bm||30 minutes||This cookie, set by Cloudflare, is used to support Cloudflare Bot Management.|
|_biz_nA||1 year||This cookie, set by Bizible, is a sequence number that Bizible includes for all requests, for internal diagnostics purposes.|
|_biz_uid||1 year||This cookie is set by Bizible, to store user id on the current domain.|
|bcookie||1 year||LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID.|
|lang||session||LinkedIn sets this cookie to remember a user's language setting.|
|lidc||1 day||LinkedIn sets the lidc cookie to facilitate data center selection.|
|UserMatchHistory||1 month||LinkedIn sets this cookie for LinkedIn Ads ID syncing.|
|_gaexp||2 months 10 days 10 hours||Google Analytics installs this cookie to determine a user's inclusion in an experiment and the expiry of experiments a user has been included in.|
|_uetsid||1 day||Bing Ads sets this cookie to engage with a user that has previously visited the website.|
|_uetvid||1 year 24 days||Bing Ads sets this cookie to engage with a user that has previously visited the website.|
|SRM_B||1 year 24 days||Used by Microsoft Advertising as a unique ID for visitors.|
|_BUID||1 year||This cookie, set by Bizible, is a universal user id to identify the same user across multiple clients’ domains.|
|_ga||2 years||The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.|
|_ga_33YSH1JFFW||2 years||This cookie is installed by Google Analytics.|
|_gcl_au||3 months||Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services.|
|_gd_session||4 hours||This cookie is used for collecting information on users visit to the website. It collects data such as total number of visits, average time spent on the website and the pages loaded.|
|_gd_visitor||2 years||This cookie is used for collecting information on the users visit such as number of visits, average time spent on the website and the pages loaded for displaying targeted ads.|
|_gid||1 day||Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously.|
|_hjAbsoluteSessionInProgress||30 minutes||Hotjar sets this cookie to detect the first pageview session of a user. This is a True/False flag set by the cookie.|
|_hjFirstSeen||30 minutes||Hotjar sets this cookie to identify a new user’s first session. It stores a true/false value, indicating whether it was the first time Hotjar saw this user.|
|_hjIncludedInPageviewSample||2 minutes||Hotjar sets this cookie to know whether a user is included in the data sampling defined by the site's pageview limit.|
|_hjIncludedInSessionSample||2 minutes||Hotjar sets this cookie to know whether a user is included in the data sampling defined by the site's daily session limit.|
|_hjTLDTest||session||To determine the most generic cookie path that has to be used instead of the page hostname, Hotjar sets the _hjTLDTest cookie to store different URL substring alternatives until it fails.|
|at-rand||never||AddThis sets this cookie to track page visits, sources of traffic and share counts.|
|CONSENT||2 years||YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data.|
|undefined||never||Wistia sets this cookie to collect data on visitor interaction with the website's video-content, to make the website's video-content more relevant for the visitor.|
|uvc||1 year 1 month||Set by addthis.com to determine the usage of addthis.com service.|
|_fbp||3 months||This cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website.|
|_mkto_trk||2 years||This cookie, provided by Marketo, has information (such as a unique user ID) that is used to track the user's site usage. The cookies set by Marketo are readable only by Marketo.|
|ANONCHK||10 minutes||The ANONCHK cookie, set by Bing, is used to store a user's session ID and also verify the clicks from ads on the Bing search engine. The cookie helps in reporting and personalization as well.|
|fr||3 months||Facebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin.|
|loc||1 year 1 month||AddThis sets this geolocation cookie to help understand the location of users who share the information.|
|MUID||1 year 24 days||Bing sets this cookie to recognize unique web browsers visiting Microsoft sites. This cookie is used for advertising, site analytics, and other operations.|
|test_cookie||15 minutes||The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies.|
|VISITOR_INFO1_LIVE||5 months 27 days||A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface.|
|YSC||session||YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages.|
|yt-remote-connected-devices||never||YouTube sets this cookie to store the video preferences of the user using embedded YouTube video.|
|yt-remote-device-id||never||YouTube sets this cookie to store the video preferences of the user using embedded YouTube video.|
|_an_uid||7 days||No description available.|
|_clck||1 year||No description|
|_clsk||1 day||No description|
|_dc_gtm_UA-718299-1||1 minute||No description|
|_hjSession_2602456||30 minutes||No description|
|_hjSessionUser_2602456||1 year||No description|
|6suuid||2 years||No description available.|
|AnalyticsSyncHistory||1 month||No description|
|CLID||1 year||No description|
|d-a8e6||1 year||No description available.|
|dpi_test||1 day||No description|
|dpi_utmOrigVals||5 months 27 days||No description|
|intercom-id-rbb6qelf||8 months 26 days 1 hour||No description|
|intercom-session-rbb6qelf||7 days||No description|
|li_gc||5 months 27 days||No description|
|loglevel||never||No description available.|
|referrer||session||No description available.|
|s-9da4||15 minutes||No description available.|
|SM||session||No description available.|
|xtc||1 year 1 month||No description|