# email.atmos.calendarPersonal

> Private calendar preferences and source settings. Each account controls its own Space and separate consent.

- Kind: space
- Authority: atmos.email
- Lexicon: 1
- Published by [comail.at](https://lexicon.garden/identity/did:plc:yu6rmwoemqfnmsdkljyvmuhg), the NSID's authority

## Links

- [Documentation](https://lexicon.garden/lexicon/did:plc:yu6rmwoemqfnmsdkljyvmuhg/email.atmos.calendarPersonal)
- [Schema JSON](https://lexicon.garden/lexicon/did:plc:yu6rmwoemqfnmsdkljyvmuhg/email.atmos.calendarPersonal/schema.json)
- [Analytics](https://lexicon.garden/lexicon/did:plc:yu6rmwoemqfnmsdkljyvmuhg/email.atmos.calendarPersonal/analytics)

## Space (`email.atmos.calendarPersonal`)

Type: space · key any

### Shown at sign-in

- `name` (string): Comail Calendar Preferences (alpha)

### Collections

- `collections` (array · nsid): The record collections clients of this space type use. A space: scope covers these unless it names its own.
  - Collections: `email.atmos.calendarPersonal.properties`, `email.atmos.calendarPersonal.sources`

### Asking for it (OAuth scope)

- `space:email.atmos.calendarPersonal` (scope): A client asks for access to spaces of this type with this scope. On its own it covers your own spaces, with any key, and reading, creating, updating and deleting records in the collections above; authority, skey, collection, action and manage narrow or widen that. From the Atproto Spaces proposal (0016).
  - Scope builder: `Open in the scope builder`

## Schema

```json
{
  "$type": "com.atproto.lexicon.schema",
  "defs": {
    "main": {
      "collections": [
        "email.atmos.calendarPersonal.properties",
        "email.atmos.calendarPersonal.sources"
      ],
      "description": "Private calendar preferences and source settings. Each account controls its own Space and separate consent.",
      "key": "any",
      "name": "Comail Calendar Preferences (alpha)",
      "type": "space"
    }
  },
  "draft": true,
  "id": "email.atmos.calendarPersonal",
  "lexicon": 1
}
```