Learn the daily workflows, set up your workspace and make every receipt feel like your temple.
Sign in using your temple’s staff sign-in page. Confirm the temple name before you begin. Available menus and actions depend on your assigned permissions and enabled features.
Use the sidebar or Find a menu to reach the right area. These explanations describe the sections observed in the application; use the actions available to your account.
See today’s collections, donations, bookings, upcoming services and operational alerts.
Review the date and temple time zone. Open the linked records or financial reports to investigate a total. Figures reflect the collections your account is permitted to view.
Serve devotees at the counter and review bills, bookings, donations, collections and receipts.
Find the devotee, choose the offering or donation purpose, review the amount and receiving account, then record the payment. Check the saved bill and receipt before printing. Use the available refund or cancellation action on the original record when appropriate.
Maintain devotee profiles, family relationships, memberships, deities and temple service information.
Search before creating a profile to avoid duplicates. Keep contact details current; use linked history to trace bookings and donations. Configure poojas, sevas and annual worship before taking bookings.
Maintain the items and categories used across temple operations.
Create clear names and review the unit, price and active status where the form provides them. Use consistent items in billing and stock records.
Manage prasadam orders, production, stock, distribution and collection tokens.
Check availability before accepting an order. Record production and distribution in their respective screens. Use the challan or token to support collection and review remaining stock.
Organise festival and event records and their schedules.
Maintain dates and descriptions, then review the related event details. Public visibility depends on the publication controls available in your workspace.
Track hundi sessions and their closure.
Open the relevant session, record the count using the available fields and review before closure. Use the financial report to review included collections.
Review temple notifications and communication configuration.
Check the configured channel and recipient before sending. A preview or saved sample is not proof that a message was delivered. Disabled channels must be configured before use.
Organise queues and tokens for temple services.
Choose the relevant queue, work through the available token actions and verify its current status. Keep staff responsibilities clear at each service point.
Maintain ornament records and the custody operations available to your temple.
Use identifiable records and review the available issue, return and history controls. Confirm the responsible person and record status before completing an operation.
Manage suppliers, purchases, goods receipts, stock locations, movements and assets.
Keep units and locations consistent. Record goods received and stock movements against the correct item; review on-hand and available stock before distribution.
Maintain staff information and the staff operations available to the temple.
Keep staff records current. A staff record and a sign-in account serve different purposes; manage account access under Users & access.
Review cash book, financial reports and accounting information.
Select the correct date range and inspect collection, payment and refund references. Compare exports with the displayed totals. Bank routing configuration does not itself transfer money.
Configure temple identity, language, colours, receipts, banks, website content and integrations.
Complete temple setup, then print settings and master data. Review gateway, calendar and email settings individually. Public booking and notification availability depend on the enabled configuration and plan.
Manage sign-in users, roles, permissions and access history.
Assign each person their own account and the permissions required for their work. Review View, Create, Update, Delete, Approve, Export and Print separately where available. Test the account after assignment.
The following is a recommended responsibility guide, not a promise of default permissions. A temple administrator configures the actual module and action permissions. Custom roles can differ.
| Role | Typical responsibility | Access to review |
|---|---|---|
| Temple Owner / Admin | Temple configuration, access policy and overall supervision. | Settings, Users, Roles and reports appropriate to the owner’s responsibility. |
| Temple Manager | Coordinate daily services, schedules, staff and exceptions. | Operational modules and approval actions specifically delegated by the owner. |
| Cashier | Find devotees, prepare bills, record collections and print receipts. | Billing, relevant bookings/donations/devotees and Print; refund access only if explicitly delegated. |
| Accountant | Review cash book, accounting entries, reconciliation and financial reporting. | Accounting, Finance/Reports and Export as required; operational billing access only when needed. |
| Reception | Register devotees and help with bookings and enquiries. | Devotees and Bookings; payment access only if reception also performs collections. |
| Priest | Review assigned services and the details needed to perform them. | Relevant pooja/seva schedules and minimum necessary devotee or booking information. |
| Inventory Manager | Maintain stock, purchases, suppliers, locations and distribution records. | Inventory and relevant prasadam/asset operations. |
| Staff | Carry out the specific duties assigned by the temple. | A narrow set of modules and actions matched to that person’s work. |
| Volunteer | Assist with assigned service points and visitor operations. | Limited queue or service information; financial and access administration usually unnecessary. |
Use your own logo, letterhead and footer alongside the built-in receipt and challan layouts.
Maintain organisation details, registration information, address, phone, email, website, currency, time zone and financial-year start month. Review the details that appear on receipts.
Changing the registered temple email requires reconnecting devotee email login, according to Temple setup.
Choose Light or Dark theme, a colour preset or custom primary/sidebar colours. Preview first and save temple settings to apply them for temple users.
Choose Heritage maroon, Temple teal, Royal navy, Warm saffron, Forest green or Sacred purple. Save to apply the theme to published temple pages. Workspace and login colours are separate.
Use a PNG/JPEG logo up to 2 MB. The workspace banner supports up to 2 MB and 4096 pixels per side; recommended size is 1600 × 320 pixels. Keep important artwork near the centre because it is cropped to fit.
Banner and contact-footer visibility can be switched off while keeping saved details.
Add bank accounts before enabling multiple-account routing. Assign receiving accounts to relevant offerings and donation purposes. Cash stays in cash in hand; this setup does not move money or change gateway settlement.
Review Cashfree gateway, calendar/panchanga and devotee email/Gmail configuration from their dedicated settings pages. Enable only services configured for your temple and verify their operation before relying on them.
Receipt layout and slip language are configured separately in Print settings. Service and item prices belong to their master-data screens.
Sign-in confirms your identity; your assigned permissions determine which screens you can use. Ask the temple administrator to review your role and the required module/action. A role name such as Cashier does not automatically grant billing access.
Check that the bill contains an item, required fields are complete and the payment covers the amount due. Review any validation message and the receiving account selection. Do not record a payment twice if the first save is still processing.
Upload your logo, wide letterhead/header and footer as PNG or JPEG in Temple setup or Print settings. Select Uploaded letterhead in Print settings, preview it and save artwork. Use the supplied slip layouts and header text controls for the remaining design.
The inspected upload controls accept PNG or JPEG images. Convert your approved letterhead to a suitable image before uploading. A free-form Word, PDF, HTML or CSS template import is not documented here.
No. Public website colours, staff workspace colours and receipt print layouts have separate controls. Configure each in its own section.
Temple setup supports English or Kannada for the application. Print settings has a separate slip-language selector. Names and descriptions remain as entered; receipt amount-in-words text is currently described as English.
Open the saved receipt preview and choose Print / Save PDF. Match the browser/printer paper size to the preview. Choose Save as PDF in the print dialog when available.
Save the artwork upload, then choose Uploaded letterhead as the receipt header style. The uploaded letterhead replaces the text header to avoid duplication. Confirm you are previewing the correct temple and the latest saved settings.
The Temple setup screen states that reprints use current temple artwork while transaction details stay unchanged. Keep an approved copy of important issued receipts if you need the original visual appearance.
Add accounts first. Enable multiple bank accounts if the temple needs them, then assign receiving accounts to applicable services. Donation purpose defaults are configured separately. Cash remains cash in hand; routing does not change gateway settlement.
Open the original donation and inspect its collection and refund history. Use available authorised actions and retain the original references. A full refund is reflected on the original receipt; do not delete history to make totals look correct.
Check the date range, temple time zone, included transaction types, refunds and your permissions. Today’s net collection is described as payments plus closed hundi, less refunds. Compare records within the same scope.
Check whether online booking is enabled, the offering is available and the required gateway/configuration is complete. A visible booking screen or gateway settings page does not establish that a live payment integration is ready.
Check the enabled channel, credentials/configuration, recipient details and available delivery status. An unsent preview is not a delivered notification.
Describe the screen, action, date/time, expected result and visible error. Include a bill/booking reference only through your authorised support channel. Redact passwords, API keys, bank details and unnecessary devotee information from screenshots.
Guide reviewed against the Demo2 interface on 10 October 2026. Screenshots are cropped examples; your permissions, plan and configuration may differ.
Back to top ↑