# rsvp.atmo.dev.space

> For development and testing of atmo.rsvp spaces.

- Kind: space
- Authority: dev.atmo.rsvp
- Lexicon: 1
- Published by [atmo.rsvp](https://lexicon.garden/identity/did:plc:b63bmauox6z5rbibwrhxrdnw), the NSID's authority

## Links

- [Documentation](https://lexicon.garden/lexicon/did:plc:b63bmauox6z5rbibwrhxrdnw/rsvp.atmo.dev.space)
- [Schema JSON](https://lexicon.garden/lexicon/did:plc:b63bmauox6z5rbibwrhxrdnw/rsvp.atmo.dev.space/schema.json)
- [Analytics](https://lexicon.garden/lexicon/did:plc:b63bmauox6z5rbibwrhxrdnw/rsvp.atmo.dev.space/analytics)

## Space (`rsvp.atmo.dev.space`)

Type: space · key any

### Shown at sign-in

- `name` (string): atmo.rsvp development

### Asking for it (OAuth scope)

- `space:rsvp.atmo.dev.space` (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 the scope names; 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": [],
      "description": "For development and testing of atmo.rsvp spaces.",
      "key": "any",
      "name": "atmo.rsvp development",
      "type": "space"
    }
  },
  "id": "rsvp.atmo.dev.space",
  "lexicon": 1
}
```