# chat.gel.assistant.conversation

> A single chat with an assistant. The space holds the chat's info record and messages. When sharing a chat, the read access on the space must be updated.

- Kind: space
- Authority: assistant.gel.chat
- Lexicon: 1
- Published by [gel.chat](https://lexicon.garden/identity/did:plc:k2csuyvih44bjf2lex73x56v), the NSID's authority

## Links

- [Documentation](https://lexicon.garden/lexicon/did:plc:k2csuyvih44bjf2lex73x56v/chat.gel.assistant.conversation)
- [Schema JSON](https://lexicon.garden/lexicon/did:plc:k2csuyvih44bjf2lex73x56v/chat.gel.assistant.conversation/schema.json)
- [Analytics](https://lexicon.garden/lexicon/did:plc:k2csuyvih44bjf2lex73x56v/chat.gel.assistant.conversation/analytics)

## Space (`chat.gel.assistant.conversation`)

Type: space · key tid

### Shown at sign-in

- `name` (string): Chat

### Collections

- `collections` (array · nsid): The record collections clients of this space type use. A space: scope covers these unless it names its own.
  - Collections: `chat.gel.assistant.info`, `chat.gel.assistant.message`

### Asking for it (OAuth scope)

- `space:chat.gel.assistant.conversation` (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": [
        "chat.gel.assistant.info",
        "chat.gel.assistant.message"
      ],
      "description": "A single chat with an assistant. The space holds the chat's info record and messages. When sharing a chat, the read access on the space must be updated.",
      "key": "tid",
      "name": "Chat",
      "type": "space"
    }
  },
  "id": "chat.gel.assistant.conversation",
  "lexicon": 1
}
```