NGO Software Views for Trustees and Programme Staff
A trust has a board, a donor desk, programme staff at centres and an accounts person. Each one works from a different slice of the same records.
Roles a trust usually sets up
These are the roles most trusts begin with, and they can be split further.
What one role does not see
Field staff at a tuition centre have no reason to open donor giving history, and a fundraiser has no reason to read a patient’s record at a health camp. Each login is kept to the records that role works on. Beneficiary names are often shown to programme staff and withheld from trustees, who read counts instead. The trust chooses where each of those lines falls.
Logins beyond the core staff
What the trust decides
Who gets which login is settled with the trust while the system is being set up, and it can be changed afterwards. GullySystem does not decide who in a trust may read what.
- Whether trustees see beneficiary names or only counts
- Whether a programme head may open another programme’s records
- Who may export donor or beneficiary lists
- Whether volunteers and auditors get logins at all
Frequently asked questions
Can one person hold two roles?
Yes. A small trust often has one person on donor records and accounts, and both sets of screens open under the same login.
Is a centre worker limited to their own centre?
Usually. Most trusts set field staff to one centre, and the programme head reads across all of them.
Do trustees need to learn the whole system?
No. A trustee login opens on summaries and board papers, and a trustee who wants more detail can be given it.
Can access be changed later?
Yes. Role changes are made by GullySystem staff when the trust asks, including a new role for a new programme.
Tell us what you need.
Send a short brief and one of our engineers will come back to you within one business day.
- No obligation
- A reply within one business day
- Your details stay private
