This collection of how-to guides is built for Apricot users who want to get things done: faster and with fewer headaches. Whether you’re designing forms, setting up rules and alerts, or managing participant data, you’ll find clear, step-by-step instructions from the Treadwell team to support your work.
Note: Explore the template library for a starting point for your forms
Adding a Field
Removing a Field
Why it matters?
Forms are the backbone of your data collection in Apricot. Being able to add or remove fields ensures that your forms remain aligned with evolving program needs, funder requirements, or reporting goals. Clean and well-structured forms lead to more accurate data and efficient workflows.
Your Apricot database has a limited number of user seats available. These users are split up into “Standard” and “Administrator” seats. Some sites may have “Guest” as an option (an add-on feature).
Administrators can make changes and updates to specific users by clicking on their User Card located on the Users Page. Navigate to this page by selecting the “Administrator” tab, expanding “Access Control” from the left-hand menu, then clicking on “Users”.
Tip: A record can also be added or removed from the record itself too by expanding the “Favorites” from the right-hand side menu, then(un)checking the list(s) you want to add to or remove the record from. Don’t forget to click on “Set Favorites”, otherwise it won’t work!
Rules & Alerts in Apricot allow you to automatically notify users when certain conditions are met, helping you stay on top of critical updates, compliance, or workflow triggers.
Rule Details
Trigger
Action
Why it matters?
Rules & Alerts in Apricot help you stay ahead of the action by triggering instant notifications when key conditions are met, whether it’s a new referral, a compliance risk, or an overdue task. Automate your follow-ups, flag exceptions in real time, and make sure the right people see what matters most.
When searching a name in Apricot, you should utilize the wildcard function: % in front of your search.
Why this is important: In Apricot, while the duplicate check function is helpful, it does not find duplicates when there are small differences between records (ex. The name is spelled slightly differently, the DOB is off by a day or year, etc.), so strong search practices help to reduce the duplicates that will have to be merged or archived later on.)
Tips:
Tip: When to use
Lookup List can save you time when:
Every record for every form created in Apricot has an identifying number, which is called a Record ID. It is a built-in unique identifier generated by the system and can be used to distinguish clients without revealing personally identifiable information. This field, as with all System Fields, cannot be edited or imported into. To find the Record ID, use any of the methods below:
Copying a Tier 2 record is similar to copying a Tier 1 record. If copied from the record itself, the new Tier 2 copies will always be placed under the same Tier 1 record. If copied from the document folder, the record can be copied from the current Tier 1 to one or more other chosen Tier 1s. (For example, copy Sally Jones’ case note to add to both Bill and Bobby Jones.)
Note: Emojis will show in native reports, can be filtered, and will export into Excel as emojis. If you need them to appear in Results reports – we can help!
The Auto Populate field is a type of linking field in Apricot that allows you to automatically pull data from one record and display it on another related record. This is recommended when you need to create a calculation on one form using data from another form or physically display data from one form on another related form.
Note: it’s important to use Auto Populate sparingly, as it can lead to data redundancy in your database. Reach out to us if you have questions whether this feature is recommended for your use case.
To successfully publish a form in Apricot, make sure your form includes at least one:
Tip: If your Publish button is still grayed out, double-check that:
Why it matters?
Before you can publish a new or updated form in Apricot, you need to meet certain system requirements, otherwise, the Publish button stays grayed out. These checks ensure that every form you release is functional, searchable, and ready for reporting. Knowing what to look for saves you time and frustration during the form-building process.
A restricted report is a pre-built Apricot report that cannot be edited. These reports are view-only and cannot be modified, renamed, or restructured by admins. They’re built using Apricot’s stock forms and are designed to provide a standard reporting baseline that many organizations find useful, or are used to meet federal or state reporting requirements.
Note: The original locked report will remain unchanged. You can hide it from end users by editing permissions or hiding the category if needed.
Why it matters
Restricted reports give you a ready-made starting point. While you can’t change the originals, copying lets you adapt those reports for your own organization’s needs, e.g. adding filters, customizing fields, or tailoring visuals, without losing the baseline report.
Exporting data from Apricot is quick and lets you take your reports into a familiar format for sharing or further analysis. Whether you’re preparing numbers for a funder, a board presentation, or just need to slice the data differently, Excel exports give you flexibility without changing anything in Apricot.
Tip: What you see in Apricot is what gets exported, so double-check your filters before exporting to make sure your file includes the right data.
Why it matters
Sometimes you need to share Apricot data outside the system, e.g. for a funder report, a board meeting, or deeper analysis in Excel. Exporting your data ensures you can work with it in a familiar format, while keeping your original Apricot records intact.
Instead of configuring permissions for each user individually, create a Role that defines what users can view, create, edit, or delete. You can then assign the same Role to multiple users, making permission management faster and more consistent.
Tip: Create roles based on job responsibilities (e.g. Case Manager, Supervisor, Reporting Analyst) rather than individual users. This makes permission management much easier as your team grows.
Why it matters
Well-designed Roles simplify user management, strengthen data security, and reduce administrative work. As your team grows, Roles make it easy to maintain consistent permissions without configuring each user individually.