Documentation for users and database administrators

Contacts and their contact info: name, addresses, phone & email, demographic details

The Log: interactions with contacts, including payments & pledges, volunteer time, event attendance, and everything else you track in the log

Links: relationships among your contacts

Database administrator features

Adding a new user account

  1. From the Main Menu, click the "Admin" menu.
  2. Click "Users" in the Admin submenu.
  3. Click "Add a new user account"
  4. Provide an account login and password in the dialog box.
  5. An account has now been created. Add the user's full name and edit the privilege level and permissions as necessary. Add a default log code if one is desired. Email features are inactive in the alpha release of ebasePro 2.80.
  6. Click OK to return to the list of user accounts.


Adding email account settings to ebase

[placeholder for documentation on how to set up ebase to check & send email]

Special settings needed to get Gmail accounts working in ebase

To use ebase email functions to send/retrieve mail from a GMail account, the email account settings need to be set as outlined in the following FAQ page for the SMTPit plug-in.  (ebase uses the SMTPit Pro email plug in from CNS to provide email functionality):

During development, we found it particularly important to pay attention to the settings of "Outgoing TlsSslType" and "outgoing port".  You must use one of the following pairs of settings:

  • port 465 with "BeforeConnection"
  • port 587 with "AfterConnection"

Backing up your ebase

ebase 2.80 includes separate files for data and user interface. Your data file is the one that's most important to back up, but it's a good idea to keep one clean copy of the user interface file(s) as well, just so you don't have to download a new one if your current one is damaged.

Recovering from backup

If your ebase data is damaged somehow, either through file corruption, loss, hardware crash (etc.) or accidental data entry, you can revert to a backup of the data by simply deleting the ebase data file in use and replacing it with a backup copy.

The same goes for your ebase user interface: no data is stored in the user interface files, so you can upgrade them or recover from backup without losing anything. One caveat applies: if you've made customizations to your user interface, protect this file like your data file, as it it unique to you and not interchangeable with public versions of the user interface.

Reports and exports: analyzing & presenting your ebase data

Importing: bringing data en masse into ebase