---
# System prepended metadata

title: Apollo - Event Creation

---

# Apollo - Event Creation


- ![](https://i.imgur.com/R79bXsu.png)

here we can separate community and internal meetings by simply publishing these events in product channels or use the internal-calendar channel

- ![](https://i.imgur.com/83B6ZWT.png)

- ![](https://i.imgur.com/ANp8vnT.png)

- ![](https://i.imgur.com/2zLpCWb.png)

- choose 1 if you want a signup option (accepted, declined or tentative).
    Only users that accepted will get a notification when the event starts.
- choose 2 if you want to configure a signup option - here you can also choose not give the option to signup

- ![](https://i.imgur.com/5BItqEo.png)

- ![](https://i.imgur.com/oMOCDY3.png)

- ![](https://i.imgur.com/4vjXotc.png)

- ![](https://i.imgur.com/wOzi8Zt.png)

- Repeat: 
- ![](https://i.imgur.com/8c2qvbd.png)

- ![](https://i.imgur.com/h7WDuXq.png)

- Role mention & advanced (premium) options:
- ![](https://i.imgur.com/fHkWfXv.png)



Q: 
- internal meetings - seniors always want to be mentioned or not?
- internal meetings into product "main channel" instead of a collective #internal-calendar channel
- internal meetings into a public calendar
    - restrict signup to certain roles (premium feature) could be used to post publicly (signup feature must be used!) 
- signup option? if so - make sure everyone should be activly using this feature if they want to receive notifications
- a community event was tested for the last radio event - worked without any issue, some people are always confused :joy:


# Regular meetings:

- For every event apollo will create automatically a thread 15min before the meeting, this can be perfectly used to share stuff during the meeting (or e.g. AMA), this thread will automatically be archived 24h after the event! 

### Community Call
- bi-weekly, Friday (next meeting 12-17)
- default signup
- 3 PM UTC
- duration: 1h
- description
    - Join the Project managers from each of our teams for our Bi-weekly Community Call!
- new events will be created x days before the event starts
- mentioned role: @everyone

## mistX

### mistX Labs - Start of week team meeting
- weekly, Monday (next meeting 12-13)
- default signup
- 4 PM UTC
- duration: 1h
- description
    - none
- new events will be created 3 days before the event starts
- mentioned role: @mistx

### mistX Labs - End of week team meeting
- weekly, Thursday (next meeting 12-16)
- default signup
- 5 PM UTC
- duration: 1h
- description
    - none
- new events will be created 3 days before the event starts
- mentioned role: @mistx

## Crucible / NFT

### NFT Design weekly catchup
- weekly, Saturday (next meeting 12-18)
- default signup
- 1 PM UTC
- duration: 1h
- description
    - Weekly catchup for the NFT design team
- new events will be created X days before the event starts
- mentioned role: @crucible

### Crucible weekly meeting
- weekly, Thursday (next meeting 12-16)
- default signup
- 1 PM UTC
- duration: 30m
- description
    - Weekly meeting for the Crucible team
- new events will be created X days before the event starts
- mentioned role: @crucible

## Copper

### Copper Mid-Week Sync
- weekly, Wednesday (next meeting 12-15)
- default signup
- 9 PM UTC
- duration: ?
- description
    - none
- new events will be created X days before the event starts
- mentioned role: @copper

### Copper marketing x biz-dev
- weekly, Thursday (next meeting 12-16)
- default signup
- 8:30 PM UTC
- duration: 1h
- description
    - none
- new events will be created X days before the event starts
- mentioned role: @copper

### Copper Planning Meeting
- weekly, Sunday (next meeting 12-12)
- default signup
- 5 PM UTC
- duration: 1:30h
- description
    - Plan out team's work for the upcoming week
- new events will be created X days before the event starts
- mentioned role: @copper



