01
Set Prayer Times
Choose the saved prayer settings used to generate every Preview Draft and Prayer Block.
Prayer Defaults are your saved source of truth. Workspace and scheduling use them to generate prayer times.
- Location sets the city, country, coordinates, and time zone.
- Calculation method uses Aladhan API for launch. Change it if your local mosque or community follows a different method.
- School changes Asr timing when needed.
- Selected prayer checkboxes decide which blocks appear in preview, sync, feeds, and emails.
- Before and after minute inputs create the reserved calendar window around each prayer.
- Save preferences stores the defaults. Workspace uses the saved version, not unsaved form changes.
- Saving Prayer Defaults from Settings or Preview Lab also queues live full sync for saved full auto sync rules when those prayer settings changed.
Field examples
You need 10 minutes before Dhuhr
Setup: Set Dhuhr before buffer to 10 and after buffer to 20, then save.
Expected: The Dhuhr Prayer Block reserves a 30-minute window around Dhuhr using those saved buffers.
You only want workday prayers
Setup: Select only the prayers you want generated, then use Working days only in Workspace or scheduling.
Expected: Unselected prayers never appear. Weekend filtering is applied later by the chosen delivery action.
Asr time looks different
Setup: Change the school setting and save.
Expected: New previews use the selected Asr school. Already delivered app-owned blocks change only when you sync or send again.
02
Choose Your Calendar Path
Pick the delivery method that fits your calendar permissions and comfort level.
- Email/export only: no calendar OAuth. You download or receive .ics files.
- Read-only Agenda Source: Arihna Biha reads your agenda for preview and protection, but does not write to it.
- Full sync Sync Target: Arihna Biha can create, update, track, and delete its own Prayer Blocks.
- Private feed URL: your calendar subscribes to a separate read-only prayer calendar.
- Invite email: one meeting invite is sent per Prayer Block.
Path examples
No calendar access
Setup: Use Download .ics or grouped .ics email.
Expected: You manually import the file. Arihna Biha does not read or write any provider calendar.
Preview around real meetings
Setup: Connect a read-only Agenda Source and make it visible in Workspace.
Expected: Arihna Biha can see blocker events for preview and protection, but it cannot create or edit calendar events.
Hands-off updates
Setup: Use a writable Sync Target or Supporter scheduling.
Expected: Arihna Biha can keep app-owned Prayer Blocks refreshed and remove them later through app actions.
Best first choice
If you are unsure, use read-only agenda access or email/export first. Upgrade to full sync when you want Arihna Biha to manage blocks directly.
03
Connect Calendars
Understand Calendar Connections, Agenda Sources, Sync Targets, and account limits.
- Calendar Connection
- A connected Google or Outlook account.
- Agenda Source
- A calendar Arihna Biha can read for preview and conflict context.
- Sync Target
- A writable calendar Arihna Biha can use for direct sync.
- Read-only access lets the app see busy events, but not create or edit them.
- Read-write access lets the app manage Arihna Biha-owned Prayer Blocks.
- Community access uses one active agenda account after setup.
- Supporter access unlocks full sync and higher limits.
- Switching Agenda Sources changes what Workspace reads without deleting the provider connection.
- Hidden sources stay connected, but Workspace protection ignores them until you show them again.
Connection examples
Use Work as blocker only
Setup: Connect Work calendar as an Agenda Source with read-only access.
Expected: Workspace can avoid work meetings, but Sync cannot write Prayer Blocks to that calendar.
Write prayers to a managed calendar
Setup: Select a writable calendar as a Sync Target.
Expected: Sync creates and updates Arihna Biha-owned Prayer Blocks on that target only.
Switch from Work to Personal agenda
Setup: Hide Work and show Personal in Agenda Sources.
Expected: Workspace protection now uses Personal events as blockers without disconnecting Work.
04
Send, Sync, Delete
Understand every Workspace action before it changes a calendar or sends files.
- Download .ics creates a calendar file on your device.
- Grouped .ics email sends one calendar file by email.
- Calendar invitations are marked Coming soon. Arihna Biha currently sends .ics calendar files by download or grouped email.
- Regenerated .ics files keep the same event identity for the same Prayer Block so calendar imports can update earlier Arihna Biha events instead of creating unrelated copies.
- Sync writes Arihna Biha-owned blocks to selected Sync Targets.
- Delete removes Arihna Biha-owned synced blocks based on the chosen scope.
- Undo restores the latest eligible delete.
- Before Sync or Send, the review dialog previews visible Agenda Source conflicts in the selected range.
- If conflicts appear, choose Protect first, adjust the range, or continue knowingly after review.
- The review checkbox confirms you inspected the targets and expected impact.
Examples
You only want a file
Setup: Use Download .ics.
Expected: Arihna Biha creates a file. No calendar account is changed by the app.
You want automatic calendar placement
Setup: Use Sync on a writable Sync Target.
Expected: Arihna Biha creates, updates, and can later delete only its own Prayer Blocks.
You want recipients to import by email
Setup: Use Grouped .ics email.
Expected: Arihna Biha sends one .ics file. Re-importing a regenerated file can update the same Prayer Blocks because their event identity stays stable.
Conflicts appear before delivery
Setup: Open Send or Sync while visible Agenda Source conflicts exist in the selected range.
Expected: The dialog shows the conflict preview before confirmation, with a Protect first path and range controls.