# Calendaring introduction

Anyone can read calendars shared publicly at Example orga.

Your personal [[account]] grants read-only access to closed-group shared calendars.

Custom group accounts provide write access to (closed-group or public) shared calendars.


## Special strings

NB! This documentation uses special strings
which you may want to adapt for your local setup:

organisation: Example orga
eventhost: event.example.org


## Clients

Recommended calendaring client depends on the operating system you use:

  * Mac, iPhone and iPad: Apple Calendar
  * Windows and Linux: [Mozilla Thunderbird](https://www.thunderbird.net/)
  * Android: [DAVdroid](https://f-droid.org/app/at.bitfire.davdroid)
    and [ICSdroid](https://f-droid.org/app/at.bitfire.icsdroid)


## Read-only access

When you only need to read a calendar,
the best (most efficient) is to subscribe to an **iCal** calender:

 1. Copy address of relevant calendar from web page
    <http://event.example.org/>.
 2. Open calendaring client, and add new account profile of type "ical".
 3. Paste the calendar address as server address.

Closed-group calendars also require username and password,
and require a secure connection (TLS or SSL, or "https://" address).


## Read-write access

To both read a calendar and help maintain its content,
you need to setup a **CalDAV** profile:

 1. Open calendaring client, and add new account profile of type "CalDAV".
 2. Server address: **event.example.org**
 3. Username and password: Either personal or calendar-group account credentials.

If above fails, or if you want to specifically pick a single calender,
use this alternative approach:

 1. Copy address of relevant calendar from web page
    **https://event.example.org/**  
    (replace USERNAME with either personal or calendar-group account name)
 2. Open calendaring client, and add new account profile of type "CalDAV".
 3. Paste the calendar address as server address.