Skip to main content
GullySystem
Non-profit

Roles and Permissions for Temples

Control which records and actions each user can access.

Platform

Does this function belong in your operation?

Use when different staff should see or change different business information.

A user joins, changes responsibility or leaves.

The trust lists each trustee with role, photo and term, and sets whether the contact is shown on the website’s about page.

Bring the records the workflow depends on.

  • User list
  • Role responsibilities
  • Record-level access rules

Outputs to check

  • Approved role-access matrix
  • User assignment history
  • Access-review exception list

Follow the roles and permissions workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Map responsibilities

    Identify the records and actions each role needs.

  2. 2. Review sensitive rights

    Separate high-impact actions and define approval authority.

  3. 3. Assign named users

    Grant the approved roles without sharing credentials.

  4. 4. Test access

    Check permitted actions, denied actions and combined-role effects.

  5. 5. Review changes

    Remove obsolete access after transfers, temporary cover or departures.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Owner

Decides who may see money. It is the one setting most owners want to make themselves.

Branch manager

Works inside their own branch and requests anything beyond it.

Office admin

Adds a new joiner to a role on the first morning, and closes it on the last.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Temporary cover required

Grant time-limited authority with an owner and review date.

Conflicting roles assigned

Review combined permissions rather than checking each role in isolation.

User leaves

Revoke access in each connected system and track any unconfirmed closure separately.

Can this work independently?

Permissions operate on the applications and records that enforce them. A documented role matrix alone cannot restrict an unrelated system. Employee or identity-provider links can support joiner and leaver actions, while audit records show assignments and privileged changes.

Systems and records it connects with

  • Audit trail: Actor, timestamp and change evidence for controlled actions.
  • Multi-branch consolidation: Branch identifiers and reconciled combined reporting inputs.
  • Workflow and approvals: Authorised decisions and pending request status.
  • Payroll: Approved pay inputs, deduction calculations and payment instructions.

Configure, test and introduce the workflow.

  • You describe who does what in the business. You get a proposed set of roles to confirm.
  • Cost, margin, wastage and salary visibility are settled. A note records who may see each. Staff are entered with their own sign-in. Shared passwords are retired as people move across.
  • A few staff try their screens on the trial. They tell us what is missing or too open. Gaps are found early. Exceptions granted to individuals are reviewed with the owner. The leaving routine is written down.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Restricted records are inaccessible to unauthorised users.
  • Role changes affect the intended permissions.
  • Departed users lose access as configured.
Temples

How the business operates.

The temple office runs Temple Management Software, set up by GullySystem for trusts with a seva counter. Counter staff, priests and trustees use it. Seva and pooja bookings, donations by type, numbered PDF receipts, devotee details with gothra and nakshatra, festivals and priest duties sit together. The temple also gets a website with timings, sevas and a donation page.

Pooja booking

Set each seva’s price type, duration, days, time slots, bookings per slot and required devotee details. Bookings are numbered and move from pending to confirmed, assigned, completed or cancelled.

Online seva booking

Let devotees request a seva from your temple website with date, slot, gothra, nakshatra and sankalpa. The office confirms the request and takes payment at the counter when the family arrives.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Pooja booking. Set each seva’s price type, duration, days, time slots, bookings per slot and required devotee details. Bookings are numbered and move from pending to confirmed, assigned, completed or cancelled.
  • Online seva booking. Let devotees request a seva from your temple website with date, slot, gothra, nakshatra and sankalpa. The office confirms the request and takes payment at the counter when the family arrives.
  • Donations by type. Record every donation against a head you define, such as annadana, gau seva, building fund or hundi, with the donor’s tax ID, payment mode, reference and purpose. Each fund reads separately.
  • Online donations. Let devotees give from your website by bank transfer and enter the transaction reference. A numbered receipt is raised with that reference for matching against the bank statement.

Operational bottlenecks to check

Receipt books run out on festival days

On festival days a queue forms before the doors open. Receipts written by hand smudge in the heat of the counter, and the evening total may not match the cash box or the hundi count.

Bookings for the next day are not visible

Bookings arrive at the counter, by phone and through trustees, and each carries a different slip. The priest learns the sankalpa count only when names are read out at the homa.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Sevas and slots

    Enter each pooja or seva with the name your office uses, the amount or free-will offering, the days performed, time slots and bookings per slot. Choose which ones devotees may request online, and which stay counter-only.

  2. 2. Booking

    At the counter, staff pick the seva, date and slot, note the gothra, nakshatra, rashi and sankalpa, and take payment. Online requests arrive as pending bookings with those details filled in by the devotee.

  3. 3. Receipt

    Every paid booking or donation takes the next number in the series and comes out as a PDF. Donation receipts carry the trust’s tax-exemption details and the donor’s tax ID where the trust is registered for exemption.

  4. 4. Priest assignment

    The office assigns a priest to the booking and marks it confirmed, assigned or completed. The priest opens the day’s list with every sankalpa on it, in the order of the homa.

  5. 5. Closing the day

    The dashboard shows today’s donations, the month’s total, the day’s bookings and online requests still waiting, with collections by payment mode. Exports go to the trust’s accountant for the audit file.

Industry reports to connect with

  • Today’s and this month’s donations
  • Donations and seva bookings totals
  • Collections by payment mode: cash, cheque, bank transfer and online
  • Receipts register, downloadable as CSV

Questions before implementation.

When should temples consider roles and permissions?

Use when different staff should see or change different business information. A user joins, changes responsibility or leaves.

What should we bring to the requirements discussion?

Bring anonymised examples of User list; Role responsibilities; Record-level access rules. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Control which records and actions each user can access. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Permissions require ongoing ownership and do not replace broader security controls.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Restricted records are inaccessible to unauthorised users. Use this check when reviewing the first working version.

Talk to us

Discuss roles and permissions for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements