Search Results

Summary ChilliDB has Quote functionality offered that a user can generate against their clients with all the products or services they provide. This can be accessed via Quote Module under System Menu. We can Create, View, Edit, Save, Send/E-mail, Expire, Approve, Decline, Print or Create Like Quote. Create We can Create Quote by following simple steps. To create Quote, We should first Go to Quote Module by clicking on Quote Module from the list of System Menu. Once we are in Quote Module, We can Create new Quote simply by clicking Create Link on the top right hand side of the page. On Quote Create Page we can fill all the information related to that Quote like Client Detail, Date of creation, Expiry Date, Reference, Choose Product/Service for that Quote, Notes, and so on. System will generate Quote Number automatically after any Quote is saved and Status is changed automatically based on status of that Quote i.e. Draft, Accepted or Declined. Setting a Default Expiry Date for Quote We can set a default expiry date for a Quote via System Settings which can be accessed via System –> System Management –> Manage System Configuration –> Quote Default Expiry Days. Sending Quote After all the fields are filled in properly, we can Send Quote to our Client and Client will receive both pdf version attached and a link to View, Accept or Decline Quote via their Email. While Sending Quotes, we can choose from list of contact and their email addresses, write Subject and Body, choose classification before sending just like sending Email and Click Send. We can either use template for Sending Quote or Compose our own, in Either case we should make sure that Quote Link token is attached within the mail before sending. It can be selected from the list available on Mail merge tokens. Accepting Quote After Quote is Sent to the Client, they will receive both pdf version attached and a link to View, Accept or Decline Quote via their Email. Now, Quote can be viewed by clicking/visiting the link on Email. All the fields will be populated with respect to Quote Create step. User can either Accept or Decline received Quote by clicking on Accept or Decline button respectively. Approving Quote User can Approve received Quote by clicking Approve and will be directed to Quote Approve Page. From here user can fill in details like Purchase Order Number, upload Purchase Order file, and write Comments if any. Which will be sent back to ChilliDB and will be reflected under Quote Grid Columns on Quote page. After filling up all the fields, User can Approve Quote by clicking Accept. Declining a Quote User also can Decline a quote received by clicking Decline. This will also be reflected back on Quote Page on ChilliDB. This can be done by clicking Decline on top right corner of Quote Display Page. After User clicks Decline, they are directed to Decline Quote Page where they can write Comment on Comments field for the action if they want to and after clicking Decline, the Quote will be declined. After User Accepts or Declines Quote, the action will be reflected while visiting link for quote received via Email. Accepted Quote will be displayed as: 1. On Quote Display Page (Link): 2. On Quote List: Declined Quote will be displayed as: 1. On Quote Display Page (Link): 2. On Quote List: Quote Display Page Action Menu: From Quote Display Page – Action Menu, we can choose to Mark any quote as Approved, Decline, Print or Create Like by selecting Mark as Approved, Mark as Declined, Print or Create Like respectively. Mark as Approved By selecting this, we can manually Approve any Quote that we create. After clicking on Mark as Approved, a new page will popup where we can fill in details like Purchase Order Number, Upload Purchase Order, and write Comments if any like any user would do while approving received Quote. Quote is approved after Approve button is clicked or we can cancel this by clicking Cancel button. Remember only Quote that has its Status – Draft Can be Accepted Manually. If Quote is already Accepted or Declined by user, this Menu is no longer available. Mark as Declined By selecting this, we can manually Decline any Quote that we create. Only After clicking on Mark as Declined, a new page will popup where we can write Comments if any like any user would do while declining received Quote. Quote is declined after Decline button is clicked or we can cancel this by clicking Cancel button. Remember only Quote that has its Status – Draft Can be Declined Manually. If Quote is already Accepted or Declined by user, this Menu is no longer available. Print By Selecting this, we can Print the Quote. After we click on Print, a reporting view of the Quote is displayed on new screen. From where you can View Quote, Print, Save a file on different formats, and/or Email file. Create like We can Create another Quote that is same as the one we are viewing by selecting Create Like menu. Another popup page will appear with Reference and Notes field being empty for us to enter new details. We can add new products or services by clicking Add new Line, Save, Send or Cancel the Action. These function same as in creating a new Quote. Any Quote that is of Draft, Accepted or Declined Status has Create Like menu available. Declined Quote has this function on bottom right corner on Quote Display Page. This Button also functions as same.

Summary ChilliDB has Invoice functionality offered that a user can use to generate an invoice against their clients for any of their products or services. This can be accessed via the Invoice Module under System Menu. Here, users can Create, View, Edit, Save, Send/E-mail, Void, Approve, Expire, Print or Create like Invoice. Create Users can Create an Invoice by following a few simple steps. To create an invoice, first go to the Invoice Module by clicking on it in the System Menu. Once in the Invoice Module, users can create an invoice simply by clicking the 'Create' link on the top right-hand side of the page. On the Invoice Create Page users can fill in the relevant information related to the Invoice they are creating, like Client Detail, Date of creation, Due Date, Reference, and Choose Product/Service. The system will generate an Invoice Number automatically after an invoice is saved and the Invoice Status is changed automatically based on status of that particular invoice, i.e. Draft, Authorised or Declined. Sending an Invoice When sending an invoice, users choose recipients from their contacts, write a Subject and Body, and choose a classification before sending it. After all fields are filled in properly, users can Send an invoice to a client. Users can either use a template to send an invoice or compose their own. In either case, they should make sure that an Invoice Link Token is attached within the email before sending it. This can be selected from the list available in Mail merge tokens. After an invoice is sent to a client, they will receive both a pdf version and a link to view the invoice via their email. The recipient can view the invoice by clicking/visiting the link attached to their email. All the fields will be populated with respect to the information entered in the Invoice Create step. Invoice Display Page Action Menu: From Invoice Display Page – Action Menu, users can choose to Expire, Authorise, Void, Print and Create Like invoices by selecting Void, Print or Create Like respectively. Expire Users can expire newly generated invoices that are still of Draft Status if they wish to. After an invoice is expired, this will be reflected in its status. Authorise User can manually Authorise an invoice generated by clicking Authorise from the Action Menu. After Authorise is clicked, the user is directed to a page where they can write a comment, if necessary, and click 'Authorise' to manually Authorise a draft invoice. Void By selecting this, users can manually Void an invoice which they created. Print By selecting this, users can print the invoice they received. After they click on Print, a reporting view of the Invoice is displayed on a new screen, from where they can View the quote, Print it, Save it as a file in different formats, and/or Email the file. Create like Another option available in the Invoice Module is to create another invoice that is a copy of one that already exists by selecting Create Like menu while viewing the invoice you wish to duplicate. Another popup page will appear with the Reference field being empty, allowing users to enter new details. They can add new products or services by clicking Add new Line, as well as Save, Send or Cancel the action. This functions in the same way as when creating a new invoice.

To adjust the amount of users who can access your system, you must add or reduce your ChilliDB licenses. There are two types of licenses: Concurrent licenses where each user has their own ChilliDB login, however they use a license from the pool of licenses (in other words, they are shared). With each login, a license is taken from the pool. This model supports peaks and troughs in system usage where you may have lots of users at different times of the day and not all users using the system at the same time. Named licenses where each user has their own ChilliDB login and license and only they can use that license. This model supports clients who need to have access to ChilliDB at any time and do not want to miss out on being able to login due to there being no free licenses which would be the case if they had concurrent licenses When your system runs our of available licenses, the following screen will start appearing to your users when they try to login to ChilliDB: Your licenses are adjusted from the licensing details page. This is accessed from the 'Display Licensing Details' link on the system management page. On the licensing details page, select the ‘add more licences’ or ‘reduce my licences’ links to adjust the amount of licenses for your system. The license changes take effect immediately. Please note that if named licenses are allocated to a user they can’t get deleted so they need to be reassigned. Billing When increasing licenses, an adjustment bill is sent straight away for that billing cycle, for decreases in licenses you will be charged less in the next bill. To avoid confusion with adjustment bills, only one change can be made per billing cycle. If you have made a mistake please log your license change request in the helpdesk.

The role access is controlled by the sensitivity settings, which are bulk updated by going to the "Contact Categorisation" and "Note Categorisation" reference data tables. From there you can right click on a note type and click maintain. For all notes/contacts of the selected type you can allow all roles to view, or click create to specify which roles should be able to view the data of that type. These settings can be updated at any time.

Note Locking is where Notes created in ChilliDB can be locked from modification after a period of time. This is done to protect the content of Notes from changes. ChilliDB holds a configuration setting to capture the number of days after which a Note should be locked. A Note will be locked based on the calculation of Note Creation Date + [The Configured Number of Days]. Locked Notes can only be edited once they are locked by users who have the Security Ticket NOTE MANAGER in their User Role. By default this setting is turned off in most systems. You can request to have this feature turned on in your system through lodging a request in ChilliDB HelpDesk. You just need to state how many days you would like the Notes to remain editable for, e.g. 1 day

The Note Search rolls up information to the Note level by default. This means that if a Note is created against more than one Organisation, the search results will show "..." under the 'Organisation Name' column. Likewise, if the Note was created against more than one Contact, then the "Contact Full Name" column will also show "...". Users also have the option of choosing 'Show one row per Note' and 'Show one row per Contact/Organisation Association' from the 'Result Behaviour' menu in the top left-hand corner of the Notes Advanced Search page. Selecting the second option will return all Note - Contact - Organisation associations, so you will see all Notes and each Contact / Organisation it is linked to.

The Sensitivity feature allows the user to restrict access to certain information within the ChilliDB system based on Types (Categories) or according to custom-selected User Roles. At the moment, this feature can be applied to Contacts, Notes, and Membership Packages. This article covers different levels of sensitivity, how the various areas of ChilliDB are affected by sensitivity settings, and managing sensitivity. Table of Contents Levels of Sensitivity Finding Information if the Record is Sensitive Reporting Views Web Service Outlook Plug-in Managing Sensitivity Settings Bypassing Sensitivity Settings Frequently Asked Questions Levels of Sensitivity The ChilliDB system currently offers three levels of sensitivity: 1. No sensitivity – the record can be viewed or modified by any logged-in user as long as that user has the security ticket to view or modify the record. 2. Sensitivity based on Type – the record can only be viewed or modified by those User Roles defined at the Type level. At this level, the Type will contain selected User Roles that can access (view or modify) the record associated with the type. This is managed through the Reference Data - Create and Maintain screen when creating or editing the Categorisation. Where a record has no sensitivity settings applied and then those settings have changed for the Type, the record will automatically apply the Sensitivity based on the Type. This is because the Sensitivity based on Type will override the “No sensitivity” condition. 3. Sensitivity based on selected User Roles – the record can only be viewed or modified by the User Roles defined to access that specific record. Even though some User Roles contain the security ticket to view or modify the record, they won’t be able to access the record if the User Roles are not included in the allowed User Role list for that specific record. This is managed through the Manage Sensitivity screen, which is accessible when viewing the record via the Quick Action called “Manage Sensitivity” or when creating or editing a record via a link in the Sensitivity field. This will only appear if the User has the security ticket “Sensitivity Modify”. This ticket can be granted via 'System - Users - Maintain roles and Tickets', choosing the appropriate role from those available, searching for 'Sensitivity', and then selecting the appropriate ticket(s). Sensitivity based on selected User Roles will override sensitivity rules based on Type. The user can also enable all User Roles to access the record. This will ensure the record will stay accessible to all User Roles even though the Sensitivity settings for the record Type have changed. Finding Information if the Record is Sensitive When the records have Sensitivity settings applied, a user whose User Role does not have access via the Sensitivity tickets experiences the following conditions: View/Modify Records The user is not able to access the record display page. The page indicates that the record is sensitive and redirects the user back to the home page. Some of the links in the system, such as in the Search pages, show the Sensitive records in a different colour. The default colour is orange; however the user can customise this colour setting at the system level. The links are also disabled from clicking and a tooltip is displayed to notify the user that sensitivity rules apply to the record. The address details, phone, fax, email, and other details, such as gender, date of birth, job title and department, which are specific to the Contact record, are hidden from the export and print list when doing Export All or Print All from the search results grid. Sensitive Contacts are not included in the Bulk Update for Contacts. When selecting the sensitive Contacts to be included in the Bulk Update, a warning message is shown to notify that the sensitive Contacts will not be included in the Bulk Update process. Send Message Custom fields and the Contact communication details for phone, fax, and email are hidden when refining the Contact recipients of the message upon performing the “Send Message” Quick Action from some screens like Contact Search, Contact tab in Organisation Display screen, Distribution List Display screen, and Membership Display screen. When viewing notes from screens such as Contact note listings and Note searches, all custom fields and the details field are hidden Within the Refine Message Recipient screen, the sensitive Contact name is shown in a specific colour. The default colour is orange; however the user can customise this colour setting at the system level. Since the communication details are hidden, the sensitive Contact shows the “Not Available” message in the Communication Address area. The Refine Message Recipient screen also shows the warning message to indicate how many sensitive Contacts are shown in the recipient list and notify the user that those sensitive Contacts will not be included when sending the message. Furthermore, these sensitive Contacts are not included in the Send Message screen. The sensitive Contacts do not appear on the search result when the user tries to search for the message recipient from the Find Recipient popup screen (accessible from the Send Message screen by clicking Find link). When sending a message to a Distribution List, any sensitive Contacts contained in the Distribution List are not included as the message recipients. A notification message appears on the Send Message screen to notify that the sensitive Contacts contained in the Distribution List will not be included in the message. Distribution List The Contact communication details for phone, fax, and email are hidden when they are displayed in the Members or Unsubscribed Members tabs within the Distribution List Display screen. The Contact communication details for phone, fax, and email are hidden when assigning the Contact’s communication item to the Distribution List upon performing the “Subscribe to Distribution List” Quick Action from some screens like Contact Search and Contact tab in Organisation Display screen. The communication items are still shown in the Communication address area however the details of those communication items are marked as “** HIDDEN **”. Within the Subscribe to Distribution List screen, the sensitive Contact name is shown in a specific colour. The default colour is orange; however the user can customise this colour setting at the system level. The Subscribe to Distribution List screen also shows a warning message to indicate how many sensitive Contacts are shown in the subscriber list. Event The phone, fax, and email of the sensitive Contact are hidden from the Event Attendee list screen which is accessed from selecting the “Show/Export Full Attendee List” Quick Action item or by clicking the “Show List” link on the Session tab under “Registrations/Attendance count” column within the Event Display screen. The phone, fax, and email as well as the address details of the sensitive Contact are also hidden from the export list and print list when doing Export All or Print All from the Event Attendee list screen above. Membership The Contact communication details for phone, fax, and email will be hidden when assigning the Contact as Member of a Membership package which manages the Distribution List. The communication items will still be shown in the Address field however the details of the communication item will be marked as “**HIDDEN **”. The drop down list which is showing available communication for the Contact is also disabled and the rule for automatic communication subscription into a Distribution List is used in here to automatically select the preferred communication item to be assigned into the Distribution List managed by the Membership Package. As for a user whose User Role is included in the Sensitivity settings, they experience the following conditions: The user is able to view the record. A padlock icon is displayed on the top right corner of the panel next to the Online Help icon to indicate that the record applies sensitivity settings. Bringing the mouse icon over the padlock icon shows a tooltip with information regarding the level of sensitivity applied to the record as well as the User Roles which are allowed to view/modify the record. Clicking the padlock icon shows the Sensitivity Display popup screen showing the same information in the padlock icon tooltip. When a user has the security token/ticket to modify the sensitivity settings, they are able to see the “Manage Sensitivity” Quick Action from the record display screen, or have the Sensitivity field shown as a hyperlink from the record maintenance screen. Clicking on the “Manage Sensitivity” Quick Action or the Sensitivity field hyperlink will enable the user to manage the sensitivity settings of the record. The user is able to modify the record, send a message to the sensitive Contact, export/print the sensitive Contact, or view the communication details of the sensitive Contact as if the sensitivity settings were not applied. Reporting Views The Reporting Views will ignore the sensitivity rules and will only indicate if the record contains sensitivity settings or not by showing the information within the field called “Is Sensitive”. The field returns a value of true or false. Web Service The Web Service will ignore the sensitivity rules at this stage, and will update it in the future to include the flag to indicate the record contains sensitivity settings or not (similar to the “Is Sensitive” field in the reporting views). Outlook Plug-in As the current Outlook plug-in relies on the web service, the plug-in will also ignore the sensitivity rules at this stage. Managing Sensitivity Settings The user will be able to manage the sensitivity settings where their User Role contains the SENSITIVITY MODIFY ticket. The sensitivity setting itself is managed by selecting the “Manage Sensitivity” Quick Action from the record display screen (this is after the record has been created), or else through the Sensitivity field hyperlink from the record maintenance screen (this is when creating a new record or modifying an existing record). As for managing the settings for the Sensitivity based on Type, the user can create or modify the settings from the Reference Data - Create and Maintain screen by creating a new Type or modifying an existing Type. Bypass Sensitivity Settings The user can have a special privilege to treat all sensitivity rules as nothing (bypassing the sensitivity rules) by assigning a special ticket called “SENSITIVITY OVERRIDE” to the User Role. By assigning that ticket to the User Role, the users associated with that User Role are able to view and modify any records in the system regardless of any sensitivity settings applied to the records. Frequently Asked Questions 1. How do I overwrite a record when Type based sensitivity is applied? Answer: You can modify the Sensitivity settings of the Type from the Reference Data - Create and Maintain screen to include additional User Roles. Another way is to assign the “SENSITIVITY OVERRIDE” ticket against your current User Role so you can bypass the sensitivity rules for the sensitive record. 2. What happens if a new Role has been created and I would like to associate this new Role to the Sensitivity settings of a Type? Answer: You can modify the Sensitivity settings of the Type from the Reference Data - Create and Maintain screen to include your current User Role. If your User Role has “SENSITIVITY OVERRIDE” ticket, then you will be able to view the record and then modify the sensitivity settings of that record to set it to be based on user selected User Roles and then include your new Role in the User Roles list. 3. What happens if a Role which is included in the Sensitivity Settings is expired? Answer: You will be asked to assign an existing User Role as a replacement for the expired Role. Any sensitivity settings belonging to the old User Role will not be deleted and will be marked as “[EXPIRED]”. 4. Can I filter sensitive records in my reporting view? Answer: You can filter records based on the information if the record contains sensitivity or not. However, you cannot filter sensitive records that have been designated as such based on specific User Roles. 5. Can the sensitive Contacts be restricted through the Web Service? Answer: The current web service does not allow the user to restrict the sensitive contacts. 6. Can the sensitive Contacts be restricted within the Outlook plug-in? Answer: The current Outlook plug-in does not allow the user to restrict the sensitive contacts. 7. What is the precedence of sensitivity rules? Answer: Below is the order of precedence from the lowest importance to the highest importance within the sensitivity rules: (Lowest) No Security > Restricted based on Type > Restricted based on selected User Roles > Visible to Everyone (Highest) Note: The highest order of precedence can override the lower one. 8. What are the Rules for determining which email address, fax number, or mobile numbers to use for refining the send message recipients? Are they impacted if that Contact is sensitive? Answer: All sensitive Contacts do not receive any messages from restricted users. This means the user is prevented from sending messages to these contacts. The sensitive Contacts shows the communication details as “Not Available” and do not include the sensitive Contacts into the To/Cc/Bcc fields when they are transferred from Refine Message Recipients screen. 9. What are the Rules for determining which email address to use for auto-subscription to Distribution List? Are they impacted if that Contact is sensitive? An All sensitive Contacts mark the communication details like email addresses, fax numbers, and mobile numbers as “** HIDDEN **”. However, the users are still able to allocate specific communication item to be assigned to the Distribution List based on the communication item type. When adding a member into a Membership Package and the membership package maintain distribution lists, the auto-subscription rules for subscribing communication item into Distribution List will apply.

1 Introduction Via an example set of business requirements, this whitepaper provides guidance on how to use the ChilliDB Sensitivity feature within Contacts and Notes. The example also uses an approach for organisation privacy for those Contacts. 2 Business Requirements ChilliDB sensitivity rules must be applied to certain Contact Types. Further sensitivity must be applied on certain Note Types for those same Contacts. Only two groups of staff may access those same Contacts’ details. Only one group of staff may access those same Notes details. 3 Functional Requirements Two User Roles that require access to the Contacts must exist. The appropriate staff must be linked to those User Roles. An appropriate Contact Type must be created. The Contacts must be categorised with that Contact Type. An appropriate Note Type must be created. The relevant Notes must be categorised with that Note Type. 4 Terms used within this Document Valid users: Users who are able to create and update sensitive Contacts and Notes. Invalid users: Users who do not have authority to create and update sensitive Contacts and Notes. 5 Set up 5.1 User Roles: (This is a system administrator task.) Navigate to System > Users> Maintain Roles & Tickets > Add new entry Create the two User roles as appropriate, selecting the tickets as required. In this example we use User Role codes of: ABC is for Alcohol & Drug Counsellors DEF is for Youth Connections Example User Role input: 5.2 Link the staff to the User Roles: (This is a system administrator task.) Navigate to System > Users> Maintain Users Ensure that appropriate Users are linked to their appropriate User roles. Example Username linked to ABC User Role: 5.3 Create an appropriate Contact Type. (This is a system administrator task.) Navigate to System > Reference Data > Create and Maintain > Contact Categorisation Create an appropriate new Contact Type and allocate the ‘Sensitivity Settings’ as follows: Click on Disallow. You now need to add the User Roles that will be able to View & Update this Contact Type. Click on Create The Add Role Access screen will display. Select appropriate tick boxes for the (User) Roles that require access Select View, per following screen: Click Apply Click Save All users will be disallowed to go to Contact Maintenance screen, except those in the ABC user roles for Contact Type of ABCDEF. 5.4 Create an appropriate Note Type. (This is a system administrator task.) Navigate to System > Reference Data > Create and Maintain > Note Categorisation Create .an appropriate new Note Type and allocate the ‘Sensitivity Settings’ as follows: Click on Disallow. You now need to add the User Roles that will be able to View & Update this Note Type. Click on Create The Add Role Access screen will display. Select appropriate tick box for the (User) Role that requires access Select View Click Apply Click Save All users will be disallowed to go to Notes Maintenance screen, except those in the ABC user roles for Note Type of ABC. 6 Day to Day Operation 6.1 Contact creation 6.1.1 Valid users can now create a Contact Type of ABCDEF. 6.1.2 Invalid users will be blocked from creating these Contact Types when Save is clicked. The following message is displayed: 6.1.3 When a valid user creates the Contact the Sensitivity is indicated as Restricted, per following screen: 6.2 Restricted status means: Valid users have full and normal access to these Contact Types. Invalid users: o Are not able to click on the contact to view the full contact record. o The contacts will be displayed as orange (default colour) on the ‘Search Results’ summary list. See following screen example. o The Contact’s name link is not active and therefore clicking on the name will not display the Contact record. Note: Sometimes you might want a descriptive Contact Type and other times you may not. This document uses the example of a generic code for the Contact Type, as opposed to descriptive text is because it is displayed on the Search Results screen. 6.3 Note creation 6.3.1 Valid users can create a Note Type of ABC for that Contact. 6.3.2 Invalid users will be blocked from creating these Notes Types when Save is clicked. The following message is displayed: 6.3.3 Searches Valid users have full and normal access to these Note Types. Invalid users: o Will be able to view the Note summary line on ‘Search Results’ screen but will not able to click on the Note to view the full record. o The Note Title will be displayed as orange (default colour) on the ‘Search Results’ summary list. Notes: The Note Title will be visible to all valid & invalid users on ‘Search Results’ screens. To add further privacy, you could consider using coding on the Note Title 7 Further Topics Regarding Sensitivity7.1 Managing Sensitivity on an existing Contact 7.1.1 Changing a Contact’s sensitivity settings can be achieved via either of two methods, as follows: From Contact Maintenance screen, not in ‘editing’ mode. Select Quick Actions > Manage Sensitivity. From Contact Maintenance screen while in ‘editing’ mode. Click Restricted Both actions above cause the Manage Sensitivity window to display.

Every grid has a list of actions that can be performed by mousing over the arrow button located at the top right of the grid and selecting an option. Common actions are export, print, and shortcuts to functions that are also available elsewhere in the system. In the above example is a contacts search results grid. To perform an action you must select some contacts using the checkboxes on the left side of the grid, then an action from the dropdown. (Note: all records can be selected by clicking the the checkbox in the header row)

Contact Roles allow you to specify information about a Contact at and Organisation at a point in time. The information held in there may be more for a Contact who has a relationship with an Organisation, whether they work at that Organisation or not. The choice of the Organisation in the Contact Role can be any Organisation in the system. So I could for instance see this like: Fred Bloggs is/was on the Board for a specific Organisation which may or may not be the one he works for Fred Bloggs is/was a Fire Warden for my Organisation You can use the Start and End Dates to indicate if the Role is present or ended. You can capture Custom Field information about the Contact Role.

Contacts can be exported from any contact listing such as search results or the Organisation page Contacts tab. To perform an action you must select at least one contact using the checkboxes on the left side of the grid, then an action from the dropdown. (Note: all records can be selected by clicking the the checkbox in the header row) If you want to include custom fields in your export or need to search for specific records, you can use the advanced search which has extra filter and column options. For more information about the grid actions menu and the advanced search, please see these articles Grid Actions Menu Introduction to Advanced Search