# at.sovrn.space.mailbox

> A private copy of one folder of your sovrn email, kept up to date by sovrn. It isn't public and isn't shared with anyone unless you choose to.

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

## Links

- [Documentation](https://lexicon.garden/lexicon/did:plc:54ba6vxrdbzi6nexczpk5xzb/at.sovrn.space.mailbox)
- [Schema JSON](https://lexicon.garden/lexicon/did:plc:54ba6vxrdbzi6nexczpk5xzb/at.sovrn.space.mailbox/schema.json)
- [Analytics](https://lexicon.garden/lexicon/did:plc:54ba6vxrdbzi6nexczpk5xzb/at.sovrn.space.mailbox/analytics)

## Space (`at.sovrn.space.mailbox`)

Type: space · key any

### Shown at sign-in

- `name` (string): Private email

### Collections

- `collections` (array · nsid): The record collections clients of this space type use. A space: scope covers these unless it names its own.
  - Collections: `at.sovrn.mail.mailbox`, `at.sovrn.mail.email`

### Asking for it (OAuth scope)

- `space:at.sovrn.space.mailbox` (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": [
        "at.sovrn.mail.mailbox",
        "at.sovrn.mail.email"
      ],
      "description": "A private copy of one folder of your sovrn email, kept up to date by sovrn. It isn't public and isn't shared with anyone unless you choose to.",
      "key": "any",
      "name": "Private email",
      "type": "space"
    }
  },
  "id": "at.sovrn.space.mailbox",
  "lexicon": 1
}
```
